From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/13158] New: rename_module.exp leaving module behind
Date: Tue, 06 Sep 2011 20:10:00 -0000 [thread overview]
Message-ID: <bug-13158-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13158
Bug #: 13158
Summary: rename_module.exp leaving module behind
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
AssignedTo: systemtap@sourceware.org
ReportedBy: dsmith@redhat.com
Classification: Unclassified
After the rename_module.exp testcase is run, it leaves a module behind:
------------------
# lsmod | fgrep stap
# make installcheck RUNTESTFLAGS='systemtap.base/rename_module.exp'
... stuff deleted ...
Host: Linux kvm-f15-64-1.usersys.redhat.com 2.6.40.3-0.fc15.x86_64.debug #1 SMP
Tue Aug 16 04:04:00 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Snapshot: version 1.7/0.152 commit release-1.6-171-gd354062 + changes
GCC: 4.6.0 [gcc (GCC) 4.6.0 20110603 (Red Hat 4.6.0-10)]
Distro: Fedora release 15 (Lovelock)
Running systemtap/src/testsuite/systemtap.base/rename_module.exp ...
=== systemtap Summary ===
# of expected passes 3
... stuff deleted ...
# lsmod | fgrep stap
stap_951b7d48fc8a19bff19415442ed9be4b_677 34009 0
------------------
This happens every time I run this test. The problem appears to be the 2nd
test in the testcase. Note that no staprun/stapio processes are left behind,
just the module itself.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-09-06 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 20:10 dsmith at redhat dot com [this message]
2011-09-07 11:26 ` [Bug testsuite/13158] " mjw at redhat dot com
2011-09-07 13:45 ` dsmith at redhat dot com
2011-09-07 17:40 ` dsmith at redhat dot com
2011-10-19 15:03 ` 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=bug-13158-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).