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 (i686 Lin


From: cvstest
Subject: [Cvs-test-results] Nightly testing results for signed-commits3 (i686 Linux 2.6.8-2-386)
Date: Wed, 22 Mar 2006 07:42:58 -0500

Nightly test results for Wed Mar 22 03:51:15 PST 2006
Linux x86-linux1 2.6.8-2-386 #1 Thu May 19 17:40:50 JST 2005 i686 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: lockfiles-13
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
PASS: lockfiles-12
** expected: 
cvs commit: \[[0-9:]*\] waiting for derekrprice's lock in 
/tmp/build-cvs-nightly-signed-commits3/cvs-sanity-signed-commits3/cvsroot/first-dir/sdir/ssdir
cvs commit: \[[0-9:]*\] obtained lock in 
/tmp/build-cvs-nightly-signed-commits3/cvs-sanity-signed-commits3/cvsroot/first-dir/sdir/ssdir
/tmp/build-cvs-nightly-signed-commits3/cvs-sanity-signed-commits3/cvsroot/first-dir/sdir/ssdir/file1,v
  <--  first-dir/sdir/ssdir/file1
new revision: 1\.2; previous revision: 1\.1
** got: 
/tmp/build-cvs-nightly-signed-commits3/cvs-sanity-signed-commits3/cvsroot/first-dir/sdir/ssdir/file1,v
  <--  first-dir/sdir/ssdir/file1
new revision: 1.2; previous revision: 1.1
FAIL: lockfiles-13
/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
PASS: sshstdio-5
--- wrapper.dif 2006-03-22 12:41:11.305358813 +0000
+++ good.dif    2006-03-22 12:41:12.118195538 +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]