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 (i686 Linux 2.6.10-1.


From: cvstest
Subject: [Cvs-test-results] Testing results for cvs-nightly (i686 Linux 2.6.10-1.771_FC2smp)
Date: Sun, 7 May 2006 03:33:17 -0400

Nightly test results for Sat May 6 22:31:29 PDT 2006
Linux x86-linux2.cf.sourceforge.net 2.6.10-1.771_FC2smp #1 SMP Mon Mar 28 
01:10:51 EST 2005 i686 i686 i386 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).
59.26user 122.40system 29:38.95elapsed 10%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (6major+5570519minor)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).
104.24user 198.55system 36:24.01elapsed 13%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+9066404minor)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).
126.00user 258.22system 51:51.75elapsed 12%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+11878804minor)pagefaults 0swaps




reply via email to

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