On Wed, 2015-11-25 at 01:27 +0100, Raphael Hertzog wrote: > On Tue, 24 Nov 2015, Ben Hutchings wrote: > > You should copy out the test output file so it's possible to see which > > step of the mqueue5 test failed. > > > > There are some recent changes to the mqueue implementation in Linux > > that might possibly have caused this (not because they are known buggy, > > but they may have user-visible effects). However it's fairly pointless > > for me to look any further without that test output. > > In a build in a normal chroot (not a minimal-sbuild one), I only got the > failure > for the amd64-i386 build: > ┏(squeeze-amd64) x230-buxy:~/deb/lts/pkg/eglibc-2.11.3 > ┗(543)$ cat build-tree/amd64-i386/rt/tst-mqueue5.out > SIGRTMIN signal in child did not arrive > child failed with status 256
The test doesn't fail reliably. Running tst-mqueue5 program against the current libc6-686, 7 out of 100 runs failed in this way. Running it against the new libc6, 8 out of 100 failed. (Both in a squeeze:i386 chroot with a 4.2 amd64 kernel.) Whatever is going wrong here, I don't think it's a regression. Ben. -- Ben Hutchings This sentence contradicts itself - no actually it doesn't.
signature.asc
Description: This is a digitally signed message part
