cvs-test-results
[Top][All Lists]
Advanced

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

[Cvs-test-results] Nightly testing results for TRUNK (x86_64 Linux 2.6.9


From: cvstest
Subject: [Cvs-test-results] Nightly testing results for TRUNK (x86_64 Linux 2.6.9-1.667smp)
Date: Tue, 14 Mar 2006 03:28:21 -0500

Nightly test results for Mon Mar 13 22:33:11 PST 2006
Linux amd64-linux1.sourceforge.net 2.6.9-1.667smp #1 SMP Tue Nov 2 15:09:11 EST 
2004 x86_64 x86_64 x86_64 GNU/Linux

Please send questions/comments to address@hidden

/bin/sh /home/users/d/de/derekrprice/cvs-nightly/src/sanity.sh `pwd`/cvs
This test should produce no other output than this message, and a final "OK".
(Note that the test can take an hour or more to run and periodically stops
for as long as one minute.  Do not assume there is a problem just because
nothing seems to happen for a long time.  If you cannot live without
running status, try the command: `tail -f check.log' from another window.)
OK, all 3605 tests passed (11 test groups skipped).
20.20user 62.41system 29:41.08elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+6464729minor)pagefaults 0swaps
/bin/sh /home/users/d/de/derekrprice/cvs-nightly/src/sanity.sh -r `pwd`/cvs
This test should produce no other output than this message, and a final "OK".
(Note that the test can take an hour or more to run and periodically stops
for as long as one minute.  Do not assume there is a problem just because
nothing seems to happen for a long time.  If you cannot live without
running status, try the command: `tail -f check.log' from another window.)
Write failed flushing stdout buffer.
write stdout: Broken pipe
OK, all 3805 tests passed.
32.77user 92.75system 35:49.82elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+9696625minor)pagefaults 0swaps
/bin/sh /home/users/d/de/derekrprice/cvs-nightly/src/sanity.sh -p `pwd`/cvs
This test should produce no other output than this message, and a final "OK".
(Note that the test can take an hour or more to run and periodically stops
for as long as one minute.  Do not assume there is a problem just because
nothing seems to happen for a long time.  If you cannot live without
running status, try the command: `tail -f check.log' from another window.)
OK, all 3639 tests passed (2 test groups skipped and 1 test passed with 
warnings).
42.10user 119.39system 47:50.99elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+12961054minor)pagefaults 0swaps




reply via email to

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