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 (x86_64 Linux 2.6.9-1


From: cvstest
Subject: [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp)
Date: Thu, 30 Nov 2006 03:30:11 -0500

Nightly test results for Wed Nov 29 22:31:33 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/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.)
mv: cannot stat `testcase07': No such file or directory
mv: cannot stat `testcase06': No such file or directory
mv: cannot stat `tmp': No such file or directory
FAIL: diffmerge1_yours
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
25.42user 65.46system 29:19.45elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2major+6708882minor)pagefaults 0swaps
PASS: diffmerge1_import
** expected: 
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/diffmerge1/testcase01,v  
<--  testcase01
new revision: 1\.1\.1\.1\.2\.1; previous revision: 1\.1\.1\.1
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/diffmerge1/testcase02,v  
<--  testcase02
new revision: 1\.1\.1\.1\.2\.1; previous revision: 1\.1\.1\.1
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/diffmerge1/testcase03,v  
<--  testcase03
new revision: 1\.1\.1\.1\.2\.1; previous revision: 1\.1\.1\.1
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/diffmerge1/testcase04,v  
<--  testcase04
new revision: 1\.1\.1\.1\.2\.1; previous revision: 1\.1\.1\.1
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/diffmerge1/testcase05,v  
<--  testcase05
new revision: 1\.1\.1\.1\.2\.1; previous revision: 1\.1\.1\.1
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/diffmerge1/testcase06,v  
<--  testcase06
new revision: 1\.1\.1\.1\.2\.1; previous revision: 1\.1\.1\.1
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/diffmerge1/testcase07,v  
<--  testcase07
new revision: 1\.1\.1\.1\.2\.1; previous revision: 1\.1\.1\.1
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/diffmerge1/testcase08,v  
<--  testcase08
new revision: 1\.1\.1\.1\.2\.1; previous revision: 1\.1\.1\.1
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/diffmerge1/testcase09,v  
<--  testcase09
new revision: 1\.1\.1\.1\.2\.1; previous revision: 1\.1\.1\.1
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/diffmerge1/testcase10,v  
<--  testcase10
new revision: 1\.1\.1\.1\.2\.1; previous revision: 1\.1\.1\.1
** got: 
FAIL: diffmerge1_yours

/bin/sh /home/users/d/de/derekrprice/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.)
Write failed flushing stdout buffer.
write stdout: Broken pipe
OK, all 3858 tests passed (1 test group skipped and 5 tests passed with 
warnings).
49.06user 116.41system 35:52.51elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+11592253minor)pagefaults 0swaps

/bin/sh /home/users/d/de/derekrprice/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.)
OK, all 3711 tests passed (2 test groups skipped and 5 tests passed with 
warnings).
58.86user 143.52system 50:57.00elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+15058565minor)pagefaults 0swaps




reply via email to

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