[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#502311: testsuite failures in glibc



Sven Joachim a écrit :
> On 2009-02-18 18:00 +0100, Aurelien Jarno wrote:
> 
>> Then maybe some regressions have been added in the latest versions.
>> Could you retry with a 2.6.26 kernel from lenny/unstable? This version
>> is working on the buildd and on my machine, so that will infirm/confirm
>> it is due to the kernel.
> 
> Would not be very convenient for me, but I may try it sometime later.
> In the meantime, to isolate problems due to the combination 64-bit
> kernel/32-bit userland I re-ran the testsuite with "linux32 debian/rules
> build" and got one error less than originally:
> 
> ,----
> | #
> | # Testsuite failures, someone should be working towards
> | # fixing these! They are listed here for the purpose of
> | # regression testing during builds.
> | # Format: <Failed test>, Error <Make error code> [(ignored)]
> | #
> | annexc.out, Error 1 (ignored)
> | check-localplt.out, Error 1
> | tst-cancel7.out, Error 1
> | tst-cancelx4.out, Error 1
> | tst-cancelx5.out, Error 1
> | tst-cancelx7.out, Error 1
> | tst-cleanup0.out, Error 2
> | tst-cpuclock2.out, Error 1
> | tst-fmon.out, Error 1
> | ***************
> | Encountered regressions that don't match expected failures:
> | tst-cancel7.out, Error 1
> | tst-cancelx7.out, Error 1
> | tst-cleanup0.out, Error 2
> | tst-cpuclock2.out, Error 1
> | tst-fmon.out, Error 1
> `----
> 
> The tst-cancel*.out files all consist of a single line reading 
> 
> child <pid> still running

When the test is running correctly, the child exit correctly and this
file is empty.

> The error in tst-cleanup0.out is due to a bashism in the test suite, I'm
> using dash as /bin/sh.  See the excerpt in the attached file
> tst-cleanup0-bashism.  There are probably more bashisms, e.g. in
> nptl/tst-tls6.sh.

Thanks, I'll commit a patch to fix that.

> The error in tst-fmon.out is unclear to me, I'm attaching that file as
> well.  I doubt that it has to do anything with the kernel, though.

Yeah, I agree it is not related to the kernel, it may be related to the
build environment though. I'll try to understand why.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net



Reply to: