[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, 25 Apr 2006 03:26:22 -0400 |
Nightly test results for Mon Apr 24 22:31:33 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, try the command: `tail -f check.log' from another window.)
OK, all 3614 tests passed (11 test groups skipped and 1 test passed with
warnings).
27.62user 67.23system 29:14.66elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+7130824minor)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, try the command: `tail -f check.log' from another window.)
Write failed flushing stdout buffer.
write stdout: Broken pipe
OK, all 3812 tests passed (1 test group skipped and 5 tests passed with
warnings).
47.20user 109.90system 35:32.98elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+11273091minor)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, try the command: `tail -f check.log' from another window.)
OK, all 3665 tests passed (2 test groups skipped and 6 tests passed with
warnings).
56.80user 137.10system 48:17.44elapsed 6%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+14569540minor)pagefaults 0swaps
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), postmaster, 2006/04/22
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/04/23
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/04/24
- [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/04/26
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/04/27
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/04/28
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/04/29
- [Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp), cvstest, 2006/04/30