Limit repeated dmesg records in results
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | igt/runner: Refactor dmesg record bufferingrunner/ runner/ runner/ +1 more | +191 | 0 replies | |
| 2/2 | igt/runner: Add the rate limit feature for dmesg logs for runnerrunner/ runner/ | +2 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH i-g-t 0/2] Limit repeated dmesg records in results
From: "Thomas, Sobin" <[email protected]>
Repeated kernel messages can make results huge causing the test exit due to storage limitation. Add an optional --rate-limit N setting that keeps the first N consecutive identical dmesg records and summarizes the remaining occurrences. The default is 0, which preserves existing output.
Sobin Thomas (2):
igt/runner: Refactor dmesg record buffering igt/runner: Add the rate limit feature for dmesg logs for runner
runner/resultgen.c | 205 ++++++++++++++++++++++++++++++++---------- runner/runner_tests.c | 3 + runner/settings.c | 30 +++++++ runner/settings.h | 1 + 4 files changed, 191 insertions(+), 48 deletions(-)
Signature · 1 line
2.43.0