From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/16570] New: the syscall.exp and nd_syscall.exp testcases take too long
Date: Wed, 12 Feb 2014 18:55:00 -0000 [thread overview]
Message-ID: <bug-16570-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16570
Bug ID: 16570
Summary: the syscall.exp and nd_syscall.exp testcases take too
long
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
I've been adding more C testcases for the syscall/nd_syscall testsuite. I've
noticed that these testcases take a long time to run. On a recent debug x86_64
kernel, the syscall testsuite took over 38 minutes to run.
From some debugging, the majority of that time is spent compiling and
recompiling the test module. Even using a cached module, it takes a lot of time
to process the sys.stp/nd_sys.stp scripts since they probe every syscall.
Compiling the module once, then using staprun to load the resulting module
should speed these tests up.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-02-12 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 18:55 dsmith at redhat dot com [this message]
2014-02-12 19:01 ` [Bug testsuite/16570] " 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-16570-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).