From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/20600] parallet testsuite hang in [nd_]syscall.exp
Date: Thu, 15 Sep 2016 14:28:00 -0000 [thread overview]
Message-ID: <bug-20600-6586-68IuGIJn4n@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20600-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20600
--- Comment #1 from David Smith <dsmith at redhat dot com> ---
When this happens, it looks like stapio's parent gets set to expect:
[root@ibm-p8-01-lp7 rhel7-ppc64le]# ps -l 20631
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
4 Z 0 20631 3434 0 80 0 - 0 exit ? 0:03 [stapio]
<defunct>
[root@ibm-p8-01-lp7 rhel7-ppc64le]# ps -wl 3434
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
0 S 0 3434 3427 0 80 0 - 391 pipe_r ? 0:02 expect --
/usr/share/dejagnu/runtest.exp --tool systemtap --tool_opts --srcdir
/root/src/testsuite --outdir=artifacts/systemt
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-09-15 14:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 14:58 [Bug testsuite/20600] New: " dsmith at redhat dot com
2016-09-15 14:28 ` dsmith at redhat dot com [this message]
2016-09-15 19:40 ` [Bug testsuite/20600] " dsmith at redhat dot com
2016-09-15 19:53 ` [Bug testsuite/20600] parallel " dsmith at redhat dot com
2016-09-15 20:13 ` dsmith at redhat dot com
2016-09-22 14:26 ` dsmith at redhat dot com
2016-09-22 18:09 ` dsmith at redhat dot com
2017-02-28 16:13 ` dsmith at redhat dot com
2017-03-02 7:29 ` mcermak at redhat dot com
2017-03-03 19:17 ` dsmith at redhat dot com
2023-12-06 20:55 ` wcohen at redhat dot com
2024-02-21 13:25 ` fche 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-20600-6586-68IuGIJn4n@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).