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 (ppc64 Linux 2.6.5-


From: cvstest
Subject: [Cvs-test-results] Nightly testing results for TRUNK (ppc64 Linux 2.6.5-7.97-pseries64)
Date: Wed, 15 Mar 2006 03:29:44 -0500

Nightly test results for Tue Mar 14 22:32:53 PST 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 3605 tests passed (11 test groups skipped and 1 test passed with 
warnings).
22.68user 78.05system 29:45.63elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (5major+5493104minor)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 3805 tests passed.
33.70user 119.40system 35:44.75elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (13major+8017423minor)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 3639 tests passed (2 test groups skipped).
45.27user 145.40system 48:48.02elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (6major+11052432minor)pagefaults 0swaps




reply via email to

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