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

[cvstest]

Nightly test results for Thu Mar 30 22:32:11 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 and 1 test passed with 
warnings).
21.99user 85.83system 29:44.11elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+6446375minor)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: multiroot4-9
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
33.41user 121.76system 34:50.09elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+9132219minor)pagefaults 0swaps
PASS: multiroot4-8
** expected: 
cvs add: scheduling file .file2. for addition
cvs add: use .cvs commit. to add this file permanently
** got: 
cvs add: scheduling file `file2' for addition
FAIL: multiroot4-9
/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.13user 155.70system 48:08.03elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+12613455minor)pagefaults 0swaps
PASS: server-22
** expected: 
E Fatal server error, aborting\.
error ETIMEOUT Connection timed out\.
** got: 
FAIL: server-23