[Cvs-test-results] Testing results for cvs-nightly (ppc64 Linux 2.6.5-7.97-pseries64)

[cvstest]

Nightly test results for Wed Jun 14 22:41:24 PDT 2006
Linux openpower-linux1 2.6.5-7.97-pseries64 #1 SMP Fri Jul 2 14:21:59 UTC 2004 
ppc64 ppc64 ppc64 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 3642 tests passed (11 test groups skipped and 1 test passed with 
warnings).
32.56user 78.24system 29:38.56elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (3major+6308220minor)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 3844 tests passed (1 test group skipped and 5 tests passed with 
warnings).
54.02user 128.87system 36:28.14elapsed 8%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (3major+9807842minor)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.)
FAIL: conflicts4-11r
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [proxycheck] Error 1
Command exited with non-zero status 2
25.74user 60.64system 18:25.38elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2major+4902518minor)pagefaults 0swaps
PASS: conflicts4-10r
** expected: 
.*
Argument --
Directory .
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/first-dir
Entry /file1/1.2/+=//
Modified file1
u=.*,g=.*,o=.*
59
baseline
<<<<<<< file1
wibble1
=======
wibble2
>>>>>>> 1.2
update
** got: 
Root /tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/secondary_cvsroot
Valid-responses ok error Valid-requests Force-gzip Referrer Redirect Checked-in 
New-entry Checksum Copy-file Updated Created Update-existing Merged Patched 
Rcs-diff Mode Mod-time Removed Remove-entry Set-static-directory 
Clear-static-directory Set-sticky Clear-sticky Edit-file Template 
Clear-template Notified Module-expansion Wrapper-rcsOption M Mbinary E F MT 
Base-checkout Temp-checkout Base-copy Base-merge Base-entry Base-merged 
Base-diff Base-signatures Base-clear-signatures OpenPGP-signature
valid-requests
Global_option -q
Argument --
Directory .
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/secondary_cvsroot/first-dir
Entry /file1/1.2/+=//
Modified file1
u=rw,g=rw,o=r
59
baseline
<<<<<<< file1
wibble1
=======
wibble2
>>>>>>> 1.2
update
FAIL: conflicts4-11r