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 (x86_64 L


From: cvstest
Subject: [Cvs-test-results] Nightly testing results for signed-commits3 (x86_64 Linux 2.6.9-1.667smp)
Date: Thu, 12 Jan 2006 04:03:16 -0500

Nightly test results for Thu Jan 12 01:00:43 PST 2006
Linux amd64-linux1.sourceforge.net 2.6.9-1.667smp #1 SMP Tue Nov 2 15:09:11 EST 
2004 x86_64 x86_64 x86_64 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: basica-5
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
0.54user 0.60system 0:02.02elapsed 56%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2major+60560minor)pagefaults 0swaps
PASS: basica-4a
gpg: keyring 
`/tmp/build-cvs-nightly-signed-commits3/cvs-sanity-signed-commits3/home/.gnupg/secring.gpg'
 created
gpg: keyring 
`/tmp/build-cvs-nightly-signed-commits3/cvs-sanity-signed-commits3/home/.gnupg/pubring.gpg'
 created
gpg: no default secret key: secret key not available
gpg: signing failed: secret key not available
/tmp/build-cvs-nightly-signed-commits3/cvs-sanity-signed-commits3/cvsroot/first-dir/sdir/ssdir/ssfile,v
  <--  sdir/ssdir/ssfile
cvs [commit aborted]: sign program exited with error code 2
exit status was 1
FAIL: basica-5
/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.)
FAIL: basica-5
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
0.63user 0.76system 0:02.88elapsed 48%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+77637minor)pagefaults 0swaps
PASS: basica-4a
gpg: keyring 
`/tmp/build-cvs-nightly-signed-commits3/cvs-sanity-signed-commits3/home/.gnupg/secring.gpg'
 created
gpg: keyring 
`/tmp/build-cvs-nightly-signed-commits3/cvs-sanity-signed-commits3/home/.gnupg/pubring.gpg'
 created
gpg: no default secret key: secret key not available
gpg: signing failed: secret key not available
cvs [commit aborted]: sign program exited with error code 2
exit status was 1
FAIL: basica-5




reply via email to

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