[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 Oct 3 00:30:32 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: tagdate-27-br2-t7
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
15.41user 51.25system 26:00.59elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+5094510minor)pagefaults 0swaps
PASS: tagdate-27-trunk-t7
** expected: 
cvs status: Examining first-dir-br2-t7
===================================================================
File: file1             Status: Up-to-date

   Working revision:    1\.1\.4\.2[^.]*
   Repository revision: 1\.1\.4\.2      
/tmp/build-cvs-nightly-cvs-nightly-cvs1-11-x-branch/cvs-sanity/cvsroot/first-dir/file1,v
   Sticky Tag:          br2 (branch: 1\.1\.4)
   Sticky Date:         (none)
   Sticky Options:      (none)

===================================================================
File: file3             Status: Up-to-date

   Working revision:    1\.1\.2\.1[^.]*
   Repository revision: 1\.1\.2\.1      
/tmp/build-cvs-nightly-cvs-nightly-cvs1-11-x-branch/cvs-sanity/cvsroot/first-dir/Attic/file3,v
   Sticky Tag:          br2 (branch: 1\.1\.2)
   Sticky Date:         (none)
   Sticky Options:      (none)
** got: 
cvs status: Examining first-dir-br2-t7
===================================================================
File: file1             Status: Up-to-date

   Working revision:    1.1.4.2 Tue Oct  3 07:57:18 2006
   Repository revision: 1.1.4.2 
/tmp/build-cvs-nightly-cvs-nightly-cvs1-11-x-branch/cvs-sanity/cvsroot/first-dir/file1,v
   Sticky Tag:          br2 (branch: 1.1.4)
   Sticky Date:         (none)
   Sticky Options:      (none)

===================================================================
File: file3             Status: Up-to-date

   Working revision:    1.1.2.1 Tue Oct  3 07:57:20 2006
   Repository revision: 1.1.2.1 
/tmp/build-cvs-nightly-cvs-nightly-cvs1-11-x-branch/cvs-sanity/cvsroot/first-dir/Attic/file3,v
   Sticky Tag:          br2 (branch: 1.1.2)
   Sticky Date:         (none)
   Sticky Options:      (none)

FAIL: tagdate-27-br2-t7

/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.35user 78.68system 30:55.60elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+8048913minor)pagefaults 0swaps

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