Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 3/3] runner/resultgen: compress dmesg if size limit hit
Date: Fri, 18 Aug 2023 21:22:03 +0200	[thread overview]
Message-ID: <20230818192203.75155-4-kamil.konieczny@linux.intel.com> (raw)
In-Reply-To: <20230818192203.75155-1-kamil.konieczny@linux.intel.com>

If dmesg log size is exceeding its limit do compressing of it
with the help of external program, given in option --compress.

Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
---
 runner/resultgen.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/runner/resultgen.c b/runner/resultgen.c
index 0dc26b335..95b9eadca 100644
--- a/runner/resultgen.c
+++ b/runner/resultgen.c
@@ -1204,6 +1204,13 @@ static bool fill_from_dmesg(int fd, char *dirname,
 	g_regex_unref(re);
 	fclose(f);
 
+	if (limit && settings->compressor) {
+		char comp[2*PATH_MAX + 256];
+
+		snprintf(comp, sizeof(comp), "%s %s/%s/%s", settings->compressor, settings->results_path, dirname, "dmesg.txt");
+		system(comp);
+	}
+
 	return true;
 }
 
-- 
2.39.2

  parent reply	other threads:[~2023-08-18 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 19:22 [igt-dev] [PATCH i-g-t 0/3] RFC: runner/resultgen: lower dmesg copied when size limit was exceeded Kamil Konieczny
2023-08-18 19:22 ` [igt-dev] [PATCH i-g-t 1/3] runner/resultgen: limit dmesg added into results Kamil Konieczny
2023-08-18 19:22 ` [igt-dev] [PATCH i-g-t 2/3] runner/settings: add compressor option Kamil Konieczny
2023-08-18 19:22 ` Kamil Konieczny [this message]
2023-08-18 19:28 ` [igt-dev] ✗ Fi.CI.BUILD: failure for RFC: runner/resultgen: lower dmesg copied when size limit was exceeded 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=20230818192203.75155-4-kamil.konieczny@linux.intel.com \
    --to=kamil.konieczny@linux.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