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

[cvstest]

Nightly test results for Sat Apr 1 22:32:13 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 3605 tests passed (11 test groups skipped).
38.99user 113.46system 29:46.81elapsed 8%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+5042870minor)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
FAIL: server-23
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
61.59user 169.07system 35:17.94elapsed 10%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+7450106minor)pagefaults 0swaps
PASS: server-22
** expected: 
E Fatal server error, aborting\.
error ETIMEOUT Connection timed out\.
** got: 
FAIL: server-23
/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.)
FAIL: server-23
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [proxycheck] Error 1
Command exited with non-zero status 2
82.16user 224.94system 48:37.27elapsed 10%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+10292078minor)pagefaults 0swaps
PASS: server-22
** expected: 
E Fatal server error, aborting\.
error ETIMEOUT Connection timed out\.
** got: 
FAIL: server-23