cvs-test-results
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Cvs-test-results] Testing results for cvs-nightly-cvs1-11-x-branch (x86


From: cvstest
Subject: [Cvs-test-results] Testing results for cvs-nightly-cvs1-11-x-branch (x86_64 Linux 2.6.9-1.667smp)
Date: Mon, 16 Oct 2006 04:30:35 -0400

Nightly test results for Mon Oct 16 00:31:16 PDT 2006
Linux amd64-linux1.sourceforge.net 2.6.9-1.667smp #1 SMP Tue Nov 2 15:09:11 EST 
2004 x86_64 x86_64 x86_64 GNU/Linux

Please send questions/comments to address@hidden

/bin/sh /home/users/d/de/derekrprice/cvs-nightly-cvs1-11-x-branch/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.)
FAIL: multiroot-setup-5
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
17.11user 54.37system 26:51.81elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (3major+5519417minor)pagefaults 0swaps
PASS: multiroot-setup-4
** expected: 
Directory 
/tmp/build-cvs-nightly-cvs-nightly-cvs1-11-x-branch/cvs-sanity/root1/mod1-1 
added to the repository
Directory 
/tmp/build-cvs-nightly-cvs-nightly-cvs1-11-x-branch/cvs-sanity/root1/mod1-2 
added to the repository
** got: 
Directory 
/tmp/build-cvs-nightly-cvs-nightly-cvs1-11-x-branch/cvs-sanity/root1/mod1-1 
added to the repository
Directory 
/tmp/build-cvs-nightly-cvs-nightly-cvs1-11-x-branch/cvs-sanity/root1/mod1-2 
added to the repository
FAIL: multiroot-setup-5

/bin/sh /home/users/d/de/derekrprice/cvs-nightly-cvs1-11-x-branch/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 3221 tests passed.
25.40user 79.07system 30:56.81elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+8048873minor)pagefaults 0swaps

make: *** No rule to make target `proxycheck'.  Stop.
Command exited with non-zero status 2
0.05user 0.00system 0:00.07elapsed 87%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+542minor)pagefaults 0swaps
cp: cannot stat `check.log': No such file or directory
rm: cannot remove `check.log': No such file or directory




reply via email to

[Prev in Thread] Current Thread [Next in Thread]