This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Keeping clean build and test status


On Sun, Feb 26, 2012 at 03:36:33PM +0000, Joseph S. Myers wrote:
> I think we should aim to keep a clean build, and clean "make check", at 
> all times - which in turn means doing a build and testsuite run for almost 
> any change that could conceivably affect the results, before checking it 
> in; glibc is quick enough to build and test, even on previous-generation 

Sounds sensible.  Currently I'm seeing:

make: *** [check] Error 2
make[2]: *** [/home/marek/libc-build/math/test-double.out] Error 1
make[2]: *** [/home/marek/libc-build/math/test-idouble.out] Error 1
make[1]: *** [math/tests] Error 2
make[2]: [/home/marek/libc-build/posix/annexc.out] Error 1 (ignored)
make[2]: *** [/home/marek/libc-build/conform/run-conformtest.out] Error 1
make[1]: *** [conform/tests] Error 2
make[2]: *** [/home/marek/libc-build/elf/tst-audit1.out] Error 139
make[2]: *** [/home/marek/libc-build/elf/tst-audit2.out] Error 139
make[2]: *** [/home/marek/libc-build/elf/tst-audit3.out] Error 139
make[2]: *** [/home/marek/libc-build/elf/tst-audit4.out] Error 139
make[2]: *** [/home/marek/libc-build/elf/tst-audit5.out] Error 139
make[2]: *** [/home/marek/libc-build/elf/tst-audit6.out] Error 139
make[2]: *** [/home/marek/libc-build/elf/tst-audit7.out] Error 139
make[2]: *** [/home/marek/libc-build/elf/check-localplt.out] Error 1
make[1]: *** [elf/tests] Error 2
make: *** [check] Error 2

Those tst-audit?.out fails are something weird I haven't inspected yet:
/bin/sh: line 1:  2562 Segmentation fault      (core dumped)

But, do you see those test-[i]double.out fails too?

	Marek


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]