|
From: Tom H. <th...@cy...> - 2011-06-27 02:32:57
Attachments:
diffs
|
Nightly build on bristol ( x86_64, Fedora 14 ) Started at 2011-06-27 03:11:00 BST Ended at 2011-06-27 03:32:35 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 580 tests, 25 stderr failures, 1 stdout failure, 9 stderrB failures, 0 stdoutB failures, 0 post failures == gdbserver_tests/mcbreak (stderrB) gdbserver_tests/mcclean_after_fork (stderrB) gdbserver_tests/mcinfcallWSRU (stderrB) gdbserver_tests/mcleak (stderrB) gdbserver_tests/mcmain_pic (stderrB) gdbserver_tests/mcvabits (stderrB) gdbserver_tests/mssnapshot (stderrB) gdbserver_tests/nlpasssigalrm (stderrB) gdbserver_tests/nlsigvgdb (stderrB) memcheck/tests/linux/stack_switch (stderr) memcheck/tests/origin5-bz2 (stderr) cachegrind/tests/chdir (stderr) cachegrind/tests/clreq (stderr) cachegrind/tests/dlclose (stderr) cachegrind/tests/notpower2 (stderr) cachegrind/tests/wrap5 (stderr) cachegrind/tests/x86/fpu-28-108 (stderr) callgrind/tests/notpower2-hwpref (stderr) callgrind/tests/notpower2-use (stderr) callgrind/tests/notpower2-wb (stderr) callgrind/tests/notpower2 (stderr) callgrind/tests/simwork-both (stderr) callgrind/tests/simwork-cache (stderr) callgrind/tests/simwork1 (stderr) callgrind/tests/simwork2 (stderr) callgrind/tests/simwork3 (stderr) callgrind/tests/threads-use (stderr) helgrind/tests/locked_vs_unlocked1_fwd (stderr) helgrind/tests/locked_vs_unlocked1_rev (stderr) helgrind/tests/locked_vs_unlocked2 (stderr) helgrind/tests/locked_vs_unlocked3 (stderr) helgrind/tests/pth_barrier3 (stderr) helgrind/tests/tc06_two_races_xml (stderr) drd/tests/pth_detached2 (stdout) exp-sgcheck/tests/bad_percentify (stderr) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 575 tests, 25 stderr failures, 0 stdout failures, 5 stderrB failures, 0 stdoutB failures, 0 post failures == gdbserver_tests/mcbreak (stderrB) gdbserver_tests/mcclean_after_fork (stderrB) gdbserver_tests/mcinfcallWSRU (stderrB) gdbserver_tests/mcvabits (stderrB) gdbserver_tests/mssnapshot (stderrB) memcheck/tests/linux/stack_switch (stderr) memcheck/tests/origin5-bz2 (stderr) cachegrind/tests/chdir (stderr) cachegrind/tests/clreq (stderr) cachegrind/tests/dlclose (stderr) cachegrind/tests/notpower2 (stderr) cachegrind/tests/wrap5 (stderr) cachegrind/tests/x86/fpu-28-108 (stderr) callgrind/tests/notpower2-hwpref (stderr) callgrind/tests/notpower2-use (stderr) callgrind/tests/notpower2-wb (stderr) callgrind/tests/notpower2 (stderr) callgrind/tests/simwork-both (stderr) callgrind/tests/simwork-cache (stderr) callgrind/tests/simwork1 (stderr) callgrind/tests/simwork2 (stderr) callgrind/tests/simwork3 (stderr) callgrind/tests/threads-use (stderr) helgrind/tests/locked_vs_unlocked1_fwd (stderr) helgrind/tests/locked_vs_unlocked1_rev (stderr) helgrind/tests/locked_vs_unlocked2 (stderr) helgrind/tests/locked_vs_unlocked3 (stderr) helgrind/tests/pth_barrier3 (stderr) helgrind/tests/tc06_two_races_xml (stderr) exp-sgcheck/tests/bad_percentify (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Mon Jun 27 03:21:43 2011 --- new.short Mon Jun 27 03:32:35 2011 *************** *** 8,10 **** ! == 575 tests, 25 stderr failures, 0 stdout failures, 5 stderrB failures, 0 stdoutB failures, 0 post failures == gdbserver_tests/mcbreak (stderrB) --- 8,10 ---- ! == 580 tests, 25 stderr failures, 1 stdout failure, 9 stderrB failures, 0 stdoutB failures, 0 post failures == gdbserver_tests/mcbreak (stderrB) *************** *** 12,15 **** --- 12,19 ---- gdbserver_tests/mcinfcallWSRU (stderrB) + gdbserver_tests/mcleak (stderrB) + gdbserver_tests/mcmain_pic (stderrB) gdbserver_tests/mcvabits (stderrB) gdbserver_tests/mssnapshot (stderrB) + gdbserver_tests/nlpasssigalrm (stderrB) + gdbserver_tests/nlsigvgdb (stderrB) memcheck/tests/linux/stack_switch (stderr) *************** *** 38,39 **** --- 42,44 ---- helgrind/tests/tc06_two_races_xml (stderr) + drd/tests/pth_detached2 (stdout) exp-sgcheck/tests/bad_percentify (stderr) |
|
From: Bart V. A. <bva...@ac...> - 2011-06-27 10:39:53
|
On Mon, Jun 27, 2011 at 4:32 AM, Tom Hughes <th...@cy...> wrote: > > Nightly build on bristol ( x86_64, Fedora 14 ) > Started at 2011-06-27 03:11:00 BST > Ended at 2011-06-27 03:32:35 BST > Results differ from 24 hours ago > > [ ... ] > > helgrind/tests/tc06_two_races_xml (stderr) > + drd/tests/pth_detached2 (stdout) > exp-sgcheck/tests/bad_percentify (stderr) > > [ ... ] Hi Tom, The test "drd/tests/pth_detached2" is failing intermittently since a long time, and even without any source code changes related to that test. I have been wondering whether this could be related to Valgrind's scheduling unfairness. The next question is: how many CPU cores are present in the system called "bristol" ? I haven't seen this behavior yet on any of the dual-core systems I have access to. Thanks, Bart. |
|
From: Tom H. <th...@cy...> - 2011-06-27 11:11:21
|
On 27/06/11 11:39, Bart Van Assche wrote: > The test "drd/tests/pth_detached2" is failing intermittently since a > long time, and even without any source code changes related to that > test. I have been wondering whether this could be related to Valgrind's > scheduling unfairness. The next question is: how many CPU cores are > present in the system called "bristol" ? I haven't seen this behavior > yet on any of the dual-core systems I have access to. It's a 6 core (with HT so 12 threads) machine. The result you quoted is from F14 but the machine is actually running F15 really but I run the tests under various other versions of Fedora via mock. That's a recent change though - previously I was using a number of different machines. I just ran the DRD tests (on F15) and this time it was pth_detached_sem which failed. On a second run they all passed, as did a number of manual runs of both pth_detached2 and pth_detached_sem. Tom -- Tom Hughes (th...@cy...) Software Engineer, Cyberscience Corporation http://www.cyberscience.com/ |