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 TRUNK (ppc64 Linux 2.6.5-


From: cvstest
Subject: [Cvs-test-results] Nightly testing results for TRUNK (ppc64 Linux 2.6.5-7.97-pseries64)
Date: Thu, 6 Apr 2006 03:26:50 -0400

Nightly test results for Wed Apr 5 22:32:09 PDT 2006
Linux openpower-linux1 2.6.5-7.97-pseries64 #1 SMP Fri Jul 2 14:21:59 UTC 2004 
ppc64 ppc64 ppc64 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, try the command: `tail -f check.log' from another window.)
/home/users/d/de/derekrprice/cvs-nightly/src/sanity.sh: line 25337: cd: 2: No 
such file or directory
rm: cannot remove `keywordname': No such file or directory
FAIL: cleanup: PWD != TESTDIR (`/tmp/build-cvs-nightly' != 
`/tmp/build-cvs-nightly/cvs-sanity')
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
19.91user 68.15system 27:35.08elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (7major+4771808minor)pagefaults 0swaps
PASS: keywordname-checkout-3
FAIL: cleanup: PWD != TESTDIR (`/tmp/build-cvs-nightly' != 
`/tmp/build-cvs-nightly/cvs-sanity')
/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
FAIL: server-23
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
32.44user 116.96system 35:19.15elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (14major+7772761minor)pagefaults 0swaps
PASS: server-22
** expected: 
E Fatal server error, aborting\.
error ETIMEOUT Connection timed out\.
** got: 
FAIL: server-23
/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.)
FAIL: server-23
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [proxycheck] Error 1
Command exited with non-zero status 2
44.49user 146.34system 48:42.79elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (16major+10770450minor)pagefaults 0swaps
PASS: server-22
** expected: 
E Fatal server error, aborting\.
error ETIMEOUT Connection timed out\.
** got: 
FAIL: server-23




reply via email to

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