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 cvs1-11-x-branch (alpha L


From: cvstest
Subject: [Cvs-test-results] Nightly testing results for cvs1-11-x-branch (alpha Linux 2.2.20)
Date: Sat, 18 Feb 2006 04:47:16 -0500

Nightly test results for Sat Feb 18 00:28:57 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-cvs1-11-x-branch/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 3184 tests passed.
35.64user 39.09system 26:33.76elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2279810major+1275486minor)pagefaults 0swaps
/bin/sh /home/users/d/de/derekrprice/cvs-nightly-cvs1-11-x-branch/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 3176 tests passed.
53.16user 62.27system 49:38.80elapsed 3%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (3101340major+1675633minor)pagefaults 0swaps




reply via email to

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