[PATCH i-g-t v1 0/4] runner: check disk limits for dmesg

[Kamil Konieczny]

Some kernel or tests bugs can result in massive dmesg flooding.
It was recently reported by our CI was flooded with dmesg size
over 400MB, such big dumps are rearly needed for devs and are
rather a sign of a bug (like unlimited or circular prints).

Try to guard dmesg log reading at a lowest level and abort
testing in such case.

Cc: Karol Krol <karol.krol at intel.com>

Kamil Konieczny (4):
  runner/resultgen: limit dmesg added into results
  runner/executor: check disk limit at dumping kmsg
  HAX/DO_NOT_MERGE: tests/core_getversion: add dmesg flooding subtests
  HAX/DO_NO_MERGE: fast-feedback with flooding dmesg

 runner/executor.c                     |  19 ++-
 runner/resultgen.c                    |  84 ++++++++++---
 tests/core_getversion.c               |  63 ++++++++++
 tests/intel-ci/fast-feedback.testlist | 172 +-------------------------
 4 files changed, 151 insertions(+), 187 deletions(-)

-- 
2.43.0