public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: wcohen@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-516-g3a85fcc Date: Tue, 29 Nov 2011 20:42:00 -0000 [thread overview] Message-ID: <20111129204238.22363.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 3a85fccd0f9a41e90fefeda0f114b19f5acd38ec (commit) from fd887931c038de645663d9b1e0dafed7519fc437 (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 3a85fccd0f9a41e90fefeda0f114b19f5acd38ec Author: William Cohen <wcohen@redhat.com> Date: Tue Nov 29 15:38:11 2011 -0500 Mark buildok/memory-write_shared_copy.stp as KFAIL when it fails Kernels built with older versions of gcc do not have the needed argument information for inlined functions. vm.write_shared_copy probes inlined functions and suffers from PR1155 in this situation. This patch marks it as a KFAIL with a mention of PR1155 when it fails. ----------------------------------------------------------------------- Summary of changes: testsuite/lib/stap_buildok.exp | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-11-29 20:42 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=20111129204238.22363.qmail@sourceware.org \ --to=wcohen@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).