[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNU Autoconf 2.68] testsuite: 205 failed
|
From: |
Eric Blake |
|
Subject: |
Re: [GNU Autoconf 2.68] testsuite: 205 failed |
|
Date: |
Thu, 23 Sep 2010 06:11:11 -0600 |
|
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100907 Fedora/3.1.3-1.fc13 Mnenhy/0.8.3 Thunderbird/3.1.3 |
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, 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.
--
Eric Blake address@hidden +1-801-349-2682
Libvirt virtualization library http://libvirt.org