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.6-235-g0f79a69 Date: Tue, 20 Sep 2011 14:27:00 -0000 [thread overview] Message-ID: <20110920142712.14754.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 0f79a69995d11865cd6231ee15170ab82453426f (commit) from e13b5aba4d5fc678d58556b3e3faf74fea94eb47 (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 0f79a69995d11865cd6231ee15170ab82453426f Author: Frank Ch. Eigler <fche@redhat.com> Date: Tue Sep 20 10:21:09 2011 -0400 testsuite: add explicit timeouts to stap session With the previous code, it was possible for the delayedkill ./loop job to be killed before the stap script watching for its end got really ready. That could mean that the stap script starts, and waits, and waits, and waits more, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits yet more, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits a bit longer, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits more , and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and keeps waiting, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and goes on waiting, and waits, and waits a lot, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits for warts, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, now getting slightly impatient, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits, and waits a lot more. Since there is no robust synchronization in the test case, let's increase the delayedkill interval to make the above wait less likely, plus add a godot timeout probe that will abort the script before it gets grey hairs, loses its teeth, and gets bombarded with funeral pre-planning spam. ----------------------------------------------------------------------- Summary of changes: .../systemtap.unprivileged/unprivileged_myproc.exp | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-09-20 14:27 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=20110920142712.14754.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: 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).