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 (i686 Linux 2.6.18-1.


From: cvstest
Subject: [Cvs-test-results] Testing results for cvs-nightly (i686 Linux 2.6.18-1.2200.fc5)
Date: Fri, 24 Nov 2006 02:57:28 -0500

Nightly test results for Fri Nov 24 01:31:31 EST 2006
Linux courage.ximbiot.com 2.6.18-1.2200.fc5 #1 Sat Oct 14 16:59:26 EDT 2006 
i686 i686 i386 GNU/Linux

Please send questions/comments to address@hidden

/bin/sh /mnt/nethome/cvstest/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.)
FAIL: update-p-1
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
28.39user 59.28system 4:22.14elapsed 33%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+2289346minor)pagefaults 0swaps
PASS: import-quirks-4
cvs [import aborted]: sign program exited via signal 11
exit status was 1
FAIL: update-p-1

/bin/sh /mnt/nethome/cvstest/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.)
FAIL: join-20
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
51.64user 97.67system 7:56.49elapsed 31%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+3953206minor)pagefaults 0swaps
PASS: join-19
cvs checkout: scheduling addition from revision 1.1.2.1 of `first-dir/file1'.
sh: line 1: 25618 Segmentation fault      (core dumped) /usr/bin/gpg --verify 
"--textmode" --quiet -- "-" 
"/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/tmp/cvssVU6zR" 2>/dev/null
U first-dir/file2
cvs [checkout aborted]: failed to verify 
`/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/tmp/cvssVU6zR': exited with 
error code 139
exit status was 1
FAIL: join-20

/bin/sh /mnt/nethome/cvstest/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.)
IO error encountered -- skipping file deletion
FAIL: writeproxy-init-1
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [proxycheck] Error 1
Command exited with non-zero status 2
221.54user 447.35system 1:07:04elapsed 16%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (9major+18388629minor)pagefaults 0swaps
PASS: template-norcsinfo-7
cvs [init aborted]: sign program exited via signal 11
exit status was 1
FAIL: writeproxy-init-1




reply via email to

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