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


From: cvstest
Subject: [Cvs-test-results] Nightly testing results for TRUNK (i686 Linux 2.6.10-1.771_FC2smp)
Date: Wed, 22 Feb 2006 03:32:52 -0500

Nightly test results for Tue Feb 21 22:32:19 PST 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 3592 tests passed (11 test groups skipped).
41.95user 124.41system 29:50.36elapsed 9%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+4943655minor)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 3792 tests passed.
67.27user 185.18system 36:37.82elapsed 11%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+7627886minor)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 3626 tests passed (2 test groups skipped).
90.51user 245.57system 50:12.08elapsed 11%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+10431729minor)pagefaults 0swaps




reply via email to

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