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

[cvstest]

Nightly test results for Mon Mar 20 22:33:25 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.04user 62.00system 32:32.93elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+6461752minor)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: admin-22-o7
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
28.07user 77.10system 36:53.43elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+8551690minor)pagefaults 0swaps
PASS: admin-22-o6
** expected: 
/tmp/build-cvs-nightly/cvs-sanity/cvsroot/first-dir/aaa,v  <--  aaa
new revision: 1\.6; previous revision: 1\.5
** got: 
FAIL: admin-22-o7
/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 3639 tests passed (2 test groups skipped).
42.39user 118.17system 57:44.84elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+12962850minor)pagefaults 0swaps