[Top][All Lists]

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

Re: [GNU Autoconf 2.68] testsuite: 205 failed

From: Ralf Corsepius
Subject: Re: [GNU Autoconf 2.68] testsuite: 205 failed
Date: Thu, 23 Sep 2010 14:36:30 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100907 Fedora/3.1.3-1.fc13 Thunderbird/3.1.3

On 09/23/2010 02:11 PM, Eric Blake wrote:
On 09/22/2010 10:31 PM, Ralf Corsepius wrote:
205: parallel autotest and signal handling FAILED (autotest.at:1617)

* Fedora 12/13/14 i386/x86_64
* RHEL6 beta2 i386/x86_64

Odd, because I specifically tested under these two, and it passed for
me. Is there an environmental difference between our two setups,

Likely - As with previous reports I sent on 2.67, I am actually building autoconf rpms in mock chroots on Fedora 13/x86_64.

such as
an inherited ignored SIGPIPE setup in the test environment? Remember,
POSIX states that a shell that inherits ignored SIGPIPE at startup
cannot undo that effect (which is rather annoying).

From what I can gather, it's the "killer test" which fails:

Not quite, it's the point at which the testsuite.log shows a diff in
expected vs. actual output. The killer test is supposed to fail, and the
real failure is occurring later in the log. But Ralf Wildenhues'
analysis is correct - the test is making a bad assumption about what
scenarios will cause a SIGPIPE, and if SIGPIPE doesn't actually happen,
then the test gets confused and fails.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]