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

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

[Cvs-test-results] Nightly testing results for cvs1-11-x-branch (x86_64


From: cvstest
Subject: [Cvs-test-results] Nightly testing results for cvs1-11-x-branch (x86_64 Linux 2.6.9-1.667smp)
Date: Thu, 23 Mar 2006 04:15:09 -0500

Nightly test results for Thu Mar 23 00:27:13 PST 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, try the command: `tail -f check.log' from another window.)
FAIL: big-2
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
13.88user 41.85system 15:44.42elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+4593919minor)pagefaults 0swaps
PASS: big-1
** expected: 
cvs add: scheduling file .file1. for addition
cvs add: use .cvs commit. to add this file permanently
** got: 
cvs add: scheduling file `file1' for addition
cvs add: use 'cvs commit' to add this file permanently
FAIL: big-2
/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, try the command: `tail -f check.log' from another window.)
Write failed flushing stdout buffer.
write stdout: Broken pipe
OK, all 3189 tests passed.
25.01user 72.35system 30:50.14elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+7947393minor)pagefaults 0swaps




reply via email to

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