[Cvs-test-results] CVS trunk testing results (HP HP-UX)

[Larry Jones]

Nightly test results for Fri Apr 20 21:39:05 EDT 2007
HP-UX hp291 B.11.00 U 9000/785 2007847090 unlimited-user license
  9:39pm  up 6 days,  9:52,  2 users,  load average: 1.06, 1.07, 1.06
 
        /bin/sh /u/scjones/cvs-nightly/src/sanity.sh `pwd`/cvs
WARNING: No working GPG was found.  This test suite will run, but
OpenPGP commit signatures will not be tested.
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 3673 tests passed (14 test groups skipped and 1 test passed with 
warnings).
        /bin/sh /u/scjones/cvs-nightly/src/sanity.sh -r `pwd`/cvs
WARNING: No working GPG was found.  This test suite will run, but
OpenPGP commit signatures will not be tested.
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.)
Error 0
cat: Cannot write to output.
No space left on device
cat: Cannot write to output.
No space left on device
cat: Cannot write to output.
No space left on device
cat: Cannot write to output.
FAIL: compression-2
*** Please see the `TESTS' and `check.log' files for more information.
*** Error exit code 1

Stop.
        /bin/sh /u/scjones/cvs-nightly/src/sanity.sh -p `pwd`/cvs
WARNING: No working GPG was found.  This test suite will run, but
OpenPGP commit signatures will not be tested.
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.)
Unable to test in proxy mode: unusable or no rsync found