From: Petri Latvala <petri.latvala@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>
Subject: [igt-dev] [PATCH i-g-t] runner: Make sure output is still collected when killing test due to taint
Date: Tue, 28 Jan 2020 13:48:01 +0200 [thread overview]
Message-ID: <20200128114801.12282-1-petri.latvala@intel.com> (raw)
If the kernel is tainted, it stays tainted, so make sure the execution
monitoring still reaches the output collectors and other fd change
handlers.
Reported-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
---
runner/executor.c | 45 +++++++++++++++++++++++++++++----------------
1 file changed, 29 insertions(+), 16 deletions(-)
diff --git a/runner/executor.c b/runner/executor.c
index 0927d1fd..ca9a12e3 100644
--- a/runner/executor.c
+++ b/runner/executor.c
@@ -759,28 +759,41 @@ static int monitor_output(pid_t child,
return -1;
}
- if (settings->abort_mask & ABORT_TAINT && tainted(&taints)) /* cancel children after a kernel OOPS */
- n = 0, intervals_left = 1;
+ /*
+ * If we're configured to care about taints, kill the
+ * test if there's a taint. But only if we didn't
+ * already kill it, and make sure we still process the
+ * fds select() marked for us.
+ */
+ if (settings->abort_mask & ABORT_TAINT &&
+ tainted(&taints) &&
+ killed == 0) {
+ if (settings->log_level >= LOG_LEVEL_NORMAL) {
+ outf("Killing the test because the kernel is tainted.\n");
+ fflush(stdout);
+ }
- if (n == 0) {
+ killed = SIGQUIT;
+ if (!kill_child(killed, child))
+ return -1;
+
+ /*
+ * Now continue the loop and let the
+ * dying child be handled normally.
+ */
+ timeout = 20;
+ watchdogs_set_timeout(120);
+ intervals_left = timeout_intervals = 1;
+ } else if (n == 0) {
if (--intervals_left)
continue;
switch (killed) {
case 0:
- /* If abort_mask doesn't have taint set, taints is still 0 here */
- if (!is_tainted(taints)) {
- show_kernel_task_state();
- if (settings->log_level >= LOG_LEVEL_NORMAL) {
- outf("Timeout. Killing the current test with SIGQUIT.\n");
-
- fflush(stdout);
- }
- } else {
- if (settings->log_level >= LOG_LEVEL_NORMAL) {
- outf("Killing the test because the kernel is tainted.\n");
- fflush(stdout);
- }
+ show_kernel_task_state();
+ if (settings->log_level >= LOG_LEVEL_NORMAL) {
+ outf("Timeout. Killing the current test with SIGQUIT.\n");
+ fflush(stdout);
}
killed = SIGQUIT;
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-01-28 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 11:48 Petri Latvala [this message]
2020-01-28 12:01 ` [igt-dev] [PATCH i-g-t] runner: Make sure output is still collected when killing test due to taint Chris Wilson
2020-01-28 15:30 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-28 15:56 ` Chris Wilson
2020-01-29 13:24 ` Petri Latvala
2020-01-29 13:28 ` Chris Wilson
2020-01-29 13:39 ` Petri Latvala
2020-01-29 22:06 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=20200128114801.12282-1-petri.latvala@intel.com \
--to=petri.latvala@intel.com \
--cc=igt-dev@lists.freedesktop.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