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: Mon, 10 Apr 2006 03:30:04 -0400

Nightly test results for Sun Apr 9 22:32:16 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 3605 tests passed (11 test groups skipped and 1 test passed with 
warnings).
22.85user 79.38system 29:50.40elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (9major+5505173minor)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 3808 tests passed.
34.27user 120.45system 36:15.84elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (21major+8042326minor)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 3642 tests passed (2 test groups skipped and 1 test passed with 
warnings).
45.69user 146.81system 49:15.98elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (6major+11091691minor)pagefaults 0swaps




reply via email to

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