[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: |
Wed, 2 Aug 2006 03:30:07 -0400 |
Nightly test results for Tue Aug 1 22:31:38 PDT 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 3644 tests passed (11 test groups skipped and 1 test passed with
warnings).
28.46user 75.11system 29:29.69elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2major+7215097minor)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 3846 tests passed (1 test group skipped and 5 tests passed with
warnings).
47.82user 116.38system 35:53.93elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+11449267minor)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 3699 tests passed (2 test groups skipped and 6 tests passed with
warnings).
58.31user 145.84system 50:50.26elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+14880156minor)pagefaults 0swaps
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/08/01
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp),
cvstest <=
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/08/03
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/08/04
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/08/05
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/08/06
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/08/07
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/08/08
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/08/09
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/08/10
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/08/11
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/08/12