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

[cvstest]

Nightly test results for Thu Aug 3 22:31:33 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 3644 tests passed (11 test groups skipped and 1 test passed with 
warnings).
34.32user 90.76system 30:46.97elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (41major+6282835minor)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
link_stat "/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/primary_cvsroot/." 
failed: No such file or directory
rsync error: some files could not be transferred (code 23) at main.c(633)
OK, all 3846 tests passed (1 test group skipped and 5 tests passed with 
warnings).
56.70user 149.00system 36:28.64elapsed 9%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (25major+9853440minor)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.)
OK, all 3699 tests passed (2 test groups skipped and 6 tests passed with 
warnings).
69.90user 174.93system 52:52.19elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (13major+13039013minor)pagefaults 0swaps