[Cvs-test-results] Testing results for cvs-nightly (i686 Linux 2.6.18-1.2798.fc6)

[cvstest]

Nightly test results for Thu Jan 18 01:30:17 EST 2007
Linux courage.ximbiot.com 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 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, use the -v option or try the command:
`tail -f check.log' from another window.)
OK, all 3649 tests passed (11 test groups skipped and 1 test passed with 
warnings).
103.59user 215.96system 31:54.32elapsed 16%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (21major+8841293minor)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, use the -v option or try the command:
`tail -f check.log' from another window.)
FAIL: multiroot-setup-7
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
167.63user 333.22system 37:25.66elapsed 22%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+13403808minor)pagefaults 0swaps
PASS: multiroot-setup-6
cvs commit: Examining .
cvs commit: Examining mod1-1
cvs commit: Examining mod1-2
cvs [commit aborted]: sign program exited via signal 11
exit status was 1
FAIL: multiroot-setup-7

/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, use the -v option or try the command:
`tail -f check.log' from another window.)
IO error encountered -- skipping file deletion
OK, all 3711 tests passed (2 test groups skipped and 5 tests passed with 
warnings).
224.05user 464.16system 57:29.61elapsed 19%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (6major+18767042minor)pagefaults 0swaps