[Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp)

[cvstest]

Nightly test results for Sat Oct 7 22:31:44 PDT 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, use the -v option or try the command:
`tail -f check.log' from another window.)
OK, all 3649 tests passed (11 test groups skipped and 1 test passed with 
warnings).
28.17user 70.41system 30:07.27elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+7226029minor)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, use the -v option or try the command:
`tail -f check.log' from another window.)
Write failed flushing stdout buffer.
write stdout: Broken pipe
FAIL: reserved-13c
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
43.77user 102.68system 33:57.88elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+10393787minor)pagefaults 0swaps
PASS: reserved-13b
exit status was 0
FAIL: reserved-13c

/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, use the -v option or try the command:
`tail -f check.log' from another window.)
OK, all 3711 tests passed (2 test groups skipped and 5 tests passed with 
warnings).
58.78user 141.15system 50:52.78elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+15046732minor)pagefaults 0swaps