cvs-test-results
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Cvs-test-results] Testing results for cvs-nightly (ppc64 Linux 2.6.5-7.


From: cvstest
Subject: [Cvs-test-results] Testing results for cvs-nightly (ppc64 Linux 2.6.5-7.97-pseries64)
Date: Fri, 28 Apr 2006 03:28:14 -0400

Nightly test results for Thu Apr 27 22:31:28 PDT 2006
Linux openpower-linux1 2.6.5-7.97-pseries64 #1 SMP Fri Jul 2 14:21:59 UTC 2004 
ppc64 ppc64 ppc64 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 3614 tests passed (11 test groups skipped and 1 test passed with 
warnings).
32.55user 81.03system 29:31.19elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (7major+6165717minor)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 3812 tests passed (1 test group skipped and 5 tests passed with 
warnings).
54.15user 131.38system 35:50.01elapsed 8%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+9654780minor)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 3665 tests passed (2 test groups skipped and 6 tests passed with 
warnings).
64.87user 154.79system 49:04.38elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+12728062minor)pagefaults 0swaps




reply via email to

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