* gdb make check dying
@ 2010-02-04 14:27 Chris Moller
2010-02-04 16:33 ` Tom Tromey
0 siblings, 1 reply; 3+ messages in thread
From: Chris Moller @ 2010-02-04 14:27 UTC (permalink / raw)
To: Project Archer
Starting at about 2100 (east coast US) least night, fresh checkouts of
gdb build okay but 'make checks' fails. Is anyone else seeing this?
> /test-demangle < ../../../src/libiberty/testsuite/demangle-expected
> FAIL at line 3937: unknown demangling style _Z1fI1AEDTclonplfp_fp_EET_
> FAIL at line 3944: unknown demangling style _Z1hI1AEDTcldtfp_miEET_
> FAIL at line 3948: unknown demangling style yz__qrs
> FAIL at line 3952: unknown demangling style oper__Oadd
> FAIL at line 3956: unknown demangling style yz__qrs__2
> FAIL at line 3960: unknown demangling style yz__qrs__tuv.1661
> FAIL at line 3963: unknown demangling style yz__qrs__tuv__2_1.1667
> FAIL at line 3966: unknown demangling style yz__qrs__tuv__2_2.1670
> FAIL at line 3970: unknown demangling style yz__qrs__tuv__2_3.1674
> FAIL at line 3974: unknown demangling style x_E
> FAIL at line 3977: unknown demangling style x__m1
> FAIL at line 3980: unknown demangling style x__m3
> FAIL at line 3983: unknown demangling style x__y__m2X
> FAIL at line 3987: unknown demangling style x__y__z__rXb
> FAIL at line 3991: unknown demangling style x__y__j
> FAIL at line 3995: unknown demangling style _ada_x__m3
> FAIL at line 3999: unknown demangling style p___elabb
> FAIL at line 4003: unknown demangling style p___elabs
> FAIL at line 4007: unknown demangling style p__taskobjTKB
> FAIL at line 4011: unknown demangling style p__taskobjTK__f1.2330
> FAIL at line 4014: unknown demangling style prot__lock__getN
> FAIL at line 4017: unknown demangling style prot__lock__getP
> FAIL at line 4020: unknown demangling style prot__lock__get__sub.2590
> FAIL at line 4023: unknown demangling style prot__lock__setN
> FAIL at line 4027: unknown demangling style prot__lock__setP
> FAIL at line 4030: unknown demangling style prot__lock__update_B7s
> FAIL at line 4035: unknown demangling style prot__lock__update_E6s
> FAIL at line 4038: unknown demangling style DFA
> ./test-demangle: 812 tests, 28 failures
> make[3]: *** [check-cplus-dem] Error 1
> make[3]: Leaving directory
> `/home/moller/tinkering/fsfgdb/pr11067/build/libiberty/testsuite'
> make[2]: *** [check-subdir] Error 2
> make[2]: Leaving directory
> `/home/moller/tinkering/fsfgdb/pr11067/build/libiberty'
> make[1]: *** [check-libiberty] Error 2
> make[1]: Leaving directory `/home/moller/tinkering/fsfgdb/pr11067/build'
> make: *** [do-check] Error 2
> [2] (moller@qcore)
> > 9:21:04
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: gdb make check dying
2010-02-04 14:27 gdb make check dying Chris Moller
@ 2010-02-04 16:33 ` Tom Tromey
2010-02-04 16:55 ` Tom Tromey
0 siblings, 1 reply; 3+ messages in thread
From: Tom Tromey @ 2010-02-04 16:33 UTC (permalink / raw)
To: Chris Moller; +Cc: Project Archer
Chris> Starting at about 2100 (east coast US) least night, fresh checkouts of
Chris> gdb build okay but 'make checks' fails. Is anyone else seeing this?
>> /test-demangle < ../../../src/libiberty/testsuite/demangle-expected
>> FAIL at line 3937: unknown demangling style _Z1fI1AEDTclonplfp_fp_EET_
Looks like a bad change in the demangler test suite.
>> make[3]: *** [check-cplus-dem] Error 1
>> make[3]: Leaving directory
>> /home/moller/tinkering/fsfgdb/pr11067/build/libiberty/testsuite'
>> make[2]: *** [check-subdir] Error 2
>> make[2]: Leaving directory
>> /home/moller/tinkering/fsfgdb/pr11067/build/libiberty'
>> make[1]: *** [check-libiberty] Error 2
>> make[1]: Leaving directory `/home/moller/tinkering/fsfgdb/pr11067/build'
>> make: *** [do-check] Error 2
As a rule you must use "make -k check".
FWIW, when I'm doing stuff locally, I only ever run the test suite in
gdb -- and then usually only parts of it. The regression tester on the
compile farm uses "make -k check" and handles diffing the sum files and
whatnot for me.
Tom
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: gdb make check dying
2010-02-04 16:33 ` Tom Tromey
@ 2010-02-04 16:55 ` Tom Tromey
0 siblings, 0 replies; 3+ messages in thread
From: Tom Tromey @ 2010-02-04 16:55 UTC (permalink / raw)
To: Chris Moller; +Cc: Project Archer
>>> /test-demangle < ../../../src/libiberty/testsuite/demangle-expected
>>> FAIL at line 3937: unknown demangling style _Z1fI1AEDTclonplfp_fp_EET_
Tom> Looks like a bad change in the demangler test suite.
I checked in a fix for this in the gcc repository.
DJ's sync script will pull it into src soon.
Tom
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-02-04 16:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-02-04 14:27 gdb make check dying Chris Moller
2010-02-04 16:33 ` Tom Tromey
2010-02-04 16:55 ` Tom Tromey
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).