[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 Tue Nov 7 00:31:05 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-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: stamps-5
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
14.26user 47.16system 19:35.72elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+4706375minor)pagefaults 0swaps
PASS: stamps-4kw
** expected: 
RCS file: 
/tmp/build-cvs-nightly-cvs-nightly-cvs1-11-x-branch/cvs-sanity/cvsroot/first-dir/aa,v
done
Checking in aa;
/tmp/build-cvs-nightly-cvs-nightly-cvs1-11-x-branch/cvs-sanity/cvsroot/first-dir/aa,v
  <--  aa
initial revision: 1\.1
done
RCS file: 
/tmp/build-cvs-nightly-cvs-nightly-cvs1-11-x-branch/cvs-sanity/cvsroot/first-dir/kw,v
done
Checking in kw;
/tmp/build-cvs-nightly-cvs-nightly-cvs1-11-x-branch/cvs-sanity/cvsroot/first-dir/kw,v
  <--  kw
initial revision: 1\.1
done
** got: 
FAIL: stamps-5

/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.
write stdout: Broken pipe
OK, all 3221 tests passed.
25.49user 77.82system 30:58.89elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+8034186minor)pagefaults 0swaps

make: *** No rule to make target `proxycheck'.  Stop.
Command exited with non-zero status 2
0.05user 0.00system 0:00.06elapsed 92%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