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: Tue, 7 Feb 2006 03:29:16 -0500

Nightly test results for Mon Feb 6 22:31:55 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).
54.79user 52.11system 29:27.00elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2982977major+1429713minor)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.
83.30user 76.76system 35:48.81elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (4345103major+2061547minor)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).
112.87user 180.24system 48:46.98elapsed 10%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (5754652major+2688311minor)pagefaults 0swaps




reply via email to

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