[Cvs-test-results] Nightly testing results for TRUNK (i686 Linux 2.6.10-1.771_FC2smp)

[cvstest]

Nightly test results for Mon Apr 10 22:32:23 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 3605 tests passed (11 test groups skipped).
42.53user 122.85system 29:51.16elapsed 9%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+5029812minor)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
/home/users/d/de/derekrprice/cvs-nightly/src/sanity.sh: line 32579: 
firstdir/CVS/Repository: No such file or directory
FAIL: writeproxy-noredirect-7a
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
69.82user 191.10system 36:23.48elapsed 11%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+7690086minor)pagefaults 0swaps
PASS: writeproxy-noredirect-7
exit status was 1
FAIL: writeproxy-noredirect-7a
/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).
91.90user 250.98system 50:39.08elapsed 11%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+10578385minor)pagefaults 0swaps