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>,
Krzysztof Karas <krzysztof.karas@intel.com>
Subject: [PATCH i-g-t v2 0/4] runner: Allow limits at dumping dmesg
Date: Wed, 20 Nov 2024 19:32:04 +0100 [thread overview]
Message-ID: <20241120183208.146299-1-kamil.konieczny@linux.intel.com> (raw)
There are few 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. Also while at this
inform user when an actual disklimit occurred and correct one error
path.
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
v2: correct size in case of no disk limits used,
also correct one error path and inform user when an actual disk
limiting could affect what is written in log (Kamil)
Cc: Petri Latvala <adrinael@adrinael.net>
Cc: Karol Krol <karol.krol@intel.com>
Cc: Ewelina Musial <ewelina.musial@intel.com>
Cc: Krzysztof Karas <krzysztof.karas@intel.com>
Kamil Konieczny (4):
runner/executor: Check for error at writing dmesg dump
runner/executor: Limit reading dmesg to chunks
runner/executor: Fix error handling at terminating test
runner/executor: Inform about terminating
runner/executor.c | 107 +++++++++++++++++++++++++++++++++++++++-------
1 file changed, 92 insertions(+), 15 deletions(-)
--
2.47.0
next reply other threads:[~2024-11-20 18:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 18:32 Kamil Konieczny [this message]
2024-11-20 18:32 ` [PATCH i-g-t v2 1/4] runner/executor: Check for error at writing dmesg dump Kamil Konieczny
2024-11-27 6:09 ` Peter Senna Tschudin
2024-11-27 15:05 ` [i-g-t,v2,1/4] " Ryszard Knop
2024-11-29 19:31 ` [i-g-t, v2, 1/4] " Kamil Konieczny
2024-11-20 18:32 ` [PATCH i-g-t v2 2/4] runner/executor: Limit reading dmesg to chunks Kamil Konieczny
2024-11-27 15:12 ` [i-g-t,v2,2/4] " Ryszard Knop
2024-11-29 19:24 ` Kamil Konieczny
2024-11-20 18:32 ` [PATCH i-g-t v2 3/4] runner/executor: Fix error handling at terminating test Kamil Konieczny
2024-11-27 14:32 ` [i-g-t,v2,3/4] " Ryszard Knop
2024-11-20 18:32 ` [PATCH i-g-t v2 4/4] runner/executor: Inform about terminating Kamil Konieczny
2024-11-27 14:32 ` [i-g-t,v2,4/4] " Ryszard Knop
2024-11-20 19:52 ` ✓ Fi.CI.BAT: success for runner: Allow limits at dumping dmesg (rev2) Patchwork
2024-11-21 4:39 ` ✗ Xe.CI.Full: failure " Patchwork
2024-11-23 23:06 ` ✗ i915.CI.Full: " Patchwork
2024-11-26 11:54 ` [PATCH i-g-t v2 0/4] runner: Allow limits at dumping dmesg Sokolowski, Jan
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=20241120183208.146299-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 \
--cc=krzysztof.karas@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