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

[cvstest]

Nightly test results for Sun Oct 15 00:30:34 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-cvs1-11-x-branch/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.)
FAIL: sticky-19
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
14.68user 46.65system 24:43.77elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+4747925minor)pagefaults 0swaps
PASS: sticky-18
** expected: 
cvs update: file1 is no longer in the repository
cvs update: file2 is no longer in the repository
** got: 
cvs update: file1 is no longer in the repository
cvs update: file2 is no longer in the repository
FAIL: sticky-19

/bin/sh /home/users/d/de/derekrprice/cvs-nightly-cvs1-11-x-branch/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.
OK, all 3221 tests passed.
25.62user 75.91system 30:54.38elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+8023682minor)pagefaults 0swaps

make: *** No rule to make target `proxycheck'.  Stop.
Command exited with non-zero status 2
0.05user 0.00system 0:00.06elapsed 91%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+542minor)pagefaults 0swaps
cp: cannot stat `check.log': No such file or directory
rm: cannot remove `check.log': No such file or directory