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


From: cvstest
Subject: [Cvs-test-results] Testing results for cvs-nightly (ppc64 Linux 2.6.5-7.97-pseries64)
Date: Sat, 29 Jul 2006 03:33:03 -0400

Nightly test results for Fri Jul 28 22:31:35 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, 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 30876: cd: 1a: No 
such file or directory
rm: cannot remove `1': No such file or directory
FAIL: cleanup: PWD != TESTDIR (`/tmp/build-cvs-nightly-cvs-nightly' != 
`/tmp/build-cvs-nightly-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
33.08user 82.63system 29:31.70elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (7major+6130626minor)pagefaults 0swaps
PASS: multiroot3-17
FAIL: cleanup: PWD != TESTDIR (`/tmp/build-cvs-nightly-cvs-nightly' != 
`/tmp/build-cvs-nightly-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, 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 3846 tests passed (1 test group skipped and 5 tests passed with 
warnings).
56.83user 138.45system 36:29.30elapsed 8%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (20major+9817563minor)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 3699 tests passed (2 test groups skipped and 6 tests passed with 
warnings).
70.06user 172.68system 52:29.11elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (24major+13043627minor)pagefaults 0swaps




reply via email to

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