[Cvs-test-results] CVS trunk testing results (BSDI BSD/OS)

[Larry Jones]

CVS trunk test results for Sun Jul  7 21:29:01 EDT 2013
BSD/OS thor.ugs.com 4.2 BSDI BSD/OS 4.2 Kernel #5: Thu Jun 16 15:47:12 EDT 2005 
    address@hidden:/usr/src/sys/compile/THOR  i386
 9:29PM  up 1 day,  5:39, 0 user, load averages: 0.61, 0.58, 0.58
 
/bin/sh /u/scjones/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 3752 tests passed (12 test groups skipped and 1 test passed with 
warnings).
/bin/sh /u/scjones/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.)
OK, all 3955 tests passed (4 test groups skipped and 6 tests passed with 
warnings).
/bin/sh /u/scjones/cvs-nightly/src/sanity.sh -Br `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: join6-32
*** Please see the `TESTS' and `check.log' files for more information.
*** Error code 1

Stop.
/bin/sh /u/scjones/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: files-12r
*** Please see the `TESTS' and `check.log' files for more information.
*** Error code 1

Stop.