public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.5-140-g49909b5
Date: Tue, 19 Jul 2011 17:56:00 -0000	[thread overview]
Message-ID: <20110719175605.20719.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  49909b5572bc61c03cc80ef94f6d00dc5bbf665d (commit)
      from  31b3e2d32929afcbc4045721a28f76d3add84bc5 (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 49909b5572bc61c03cc80ef94f6d00dc5bbf665d
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Tue Jul 19 13:52:58 2011 -0400

    resolve PR12890 vs PR10854 bunfight
    
    The PR10854 test case uses a tight loop of staprun and a nexted loop
    of pkills, written in a way that counts on staprun's pre-PR12890
    "insert; unload; retry insert" module-handling heuristic.  With this
    heuristic gone (and error messages properly generated), the PR10854
    test case goes woozy and hangs in the while { ... pkill ... } tcl
    loop.  Now we don't loop in there any more.

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

Summary of changes:
 testsuite/systemtap.base/pr10854.exp |    8 +++++---
 1 files changed, 5 insertions(+), 3 deletions(-)


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


                 reply	other threads:[~2011-07-19 17:56 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=20110719175605.20719.qmail@sourceware.org \
    --to=fche@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).