From: David Wilder <dwilder@us.ibm.com>
To: systemtap@sourceware.org
Subject: S390x 4-21 Snapshot test results
Date: Thu, 26 Apr 2007 19:21:00 -0000 [thread overview]
Message-ID: <4631059E.3050402@us.ibm.com> (raw)
Hi-
Here is the test results from s390x testing of the 4-21 snapshot. The
results are exactly the same as last week.
Several changes that affected the results were checked in this week.
So, I have included the test results from a current CVS view (as of
yesterday).
** 4-21-2007 snapshot. **
=== systemtap Summary ===
# of expected passes 334
# of unexpected failures 11
# of expected failures 129
# of known failures 7
# of untested testcases 7
# of unsupported tests 2
FAIL: buildok/seventeen.stp - PR 4393
FAIL: systemtap.samples/lket(semantic error) - PR 3833
FAIL: profile (timeout)
FAIL: profile
FAIL: sysopen (0) - PR4329
FAIL: systemtap.stress/current.stp compilation - PR4331
FAIL: 64-bit signal - PR 4425
FAIL: 64-bit timer - PR 4391
FAIL: 32-bit alarm
FAIL: 32-bit mmap
FAIL: 32-bit signal - PR 4425
------------------------------------------
** Current CVS View- results **
=== systemtap Summary ===
# of expected passes 335
# of unexpected failures 8
# of expected failures 129
# of known failures 7
# of untested testcases 7
# of unsupported tests 2
FAIL: systemtap.base/add.stp startup (eof)
FAIL: buildok/seventeen.stp - PR 4393
FAIL: systemtap.samples/lket(semantic error) - PR 3833
FAIL: sysopen (0) - PR4329
FAIL: systemtap.stress/current.stp compilation - PR4331
FAIL: 64-bit signal - PR 4425
FAIL: 64-bit timer - PR 4391
FAIL: 32-bit signal - PR 4425
New Failures:
1) add.stp startup (eof) - insmod: error inserting
'/tmp/stapVEeORk/stap_21cc76dfd6ea0d48aa503522b351c8bc_493.ko': -1 File
exists^
2) 32-bit signal - PR 4425 - This test was not run last week. The
failure is cover under PR 4425 (same as 64-bit test) , so it is not a
new failure :)
--
David Wilder
IBM Linux Technology Center
Beaverton, Oregon, USA
dwilder@us.ibm.com
(503)578-3789
reply other threads:[~2007-04-26 19:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4631059E.3050402@us.ibm.com \
--to=dwilder@us.ibm.com \
--cc=systemtap@sourceware.org \
/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).