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

[cvstest]

Nightly test results for Wed Sep 20 22:31:46 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 3649 tests passed (11 test groups skipped and 1 test passed with 
warnings).
33.72user 82.74system 30:25.28elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (6major+6337030minor)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
FAIL: head-4
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
47.46user 114.75system 32:44.68elapsed 8%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (4major+8363979minor)pagefaults 0swaps
PASS: head-3
** expected: 
T file1
T file2
** got: 
FAIL: head-4

/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 3711 tests passed (2 test groups skipped and 6 tests passed with 
warnings).
69.52user 168.37system 52:15.19elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (3major+13198871minor)pagefaults 0swaps