Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <471D1175.5060000@roguewave.com>
Date: Mon, 22 Oct 2007 15:09:09 -0600
From: Martin Sebor <sebor@roguewave.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: Re: [VOTE] release stdcxx 4.2.0 (candidate 7)
References: <47180BDA.40002@roguewave.com> <471A8753.4030600@roguewave.com>
 <471CE713.5010904@roguewave.com> <471CEBE2.4020402@roguewave.com>
 <471D0CF6.8050709@roguewave.com>
In-Reply-To: <471D0CF6.8050709@roguewave.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Liviu Nicoara wrote:
> Martin Sebor wrote:
>> Liviu Nicoara wrote:
>>> +1.
>>
>> Thanks!
>>
>> Just for the record, what particular platform (compiler/OS) and
>> configuration did you test the tarball on?
> 
> Slack 10.1, gcc 4.2.0, 11s. I've got:
> 
> PROGRAM SUMMARY:
>   Programs:                187
>   Non-zero exit status:      0
>   Signalled:                10
>   Compiler warnings:         0
>   Linker warnings:           0
>   Runtime warnings:         68
>   Assertions:           11525052
>   Failed assertions:      5229

Thanks. I'm guessing this is the summary for the tests (our nightly
builds show 360 tests but that includes 173 tests that haven't been
moved out of the Rogue Wave Perforce repository and into Apache
Subversion).

The closest we have to gcc 4.2.0 (on Slackware) is probably gcc
4.1.0 (on SuSE 10.0). The test summary for an 11s build is below
(see the full log here: http://tinyurl.com/2yk5z3). There are 12
tests that fail with a signal (9 with ARBRT, 2 with HUP, and 1
with SEGV). As I just said to Brad, we're comfortable with these
results for 4.2.0 (although we should try to reduce the number of
signaled tests in the future).

PROGRAM SUMMARY:
   Programs:                360
   Non-zero exit status:      1
   Signalled:                12
   Compiler warnings:         0
   Linker warnings:           0
   Runtime warnings:         92
   Assertions:           13904014
   Failed assertions:      6366

Martin

> 
> Liviu
> 
>>
>> Martin
>>
>>>
>>> Martin Sebor wrote:
>>>> I just created the next stdcxx 4.2.0 release candidate tag,
>>>> stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
>>>> pointed out in the original vote thread.
>>>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
>>>>
>>>> The tarball containing the release candidate sources can be
>>>> downloaded from my home directory at the following link:
>>>> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz 
>>>>
>>>>
>>>> The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
>>>>
>>>> Instructions on unpacking the tarball, configuring and building
>>>> the library and the set of examples and tests, are in the README
>>>> file contained in the tarball and can also be viewed directly
>>>> in Subversion:
>>>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
>>>>
>>>> The Jira "Release Notes" for 4.2.0 detailing the issues resolved
>>>> in this release can be viewed here:
>>>> http://tinyurl.com/ytzonz
>>>>
>>>> stdcxx 4.2.0 has been tested on the set of platforms listed in
>>>> the README. The test results for most of the tested platforms
>>>> can be be viewed on the following page:
>>>> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
>>>> (there are a few failures, most of them attributable to issues in
>>>> the Rogue Wave test infrastructure; a small number of failures are
>>>> due to known stdcxx issues).
>>>>
>>>> Please download and test the tarball and vote to approve the
>>>> release and to request the approval of the Incubator PMC to publish
>>>> it on the stdcxx site. In your vote, please include the names and
>>>> versions of the compilers and operating systems that you tested on.
>>>>
>>>> As always, everyone is encouraged to vote, including non-committers.
>>>>
>>>> This vote will close in the usual 72 hours from now, i.e., on
>>>> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
>>>> below for the countdown:
>>>> http://tinyurl.com/2h5f73
>>>>
>>>>
>>>
>>>
>>
>>
> 
>