From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/3] RFC: runner/resultgen: lower dmesg copied when size limit was exceeded
Date: Fri, 18 Aug 2023 21:22:00 +0200 [thread overview]
Message-ID: <20230818192203.75155-1-kamil.konieczny@linux.intel.com> (raw)
When dmesg kernel log exceed its limit then copy into
results.json only limited number of lines. Add also
possibility for compressing dmesg.txt after is was processed.
Bug: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/129
Previous RFC: https://patchwork.freedesktop.org/series/119630/
Cc: Petri Latvala <adrinael@adrinael.net>
Cc: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Kamil Konieczny (3):
runner/resultgen: limit dmesg added into results
runner/settings: add compressor option
runner/resultgen: compress dmesg if size limit hit
runner/resultgen.c | 146 +++++++++++++++++++++++++++++++++++++++------
runner/settings.c | 34 ++++++++++-
runner/settings.h | 1 +
3 files changed, 162 insertions(+), 19 deletions(-)
--
2.39.2
next 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 Kamil Konieczny [this message]
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 ` [igt-dev] [PATCH i-g-t 3/3] runner/resultgen: compress dmesg if size limit hit Kamil Konieczny
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-1-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