You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@stdcxx.apache.org by "Martin Sebor (JIRA)" <ji...@apache.org> on 2008/02/19 22:40:43 UTC
[jira] Created: (STDCXX-731) framework to verify binary
compatibility
framework to verify binary compatibility
----------------------------------------
Key: STDCXX-731
URL: https://issues.apache.org/jira/browse/STDCXX-731
Project: C++ Standard Library
Issue Type: Bug
Affects Versions: 4.2.0
Reporter: Martin Sebor
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.
[jira] Commented: (STDCXX-731) framework to verify binary
compatibility
Posted by "Martin Sebor (JIRA)" <ji...@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.
[jira] Updated: (STDCXX-731) framework to verify binary
compatibility
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor updated STDCXX-731:
--------------------------------
Component/s: Test Harness
Set Component to Test Harness.
> framework to verify binary compatibility
> ----------------------------------------
>
> Key: STDCXX-731
> URL: https://issues.apache.org/jira/browse/STDCXX-731
> Project: C++ Standard Library
> Issue Type: Bug
> Components: Test Harness
> Affects Versions: 4.2.0
> Reporter: Martin Sebor
> 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.
[jira] Updated: (STDCXX-731) framework to verify binary
compatibility
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor updated STDCXX-731:
--------------------------------
Issue Type: Improvement (was: Bug)
Set Issue Type to Improvement (to the existing test harness).
> 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
> 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.
[jira] Issue Comment Edited: (STDCXX-731) framework to verify
binary compatibility
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591318#action_12591318 ]
sebor edited comment on STDCXX-731 at 4/22/08 7:52 AM:
--------------------------------------------------------------
See also these [posts|http://stdcxx.markmail.org/search/?q=subject%3AABI%20test%20results].
Scheduled for 4.2.2.
was (Author: sebor):
See also these [posts|http://stdcxx.markmail.org/search/?q=ABI%20test%20results].
Scheduled for 4.2.2.
> 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.
[jira] Updated: (STDCXX-731) framework to verify binary
compatibility
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor updated STDCXX-731:
--------------------------------
Fix Version/s: 4.2.2
See also these [posts|http://stdcxx.markmail.org/search/?q=ABI%20test%20results].
Scheduled for 4.2.2.
> 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.
[jira] Updated: (STDCXX-731) framework to verify binary
compatibility
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor updated STDCXX-731:
--------------------------------
Fix Version/s: (was: 4.2.2)
4.3.0
It sure would be nice to have but who's got the time to write it...? Deferred until 4.3.0.
> 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.3.0
>
> 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.