[Cvs-test-results] Nightly testing results for TRUNK (ppc64 Linux 2.6.5-7.97-pseries64)

[cvstest]

Nightly test results for Wed Feb 8 22:32:01 PST 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, try the command: `tail -f check.log' from another window.)
OK, all 3592 tests passed (11 test groups skipped).
21.36user 76.21system 29:50.14elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (7major+5453757minor)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, try the command: `tail -f check.log' from another window.)
Write failed flushing stdout buffer.
write stdout: Broken pipe
FAIL: multiroot3-7
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
29.95user 107.77system 34:33.31elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+7441943minor)pagefaults 0swaps
PASS: multiroot3-5
** expected: 
Directory /tmp/build-cvs-nightly/cvs-sanity/root2/dir2 added to the repository
** got: 
Directory /tmp/build-cvs-nightly/cvs-sanity/root2/dir2 added to the repository
FAIL: multiroot3-7
/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, try the command: `tail -f check.log' from another window.)
OK, all 3626 tests passed (2 test groups skipped and 1 test passed with 
warnings).
44.06user 143.06system 48:52.04elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (3major+10972017minor)pagefaults 0swaps