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.6-409-g453908c Date: Mon, 14 Nov 2011 14:29:00 -0000 [thread overview] Message-ID: <20111114142908.32424.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 453908cebeeef690013465d5c0872237919d1262 (commit) from 402c3d8d0d37d92a5a42690cefac58de2a0335ef (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 453908cebeeef690013465d5c0872237919d1262 Author: Mark Wielaard <mjw@redhat.com> Date: Mon Nov 14 15:26:52 2011 +0100 testsuite/systemtap.exelib/pthreadprobes.exp: Handle pthread_mutex_timedlock. pthreadprobes.exp tested pthread_mutex_timedlock but didn't handle the result which caused it to FAIL the mutex_timedlock_entry test each time. pthread_mutex_timedlock is called with a timeout of 1 second in a loop while the mutex is held by the other thread for about 5 seconds resulting in a couple of entries resulting in a ETIMEDOUT before it is actually acquired. Expect 2 till 6 tries before success. ----------------------------------------------------------------------- Summary of changes: testsuite/systemtap.exelib/pthreadprobes.exp | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-11-14 14:29 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=20111114142908.32424.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: 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).