public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: dsmith@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-103-ga025188 Date: Mon, 03 May 2010 18:53:00 -0000 [thread overview] Message-ID: <20100503185319.28158.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 a0251889200706a6cf69183d1dc4e405ed78a0b1 (commit) from 45f22557531cb0fb1273c0bd9414100c44d8faf8 (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 a0251889200706a6cf69183d1dc4e405ed78a0b1 Author: David Smith <dsmith@redhat.com> Date: Mon May 3 13:52:54 2010 -0500 Move failing nfs test to its own testcase. * testsuite/buildok/nfs-detailed.stp: Move nfs.fop.check_flags test to nfs-fop.check_flags.stp (since it fails on RHEL5 and would mask other nfs test failures). * testsuite/buildok/nfs-fop.check_flags.stp: New test. * testsuite/systemtap.pass1-4/buildok.exp: Kfail nfs-fop.check_flags.stp. ----------------------------------------------------------------------- Summary of changes: testsuite/buildok/nfs-detailed.stp | 4 +--- ...ite_shared_copy.stp => nfs-fop.check_flags.stp} | 7 +++---- testsuite/systemtap.pass1-4/buildok.exp | 2 ++ 3 files changed, 6 insertions(+), 7 deletions(-) copy testsuite/buildok/{memory-write_shared_copy.stp => nfs-fop.check_flags.stp} (55%) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-05-03 18:53 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=20100503185319.28158.qmail@sourceware.org \ --to=dsmith@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: linkBe 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).