|
From: Tom H. <to...@co...> - 2005-11-01 03:40:23
|
Nightly build on dunsmere ( athlon, Fedora Core 4 ) started at 2005-11-01 03:30:04 GMT 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 == 203 tests, 13 stderr failures, 6 stdout failures ================= memcheck/tests/leak-tree (stderr) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/weirdioctl (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/map_unmap (stdout) none/tests/map_unmap (stderr) none/tests/mremap2 (stdout) none/tests/pth_blockedsig (stdout) none/tests/pth_blockedsig (stderr) none/tests/sigstackgrowth (stdout) none/tests/sigstackgrowth (stderr) none/tests/stackgrowth (stdout) none/tests/stackgrowth (stderr) none/tests/thread-exits (stdout) none/tests/thread-exits (stderr) none/tests/x86/int (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 == 203 tests, 11 stderr failures, 4 stdout failures ================= memcheck/tests/leak-tree (stderr) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/weirdioctl (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/map_unmap (stdout) none/tests/map_unmap (stderr) none/tests/mremap2 (stdout) none/tests/sigstackgrowth (stdout) none/tests/sigstackgrowth (stderr) none/tests/stackgrowth (stdout) none/tests/stackgrowth (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Tue Nov 1 03:35:14 2005 --- new.short Tue Nov 1 03:40:14 2005 *************** *** 8,10 **** ! == 203 tests, 11 stderr failures, 4 stdout failures ================= memcheck/tests/leak-tree (stderr) --- 8,10 ---- ! == 203 tests, 13 stderr failures, 6 stdout failures ================= memcheck/tests/leak-tree (stderr) *************** *** 19,20 **** --- 19,22 ---- none/tests/mremap2 (stdout) + none/tests/pth_blockedsig (stdout) + none/tests/pth_blockedsig (stderr) none/tests/sigstackgrowth (stdout) *************** *** 23,24 **** --- 25,28 ---- none/tests/stackgrowth (stderr) + none/tests/thread-exits (stdout) + none/tests/thread-exits (stderr) none/tests/x86/int (stderr) |
|
From: Nicholas N. <nj...@cs...> - 2005-11-01 16:44:00
|
On Tue, 1 Nov 2005, Tom Hughes wrote: > Nightly build on dunsmere ( athlon, Fedora Core 4 ) started at 2005-11-01 03:30:04 GMT > Results differ from 24 hours ago > > [...] > ================================================= > == Difference between 24 hours ago and now == > ================================================= > > *** old.short Tue Nov 1 03:35:14 2005 > --- new.short Tue Nov 1 03:40:14 2005 > *************** > *** 8,10 **** > > ! == 203 tests, 11 stderr failures, 4 stdout failures ================= > memcheck/tests/leak-tree (stderr) > --- 8,10 ---- > > ! == 203 tests, 13 stderr failures, 6 stdout failures ================= > memcheck/tests/leak-tree (stderr) > *************** > *** 19,20 **** > --- 19,22 ---- > none/tests/mremap2 (stdout) > + none/tests/pth_blockedsig (stdout) > + none/tests/pth_blockedsig (stderr) > none/tests/sigstackgrowth (stdout) > *************** > *** 23,24 **** > --- 25,28 ---- > none/tests/stackgrowth (stderr) > + none/tests/thread-exits (stdout) > + none/tests/thread-exits (stderr) > none/tests/x86/int (stderr) This machine exhibits a lot of test noise -- a number of tests fail and then work again for no apparent reason, and not just the common such ones (ie. 'tls' and 'yield'). Tom, any idea why? Nick |
|
From: Tom H. <to...@co...> - 2005-11-01 19:48:47
|
In message <Pin...@ch...>
Nicholas Nethercote <nj...@cs...> wrote:
> This machine exhibits a lot of test noise -- a number of tests fail and
> then work again for no apparent reason, and not just the common such ones
> (ie. 'tls' and 'yield'). Tom, any idea why?
I believe the main cause of this is that because the sysinfo page is
placed at a random address by the kernel it was occasionally placed
at the preferred load address of ld.so which then stopped us mapping
the interpreter.
What should happen in that case is that the interpreter is mapped at
a different address instead, and I have just committed a fix that
should achieve that.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Julian S. <js...@ac...> - 2005-11-01 20:25:35
|
On Tuesday 01 November 2005 19:48, Tom Hughes wrote: > In message <Pin...@ch...> > > Nicholas Nethercote <nj...@cs...> wrote: > > This machine exhibits a lot of test noise -- a number of tests fail and > > then work again for no apparent reason, and not just the common such ones > > (ie. 'tls' and 'yield'). Tom, any idea why? > > I believe the main cause of this is that because the sysinfo page is > placed at a random address by the kernel it was occasionally placed > at the preferred load address of ld.so which then stopped us mapping > the interpreter. > > What should happen in that case is that the interpreter is mapped at > a different address instead, and I have just committed a fix that > should achieve that. Both 'tls' and 'yield' are sensitive to scheduling. Yield figures out whether a spinloop doing 'rep nop's progresses more slowly than one that doesn't (and is a bit nonsensical). 'tls' I'm less clear about but I did look at it before and thought it might be susceptible to races. J |