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

[cvstest]

Nightly test results for Wed Jul 5 22:31:30 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 3644 tests passed (11 test groups skipped and 1 test passed with 
warnings).
27.61user 68.15system 29:27.41elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+7216167minor)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
OK, all 3846 tests passed (1 test group skipped and 5 tests passed with 
warnings).
48.01user 109.84system 35:47.94elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+11451251minor)pagefaults 0swaps

/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 3699 tests passed (2 test groups skipped and 6 tests passed with 
warnings).
58.21user 139.98system 50:40.24elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+14889850minor)pagefaults 0swaps