From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Petri Latvala <adrinael@adrinael.net>,
Karol Krol <karol.krol@intel.com>,
Ewelina Musial <ewelina.musial@intel.com>
Subject: [PATCH i-g-t 0/2] runner: Allow limits at dumping dmesg
Date: Fri, 18 Oct 2024 18:18:18 +0200 [thread overview]
Message-ID: <20241018161820.76014-1-kamil.konieczny@linux.intel.com> (raw)
There are two patches, first is a check for write error which could
happen at full disk, second is a revised solution to a problem with
dmesg dumping exeeding disk limit in runner.
Previous proposed solution: runner: check disk limit at dumping kmsg
https://patchwork.freedesktop.org/series/114353/
Gitlab issue: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/129
Cc: Petri Latvala <adrinael@adrinael.net>
Cc: Karol Krol <karol.krol@intel.com>
Cc: Ewelina Musial <ewelina.musial@intel.com>
Kamil Konieczny (2):
runner/executor: Check for error at writing dmesg dump
runner/executor: Limit reading dmesg to chunks
runner/executor.c | 65 +++++++++++++++++++++++++++++++++++++++--------
1 file changed, 55 insertions(+), 10 deletions(-)
--
2.47.0
next reply other threads:[~2024-10-18 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 16:18 Kamil Konieczny [this message]
2024-10-18 16:18 ` [PATCH i-g-t 1/2] runner/executor: Check for error at writing dmesg dump Kamil Konieczny
2024-10-24 13:45 ` Krzysztof Karas
2024-11-13 15:15 ` Kamil Konieczny
2024-10-18 16:18 ` [PATCH i-g-t 2/2] runner/executor: Limit reading dmesg to chunks Kamil Konieczny
2024-10-18 17:14 ` ✓ Fi.CI.BAT: success for runner: Allow limits at dumping dmesg Patchwork
2024-10-18 17:36 ` ✓ CI.xeBAT: " Patchwork
2024-10-18 18:50 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-10-19 8:41 ` ✗ CI.xeFULL: " 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=20241018161820.76014-1-kamil.konieczny@linux.intel.com \
--to=kamil.konieczny@linux.intel.com \
--cc=adrinael@adrinael.net \
--cc=ewelina.musial@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karol.krol@intel.com \
/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