From: "naresh.kamboju at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/15964] poll_map.exp testcase timeout on ARM
Date: Wed, 18 Sep 2013 06:58:00 -0000 [thread overview]
Message-ID: <bug-15964-6586-8LtiR1oVD9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15964-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15964
--- Comment #3 from Naresh Kamboju <naresh.kamboju at linaro dot org> ---
Running ./systemtap.base/poll_map.exp ...
FAIL: poll_map (timeout)(In reply to David Smith from comment #2)
> Hmm, it is possible we need to kill the running systemtap when we get a
> timeout. Can you try the following (untested) patch?
>
> diff --git a/testsuite/systemtap.base/poll_map.exp
> b/testsuite/systemtap.base/poll_map.exp
> index 85687b6..228cc9d 100644
> --- a/testsuite/systemtap.base/poll_map.exp
> +++ b/testsuite/systemtap.base/poll_map.exp
> @@ -6,7 +6,10 @@ set ok 0
> expect {
> -timeout 400
> -ex "SUCCESS" { incr ok }
> - timeout { fail "$test (timeout)" }
> + timeout {
> + fail "$test (timeout)"
> + exec kill -INT -[exp_pid]
> + }
> eof { }
> }
> catch { close }
After applying above patch no difference in results.
Running ./systemtap.base/poll_map.exp ...
FAIL: poll_map (timeout)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-09-18 6:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 8:56 [Bug testsuite/15964] New: " naresh.kamboju at linaro dot org
2013-09-17 9:11 ` [Bug testsuite/15964] " mjw at redhat dot com
2013-09-17 10:19 ` wcohen at redhat dot com
2013-09-17 13:29 ` dsmith at redhat dot com
2013-09-18 6:58 ` naresh.kamboju at linaro dot org [this message]
2017-10-11 10:44 ` mark at klomp dot org
2017-10-11 10:49 ` mjw at fedoraproject dot org
2024-02-13 18:59 ` wcohen at redhat dot com
2024-02-13 19:46 ` fche at redhat dot com
2024-02-13 19:57 ` wcohen at redhat dot com
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=bug-15964-6586-8LtiR1oVD9@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@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).