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 (alpha Linux 2.2.20


From: cvstest
Subject: [Cvs-test-results] Nightly testing results for TRUNK (alpha Linux 2.2.20)
Date: Mon, 10 Apr 2006 04:27:29 -0400

Nightly test results for Sun Apr 9 22:32:15 PDT 2006
Linux usf-cf-alpha-linux-1 2.2.20 #2 Wed Mar 20 19:57:28 EST 2002 alpha unknown

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).
47.65user 53.97system 37:47.17elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2696983major+1458568minor)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 3808 tests passed.
71.21user 79.61system 41:13.28elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (3941003major+2108510minor)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 3642 tests passed (2 test groups skipped).
95.47user 186.16system 1:23:50elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (5236229major+2706071minor)pagefaults 0swaps




reply via email to

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