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, 6 Feb 2006 04:31:29 -0500

Nightly test results for Sun Feb 5 22:32:00 PST 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 3592 tests passed (11 test groups skipped).
57.46user 54.14system 37:35.80elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2982938major+1441343minor)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.
87.44user 81.37system 48:19.23elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (4345175major+2074204minor)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).
118.72user 183.94system 1:21:17elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (5756110major+2711053minor)pagefaults 0swaps




reply via email to

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