public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "craig.ringer at 2ndquadrant dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/27185] New: Reduce code duplication in conversions stress tests
Date: Fri, 15 Jan 2021 01:53:57 +0000	[thread overview]
Message-ID: <bug-27185-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=27185

            Bug ID: 27185
           Summary: Reduce code duplication in conversions stress tests
           Product: systemtap
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: systemtap at sourceware dot org
          Reporter: craig.ringer at 2ndquadrant dot com
  Target Milestone: ---

Created attachment 13119
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13119&action=edit
conversions.exp test enhancements

Hi

I've adjusted the stress tests referenced in
testsuite/systemtap.stress/conversions.exp to make them more concise and allow
all the test definitions to be shared across each variant.

It should be practical to further condense them by extracting the common part
into a shared file to include in each tapset and reusing the macros. But I
haven't bothered with that. At least now if you update the tests, you can just
copy/paste the new or changed test lines to all of conversions.stp,
conversions_trace.stp, conversions_profile.stp, and conversions_perf.stp
without having to rewrite everything in each one.

I also added unique probe identifiers to each one, so that on failure it's
possible to tell which test failed.

There's also now validation of whether a specific function call throws an error
that aborts the probe body or not. If something that should throw an error does
not, test output will be produced that lets you map that back to the specific
test case.

This is my first time using dejagnu and expect, but hopefully it's useful.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2021-01-15  1:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15  1:53 craig.ringer at 2ndquadrant dot com [this message]
2021-01-15  1:56 ` [Bug testsuite/27185] " craig.ringer at 2ndquadrant dot com
2021-01-16  0:11 ` fche at redhat dot com
2021-01-18  3:28 ` craig.ringer at 2ndquadrant 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-27185-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).