Return-Path: Delivered-To: apmail-stdcxx-issues-archive@locus.apache.org Received: (qmail 27595 invoked from network); 22 Apr 2008 15:03:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Apr 2008 15:03:46 -0000 Received: (qmail 2772 invoked by uid 500); 22 Apr 2008 15:03:47 -0000 Delivered-To: apmail-stdcxx-issues-archive@stdcxx.apache.org Received: (qmail 2749 invoked by uid 500); 22 Apr 2008 15:03:47 -0000 Mailing-List: contact issues-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list issues@stdcxx.apache.org Received: (qmail 2738 invoked by uid 99); 22 Apr 2008 15:03:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Apr 2008 08:03:47 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Apr 2008 15:03:02 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5B211234C102 for ; Tue, 22 Apr 2008 08:00:22 -0700 (PDT) Message-ID: <1468786110.1208876422372.JavaMail.jira@brutus> Date: Tue, 22 Apr 2008 08:00:22 -0700 (PDT) From: "Martin Sebor (JIRA)" To: issues@stdcxx.apache.org Subject: [jira] Commented: (STDCXX-731) framework to verify binary compatibility In-Reply-To: <1942912077.1203457243459.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/STDCXX-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591321#action_12591321 ] Martin Sebor commented on STDCXX-731: ------------------------------------- One relatively easy, semi-automatic way of doing this would be to enhance the [{{buildntest}}|http://svn.apache.org/repos/asf/stdcxx/trunk/bin/buildntest] script to do two builds with two sets of sources, then swap the libraries, and rerun all examples and tests. The results of those builds would then be processed by the [{{xbuildgen}}|http://svn.apache.org/repos/asf/stdcxx/trunk/bin/xbuildgen] script to produce a single cross-build report. > framework to verify binary compatibility > ---------------------------------------- > > Key: STDCXX-731 > URL: https://issues.apache.org/jira/browse/STDCXX-731 > Project: C++ Standard Library > Issue Type: Improvement > Components: Test Harness > Affects Versions: 4.2.0 > Reporter: Martin Sebor > Fix For: 4.2.2 > > Original Estimate: 80h > Remaining Estimate: 80h > > In the 4.2.0 release we ran into binary incompatibilities late in the release cycle that ended up costly to fix. What would have prevented the incompatibilities, or at least allowed us to detect them early on, would have been an automated framework to verify the binary compatibility of the library. This is a placeholder issue to design and implement such a framework. > I'm guesstimating the effort of putting something like this in place at 80 hours, possibly more. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.