[Top][All Lists]
[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: |
Tue, 31 Oct 2006 03:30:55 -0500 |
Nightly test results for Mon Oct 30 22:31:45 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.)
OK, all 3649 tests passed (11 test groups skipped and 1 test passed with
warnings).
27.94user 67.04system 30:08.38elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2major+7228349minor)pagefaults 0swaps
/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.15user 118.87system 35:54.98elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+11565188minor)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 6 tests passed with
warnings).
59.46user 145.13system 50:57.18elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+15064405minor)pagefaults 0swaps
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), (continued)
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/10/21
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/10/22
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/10/23
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/10/24
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/10/25
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/10/26
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/10/27
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/10/28
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/10/29
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/10/30
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp),
cvstest <=