[Cvs-test-results] Nightly testing results for TRUNK (alpha Linux 2.2.20)

[cvstest]

Nightly test results for Fri Feb 24 22:32:08 PST 2006
Linux usf-cf-alpha-linux-1 2.2.20 #2 Wed Mar 20 19:57:28 EST 2002 alpha unknown

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.)
FAIL: admin-22-o7
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
39.93user 47.82system 28:30.58elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2479765major+1349808minor)pagefaults 0swaps
PASS: admin-22-o6
** expected: 
/tmp/build-cvs-nightly/cvs-sanity/cvsroot/first-dir/aaa,v  <--  aaa
new revision: 1\.6; previous revision: 1\.5
** got: 
FAIL: admin-22-o7
/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
OK, all 3792 tests passed.
69.60user 82.77system 37:17.74elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (3911820major+2106857minor)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, try the command: `tail -f check.log' from another window.)
OK, all 3626 tests passed (2 test groups skipped).
88.41user 177.18system 48:32.07elapsed 9%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (5194016major+2706281minor)pagefaults 0swaps