From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/11414] New: nd_syscall.exp failures
Date: Sun, 21 Mar 2010 17:46:00 -0000 [thread overview]
Message-ID: <20100321174557.11414.mjw@redhat.com> (raw)
Some new syscalls were wired in and new testcases were added for bug #11406.
This exposed a couple of new failures for the nd_syscall cases. There are
currently the following failures:
Host: Linux fedora32.wildebeest.org 2.6.32.9-70.fc12.i686 #1 SMP Wed Mar 3
05:14:32 UTC 2010 i686 i686 i386 GNU/Linux
Snapshot: version 1.1/0.144 commit release-1.1-279-ga1ecf9f + changes
GCC: 4.4.3 [gcc (GCC) 4.4.3 20100127 (Red Hat 4.4.3-4)]
Distro: Fedora release 12 (Constantine)
Running /home/mark/src/systemtap/testsuite/systemtap.syscall/nd_syscall.exp ...
FAIL: 32-bit dup
FAIL: 32-bit eventfd
FAIL: 32-bit forkwait
FAIL: 32-bit inotify
FAIL: 32-bit mmap
FAIL: 32-bit net1
FAIL: 32-bit pipe
FAIL: 32-bit poll
FAIL: 32-bit signalfd
FAIL: 32-bit trunc
=== systemtap Summary ===
# of expected passes 25
# of unexpected failures 10
--
Summary: nd_syscall.exp failures
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mjw at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=11414
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2010-03-21 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 17:46 mjw at redhat dot com [this message]
2010-03-22 16:08 ` [Bug tapsets/11414] " dsmith at redhat dot com
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=20100321174557.11414.mjw@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--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).