public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-112-g6179a37
Date: Thu, 15 Oct 2009 20:38:00 -0000	[thread overview]
Message-ID: <20091015203814.13206.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "systemtap: system-wide probe/trace tool".

The branch, master has been updated
       via  6179a370d89b073d19407ec3d29e5e890367582b (commit)
      from  f8a493892377692c1c8f60c38ee05ac1fa77a8ed (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 6179a370d89b073d19407ec3d29e5e890367582b
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Oct 15 21:55:16 2009 +0200

    Fix transok/tval-opt.stp testcase. Pick diffent function and non-empty block.
    
    This testcase succeeded just because the value being set couldn't be
    found. So the error message being compared was the same. Set -o pipefail
    to catch that case. On vta compiled kernels it failed because the optimizer
    turned { statement } into statement. So pick a function and argument which
    location can always be found and add an extra 'next' statement so the
    block isn't folded.
    
    * testsuite/transok/tval-opt.stp: Set -o pipefail. Add 'next' to make
      sure block isn't empty. Use "do_filp_open" and "mode".

-----------------------------------------------------------------------

Summary of changes:
 testsuite/transok/tval-opt.stp |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2009-10-15 20:38 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=20091015203814.13206.qmail@sourceware.org \
    --to=mark@sourceware.org \
    --cc=systemtap-cvs@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).