Hello!
> I have been seeing 3 libstdc++ tests:
>
> FAIL: 17_intro/headers/c++200x/stdc++.cc (test for excess errors)
> FAIL: 17_intro/headers/c++200x/stdc++_multiple_inclusion.cc (test for excess
> errors)
> FAIL: 30_threads/async/async.cc execution test
>
> fail/pass at random on a fast machine.
On 7 December 2013 17:28, H.J. Lu wrote:
> On Sat, Dec 7, 2013 at 9:26 AM, H.J. Lu wrote:
>> On Sat, Dec 7, 2013 at 9:09 AM, Jakub Jelinek wrote:
>FAIL: 30_threads/async/async.cc execution test
>>>
>>> async.exe:
>>> /usr/src/gcc/libstdc++-v3/testsuite/30_threads/async/async.cc:66: void
>
I'll look into the async failure when I get home in a few hours.
On Sat, Dec 7, 2013 at 9:26 AM, H.J. Lu wrote:
> On Sat, Dec 7, 2013 at 9:09 AM, Jakub Jelinek wrote:
>> On Sat, Dec 07, 2013 at 05:43:12PM +0100, Paolo Carlini wrote:
>>> On 12/07/2013 04:48 PM, H.J. Lu wrote:
>>> >I have been seeing 3 libstdc++ tests:
>>> >
>>> >FAIL: 17_intro/headers/c++200x/s
On Sat, Dec 7, 2013 at 9:09 AM, Jakub Jelinek wrote:
> On Sat, Dec 07, 2013 at 05:43:12PM +0100, Paolo Carlini wrote:
>> On 12/07/2013 04:48 PM, H.J. Lu wrote:
>> >I have been seeing 3 libstdc++ tests:
>> >
>> >FAIL: 17_intro/headers/c++200x/stdc+
>> >+.cc (test for excess errors)
>> >FAIL: 17_int
On Sat, Dec 07, 2013 at 05:43:12PM +0100, Paolo Carlini wrote:
> On 12/07/2013 04:48 PM, H.J. Lu wrote:
> >I have been seeing 3 libstdc++ tests:
> >
> >FAIL: 17_intro/headers/c++200x/stdc+
> >+.cc (test for excess errors)
> >FAIL: 17_intro/headers/c++200x/stdc++_multiple_inclusion.cc (test for
> >e
On 12/07/2013 04:48 PM, H.J. Lu wrote:
Hi,
I have been seeing 3 libstdc++ tests:
FAIL: 17_intro/headers/c++200x/stdc+
+.cc (test for excess errors)
FAIL: 17_intro/headers/c++200x/stdc++_multiple_inclusion.cc (test for
excess errors)
FAIL: 30_threads/async/async.cc execution test
fail/pass at r
Hi,
I have been seeing 3 libstdc++ tests:
FAIL: 17_intro/headers/c++200x/stdc+
+.cc (test for excess errors)
FAIL: 17_intro/headers/c++200x/stdc++_multiple_inclusion.cc (test for
excess errors)
FAIL: 30_threads/async/async.cc execution test
fail/pass at random on a fast machine. Is this expecte