public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
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 2/3] runner: Dump the rest of dmesg also when child refuses to die
Date: Thu, 12 Mar 2020 11:59:43 +0200	[thread overview]
Message-ID: <20200312095944.7477-2-petri.latvala@intel.com> (raw)
In-Reply-To: <20200312095944.7477-1-petri.latvala@intel.com>

Signed-off-by: Petri Latvala <petri.latvala@intel.com>
---
 runner/executor.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/runner/executor.c b/runner/executor.c
index 28b8a443..790f99db 100644
--- a/runner/executor.c
+++ b/runner/executor.c
@@ -1054,6 +1054,10 @@ static int monitor_output(pid_t child,
 						     "but we didn't get informed of its demise...\n");
 				}
 
+				dump_dmesg(kmsgfd, outputs[_F_DMESG]);
+				if (settings->sync)
+					fdatasync(outputs[_F_DMESG]);
+
 				close_watchdogs(settings);
 				free(outbuf);
 				close(outfd);
-- 
2.20.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-03-12  9:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12  9:59 [igt-dev] [PATCH i-g-t 1/3] runner: Handle outputs before checking for timeout Petri Latvala
2020-03-12  9:59 ` Petri Latvala [this message]
2020-03-12  9:59 ` [igt-dev] [PATCH i-g-t 3/3] runner: Read all kernel logs when there are logs Petri Latvala
2020-03-12 10:09   ` Chris Wilson
2020-03-12 11:11 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/3] runner: Handle outputs before checking for timeout Patchwork
2020-03-12 11:52 ` Patchwork
2020-03-12 11:57 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-03-13  4:08 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20200312095944.7477-2-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