[PATCH i-g-t v3 0/3] runner: Allow limits at dumping dmesg

[Kamil Konieczny <kamil.konieczny@linux.intel.com>]

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)
v3: dropped patch 1/4 "Check for error at writing dmesg" (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>
Cc: Jan Sokolowski <jan.sokolowski@intel.com>
Cc: Ryszard Knop <rk@dragonic.eu>

Kamil Konieczny (3):
  runner/executor: Limit reading dmesg to chunks
  runner/executor: Fix error handling at terminating test
  runner/executor: Inform about terminating

 runner/executor.c | 78 +++++++++++++++++++++++++++++++++++++++--------
 1 file changed, 66 insertions(+), 12 deletions(-)

-- 
2.47.1