From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] [PATCH] tst_test: Fail the test subprocess cannot be killed
Date: Wed, 27 Jun 2018 15:44:30 +0200 [thread overview]
Message-ID: <20180627134430.GA32300@rei> (raw)
In-Reply-To: <937810331.29259972.1530105689475.JavaMail.zimbra@redhat.com>
Hi!
> Looks good to me.
>
> I'm thinking if we shouldn't also try to gather some data
> that would help person looking at the logs. For example:
> collect /proc/<pid>/stack output or trigger sysrq-t or sysrq-w.
I guess that we can search for a process whoose process group matches
our test pid then dump the stack into a log, I will look into that.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2018-06-27 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 12:36 [LTP] [RFC] [PATCH] tst_test: Fail the test subprocess cannot be killed Cyril Hrubis
2018-06-27 13:21 ` Jan Stancek
2018-06-27 13:44 ` Cyril Hrubis [this message]
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=20180627134430.GA32300@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.