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


From: cvstest
Subject: [Cvs-test-results] Nightly testing results for signed-commits2 (i686 Linux 2.6.10-1.771_FC2smp)
Date: Sat, 12 Nov 2005 05:07:29 -0500

Nightly test results for Sat Nov 12 01:51:04 PST 2005
Linux x86-linux2.cf.sourceforge.net 2.6.10-1.771_FC2smp #1 SMP Mon Mar 28 
01:10:51 EST 2005 i686 i686 i386 GNU/Linux

Please send questions/comments to address@hidden

/bin/sh /home/users/d/de/derekrprice/cvs-nightly-signed-commits2/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: basicb-5
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
2.49user 3.43system 0:32.63elapsed 18%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2major+135514minor)pagefaults 0swaps
PASS: basicb-4a
/var/local/tmp/build-cvs-nightly-signed-commits2/cvs-sanity-signed-commits2/cvsroot/first-dir/Emptydir/sfile1,v
  <--  Emptydir/sfile1
initial revision: 1.1
/var/local/tmp/build-cvs-nightly-signed-commits2/cvs-sanity-signed-commits2/cvsroot/first-dir/sdir2/sfile2,v
  <--  sdir2/sfile2
cvs [commit aborted]: sign program exited via signal 5
exit status was 1
FAIL: basicb-5
/bin/sh /home/users/d/de/derekrprice/cvs-nightly-signed-commits2/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.)
FAIL: dirs-1
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
22.81user 44.60system 5:41.42elapsed 19%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2major+1384231minor)pagefaults 0swaps
PASS: resurrection-15
cvs [import aborted]: sign program exited via signal 5
exit status was 1
FAIL: dirs-1




reply via email to

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