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 signed-commits3 (ppc64 Li


From: cvstest
Subject: [Cvs-test-results] Nightly testing results for signed-commits3 (ppc64 Linux 2.6.5-7.97-pseries64)
Date: Sun, 26 Mar 2006 05:23:11 -0500

Nightly test results for Sun Mar 26 01:29:36 PST 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-signed-commits3/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: keywordname-init-6
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
28.38user 75.24system 27:43.81elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (13major+5168445minor)pagefaults 0swaps
PASS: keywordname-init-4
cvs update: [09:59:15] waiting for derekrprice's lock in 
/tmp/build-cvs-nightly-signed-commits3/cvs-sanity-signed-commits3/cvsroot/first-dir
cvs update: [09:59:45] obtained lock in 
/tmp/build-cvs-nightly-signed-commits3/cvs-sanity-signed-commits3/cvsroot/first-dir
cvs update: conflict: `file1' created independently by second party
C file1
cvs update: conflict: `file2' created independently by second party
C file2
exit status was 1
FAIL: keywordname-init-6
/bin/sh /home/users/d/de/derekrprice/cvs-nightly-signed-commits3/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: sshstdio-6
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
41.35user 100.47system 22:47.96elapsed 10%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (18major+7667624minor)pagefaults 0swaps
PASS: sshstdio-5
--- wrapper.dif 2006-03-26 10:22:34.375429127 +0000
+++ good.dif    2006-03-26 10:22:34.696509913 +0000
@@ -1026,5 +1026,3 @@
 aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa    
                                                                                
                                                                                
      <
 aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa    
                                                                                
                                                                                
      <
 aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa    
                                                                                
                                                                                
      <
-Write failed flushing stdout buffer.
-write stdout: Broken pipe
exit status was 1
FAIL: sshstdio-6




reply via email to

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