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 (i686 Linux 2.6.10-1.


From: cvstest
Subject: [Cvs-test-results] Testing results for cvs-nightly (i686 Linux 2.6.10-1.771_FC2smp)
Date: Sat, 23 Dec 2006 03:46:37 -0500

Nightly test results for Fri Dec 22 22:31:40 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.)
OK, all 3649 tests passed (11 test groups skipped and 1 test passed with 
warnings).
60.24user 126.69system 30:34.05elapsed 10%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (4major+5641673minor)pagefaults 0swaps

/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).
112.85user 216.07system 36:59.86elapsed 14%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+9251387minor)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.)
FAIL: writeproxy-ssh-init-3
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [proxycheck] Error 1
Command exited with non-zero status 2
136.25user 287.31system 1:02:28elapsed 11%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (3major+12172545minor)pagefaults 0swaps
PASS: writeproxy-ssh-init-2
cvs [commit aborted]: received broken pipe signal
exit status was 1
FAIL: writeproxy-ssh-init-3




reply via email to

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