Re: Bug#672152: perl: FTBFS on kfreebsd-*: dist/threads-shared/t/waithires.t failing
- To: Steven Chamberlain <email@example.com>, firstname.lastname@example.org
- Cc: email@example.com, firstname.lastname@example.org
- Subject: Re: Bug#672152: perl: FTBFS on kfreebsd-*: dist/threads-shared/t/waithires.t failing
- From: Niko Tyni <email@example.com>
- Date: Wed, 23 May 2012 15:49:31 +0300
- Message-id: <20120523124931.GA5268@madeleine.local.invalid>
- In-reply-to: <20120511094622.GA5164@madeleine.local.invalid>
- References: <E1SRWRT-0005HTfirstname.lastname@example.org> <20120508205938.GQ29215@urchin.earth.li> <4FA9D4EE.email@example.com> <20120511094622.GA5164@madeleine.local.invalid>
On Fri, May 11, 2012 at 12:46:22PM +0300, Niko Tyni wrote:
> On Wed, May 09, 2012 at 03:22:38AM +0100, Steven Chamberlain wrote:
> > Trying this a few times, I see different tests failing each time: they
> > are the six 'condition obtained' checks for cond_timedwait. Some fail
> > noticeably more often than others. Based on ~60 runs on kfreebsd-i386:
> > Strangely it seems like perl 5.14.2-9 does the same. I'm using
> > experimental eglibc 2.13-32+kkh901.
> It seems to be a regression in eglibc, not in perl itself. My guess is
> the fix for #654783 in 2.13-31, but it's definitely between -27 and -32.
> Trying on kfreebsd-amd64 (asdfasdf.debian.net), the test passes
> consistently in the wheezy chroot (libc0.1_2.13-27) and fails most of
> the time in the sid one (libc0.1_2.13-32). If I LD_PRELOAD libpthread.so
> from wheezy, the tests start to pass in sid, and vice versa: LD_PRELOADing
> the sid libpthread.so in wheezy makes the test fail.
> I don't have a C test case yet, not sure how soon I can pull one
> together. Help is appreciated.
This build failure is blocking perl testing migration and is affecting
other transitions. I think we'll have to upload a new perl package with
the failing test disabled / marked as TODO on kfreebsd-* for now.
I suppose that means #672152 will stay open at 'important' until somebody
has the time to look into it properly.
Niko Tyni firstname.lastname@example.org