[Cvs-test-results] Nightly testing results for TRUNK (x86_64 Linux 2.6.9-1.667smp)

[cvstest]

Nightly test results for Wed Mar 29 22:32:02 PST 2006
Linux amd64-linux1.sourceforge.net 2.6.9-1.667smp #1 SMP Tue Nov 2 15:09:11 EST 
2004 x86_64 x86_64 x86_64 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).
21.73user 83.97system 29:41.42elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+6444995minor)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
34.16user 122.83system 35:03.03elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+9363806minor)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
44.03user 158.37system 47:53.46elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+12612589minor)pagefaults 0swaps
PASS: server-22
** expected: 
E Fatal server error, aborting\.
error ETIMEOUT Connection timed out\.
** got: 
FAIL: server-23