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: Fri, 17 Feb 2006 03:26:52 -0500

Nightly test results for Thu Feb 16 22:32:12 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 3592 tests passed (11 test groups skipped).
19.84user 62.92system 29:31.56elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+6400808minor)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 3792 tests passed.
31.89user 97.05system 35:32.75elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+9618553minor)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 3626 tests passed (2 test groups skipped and 1 test passed with 
warnings).
41.54user 123.22system 47:45.99elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+12879037minor)pagefaults 0swaps




reply via email to

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