From: William Cohen <wcohen@redhat.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: Summary of nightly tests 20061009
Date: Mon, 09 Oct 2006 21:27:00 -0000 [thread overview]
Message-ID: <452ABE9F.1090206@redhat.com> (raw)
Look over the test results for the nightly testing. The tests are
looking fairly good, but the systemtap.sample/tcptest.exp fails
consistently on the various architectures.
-Will
FC5 i686
Kernel: Linux 2.6.17-1.2187_FC5 #1 Mon Sep 11 01:17:06 EDT 2006 i686 i686 i386
GNU/Linux
Testsuite summary of failed tests
FAIL:
/home/wcohen/stap_testing_200610090830/src/testsuite/systemtap.samples/tcptest.stp
shutdown (eof)
=== systemtap Summary ===
# of expected passes 226
# of unexpected failures 1
# of expected failures 103
# of unknown successes 2
# of known failures 3
# of untested testcases 1
# of unsupported tests 1
runtest completed at Mon Oct 9 04:53:19 2006
RHEL4 i686
Kernel: Linux 2.6.9-42.0.3.EL #1 Mon Sep 25 17:14:19 EDT 2006 i686 athlon i386
GNU/Linux
Testsuite summary of failed tests
FAIL:
/home/wcohen/stap_testing_200610090830/src/testsuite/systemtap.base/timers.stp
shutdown (eof)
FAIL:
/home/wcohen/stap_testing_200610090830/src/testsuite/systemtap.samples/tcptest.stp
shutdown (eof)
=== systemtap Summary ===
# of expected passes 225
# of unexpected failures 2
# of expected failures 103
# of unknown successes 2
# of known failures 3
# of untested testcases 1
# of unsupported tests 1
runtest completed at Mon Oct 9 04:51:46 2006
RHEL4 x86_64
Kernel: Linux 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64
x86_64 x86_64 GNU/Linux
Testsuite summary of failed tests
FAIL:
/home/wcohen/stap_testing_200610090830/src/testsuite/systemtap.samples/tcptest.stp
shutdown (eof)
FAIL: transport normal - relayfs (0)
=== systemtap Summary ===
# of expected passes 226
# of unexpected failures 2
# of expected failures 103
# of unknown successes 2
# of known failures 3
# of untested testcases 1
runtest completed at Mon Oct 9 04:48:50 2006
Rawhide i686
Kernel: Linux 2.6.18-1.2747.fc6PAE #1 SMP Fri Oct 6 18:14:45 EDT 2006 i686 i686
i386 GNU/Linux
Testsuite summary of failed tests
FAIL: absentstats (0 0)
FAIL:
/home/wcohen/stap_testing_200610090830/src/testsuite/systemtap.samples/tcptest.stp
shutdown (eof)
FAIL: transport fill staging buffer - relayfs (0)
=== systemtap Summary ===
# of expected passes 225
# of unexpected failures 3
# of expected failures 103
# of unknown successes 3
# of known failures 2
# of untested testcases 1
runtest completed at Mon Oct 9 05:32:39 2006
Rawhide x86_64
Kernel: Linux 2.6.18-1.2747.fc6 #1 SMP Fri Oct 6 17:57:42 EDT 2006 x86_64 x86_64
x86_64 GNU/Linux
Testsuite summary of failed tests
FAIL:
/home/wcohen/stap_testing_200610090830/src/testsuite/systemtap.samples/tcptest.stp
shutdown (eof)
=== systemtap Summary ===
# of expected passes 226
# of unexpected failures 1
# of expected failures 103
# of unknown successes 1
# of known failures 4
# of untested testcases 1
# of unsupported tests 1
runtest completed at Mon Oct 9 04:49:25 2006
next reply other threads:[~2006-10-09 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 21:27 William Cohen [this message]
2006-10-10 15:45 ` Frank Ch. Eigler
2006-10-13 14:01 ` William Cohen
[not found] <9AE298E00BCF7B469C04BE82FCE78B8701A07E0E@scsmsx414.amr.corp.intel.com>
2006-10-16 13:57 ` William Cohen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=452ABE9F.1090206@redhat.com \
--to=wcohen@redhat.com \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).