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.16-


From: cvstest
Subject: [Cvs-test-results] Nightly testing results for TRUNK (i686 Linux 2.6.16-1.2080_FC5)
Date: Thu, 20 Apr 2006 03:43:01 -0400

Nightly test results for Thu Apr 20 01:32:12 EDT 2006
Linux courage.ximbiot.com 2.6.16-1.2080_FC5 #1 Tue Mar 28 03:38:34 EST 2006 
i686 i686 i386 GNU/Linux

Please send questions/comments to address@hidden

/bin/sh /mnt/nethome/cvstest/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).
101.69user 234.41system 30:52.08elapsed 18%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (30major+7745362minor)pagefaults 0swaps
/bin/sh /mnt/nethome/cvstest/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.)
OK, all 3808 tests passed.
167.58user 365.72system 38:35.54elapsed 23%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (9major+12075344minor)pagefaults 0swaps
/bin/sh /mnt/nethome/cvstest/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.)
IO error encountered -- skipping file deletion
OK, all 3642 tests passed (2 test groups skipped).
213.21user 471.57system 54:57.12elapsed 20%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+15963536minor)pagefaults 0swaps




reply via email to

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