public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: serhei@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-244-g62f3f43
Date: Tue, 22 May 2012 17:36:00 -0000 [thread overview]
Message-ID: <20120522173647.29771.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 62f3f43e440a91768834954dc8ca5817b2b1c2ee (commit)
from a6200d2d52b919f24d5b78575378fb2cf4c2e33e (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 62f3f43e440a91768834954dc8ca5817b2b1c2ee
Author: Serguei Makarov <smakarov@redhat.com>
Date: Tue May 22 12:17:17 2012 -0400
Basic test cases for primitive probe points defined in tapset-netfilter.cxx.
These are all ok/ko type build tests. Tests for actual use of the
functionality will be committed together with an improved netfilter.stp.
The failure of buildok/netfilter02.stp is currently due to a known bug
involving the definition of multiple netfilter probe points.
-----------------------------------------------------------------------
Summary of changes:
testsuite/buildok/netfilter01.stp | 7 +++++++
testsuite/buildok/netfilter02.stp | 6 ++++++
testsuite/buildok/netfilter03.stp | 4 ++++
testsuite/buildok/netfilter04.stp | 3 +++
testsuite/semko/netfilter01.stp | 3 +++
testsuite/semko/netfilter02.stp | 3 +++
testsuite/semko/netfilter03.stp | 3 +++
testsuite/semko/netfilter04.stp | 3 +++
testsuite/semko/netfilter05.stp | 4 ++++
testsuite/semko/netfilter06.stp | 4 ++++
testsuite/semko/netfilter07.stp | 4 ++++
testsuite/semko/netfilter08.stp | 4 ++++
testsuite/semko/netfilter09.stp | 7 +++++++
testsuite/semko/netfilter10.stp | 6 ++++++
testsuite/semko/netfilter11.stp | 3 +++
testsuite/semok/netfilter01.stp | 4 ++++
16 files changed, 68 insertions(+), 0 deletions(-)
create mode 100755 testsuite/buildok/netfilter01.stp
create mode 100755 testsuite/buildok/netfilter02.stp
create mode 100755 testsuite/buildok/netfilter03.stp
create mode 100755 testsuite/buildok/netfilter04.stp
create mode 100755 testsuite/semko/netfilter01.stp
create mode 100755 testsuite/semko/netfilter02.stp
create mode 100755 testsuite/semko/netfilter03.stp
create mode 100755 testsuite/semko/netfilter04.stp
create mode 100755 testsuite/semko/netfilter05.stp
create mode 100755 testsuite/semko/netfilter06.stp
create mode 100755 testsuite/semko/netfilter07.stp
create mode 100755 testsuite/semko/netfilter08.stp
create mode 100755 testsuite/semko/netfilter09.stp
create mode 100755 testsuite/semko/netfilter10.stp
create mode 100755 testsuite/semko/netfilter11.stp
create mode 100755 testsuite/semok/netfilter01.stp
hooks/post-receive
--
systemtap: system-wide probe/trace tool
reply other threads:[~2012-05-22 17:36 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=20120522173647.29771.qmail@sourceware.org \
--to=serhei@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).