[Cvs-test-results] Testing results for cvs-nightly (i686 Linux 2.6.10-1.771_FC2smp)

[cvstest]

Nightly test results for Mon Oct 30 22:31:49 PST 2006
Linux x86-linux2.cf.sourceforge.net 2.6.10-1.771_FC2smp #1 SMP Mon Mar 28 
01:10:51 EST 2005 i686 i686 i386 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.)
/home/users/d/de/derekrprice/cvs-nightly/src/sanity.sh: line 30849: sdir/sfile: 
No such file or directory
FAIL: multiroot2-3
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
60.58user 133.06system 31:09.38elapsed 10%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (6major+5428721minor)pagefaults 0swaps
PASS: multiroot2-2
** expected: 


N dir1/file1
N dir1/sdir/sfile
N dir1/sdir/ssdir/ssfile
No conflicts created by this import
cvs import: Importing 
/var/local/tmp/build-cvs-nightly/cvs-sanity/root1/dir1/sdir
cvs import: Importing 
/var/local/tmp/build-cvs-nightly/cvs-sanity/root1/dir1/sdir/ssdir
** got: 


N dir1/file1
N dir1/sdir/ssdir/ssfile
No conflicts created by this import
cvs import: Importing 
/var/local/tmp/build-cvs-nightly/cvs-sanity/root1/dir1/sdir
cvs import: Importing 
/var/local/tmp/build-cvs-nightly/cvs-sanity/root1/dir1/sdir/ssdir
FAIL: multiroot2-3

/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
OK, all 3858 tests passed (1 test group skipped and 5 tests passed with 
warnings).
118.13user 240.91system 45:15.24elapsed 13%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2major+9264970minor)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 3711 tests passed (2 test groups skipped and 5 tests passed with 
warnings).
140.41user 300.02system 1:10:30elapsed 10%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+12273152minor)pagefaults 0swaps