From: Sobin Thomas <sobin.thomas@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: zbigniew.kempczynski@intel.com, Sobin Thomas <sobin.thomas@intel.com>
Subject: [PATCH i-g-t 2/2] igt/runner: Add the rate limit feature for dmesg logs for runner
Date: Mon, 5 Oct 2026 11:14:42 +0000 [thread overview]
Message-ID: <20261005111442.2755785-3-sobin.thomas@intel.com> (raw)
In-Reply-To: <20261005111442.2755785-1-sobin.thomas@intel.com>
Introduce --rate-limit N option to igt_runner to control the number
of duplicate identical dmesg records are kept in the results before
the remaining repeats are summarized. The default of 0 disables the
rate limiting.
This is introduced to limit the logs to prevent log truncation due to
size limit and test abort ocurring due to large dmesg logs.
Signed-off-by: Sobin Thomas <sobin.thomas@intel.com>
---
runner/settings.c | 2 +-
runner/settings.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/runner/settings.c b/runner/settings.c
index e6f8af358..62a4a17b3 100644
--- a/runner/settings.c
+++ b/runner/settings.c
@@ -279,7 +279,7 @@ static const char *usage_str =
" --use-watchdog Use hardware watchdog for lethal enforcement of the\n"
" above timeout. Killing the test process is still\n"
" attempted at timeout trigger.\n"
- " --rate-limit N Keep the first N consecutive identical dmesg records,\n"
+ " --rate-limit N Print the first N consecutive identical dmesg records,\n"
" then summarize repeats. 0 disables limiting (default).\n"
" --dmesg-warn-level <level>\n"
" Messages with log level equal or lower (more serious)\n"
diff --git a/runner/settings.h b/runner/settings.h
index 5d2bbf3e4..4bc00e824 100644
--- a/runner/settings.h
+++ b/runner/settings.h
@@ -77,7 +77,7 @@ struct settings {
char *results_path;
bool piglit_style_dmesg;
int dmesg_warn_level;
- int dmesg_rate_limit; /* 0 disables duplicate suppression */
+ int dmesg_rate_limit;
int prune_mode;
bool list_all;
char *code_coverage_script;
--
2.43.0
next prev parent reply other threads:[~2026-10-05 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 11:14 [PATCH i-g-t 0/2] Limit repeated dmesg records in results Sobin Thomas
2026-10-05 11:14 ` [PATCH i-g-t 1/2] igt/runner: Refactor dmesg record buffering Sobin Thomas
2026-10-05 11:14 ` Sobin Thomas [this message]
2026-10-05 11:57 ` ✓ i915.CI.BAT: success for Limit repeated dmesg records in results Patchwork
2026-10-05 12:06 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-05 14:54 ` ✗ i915.CI.Full: failure " Patchwork
2026-10-05 17:58 ` ✗ Xe.CI.FULL: " 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=20261005111442.2755785-3-sobin.thomas@intel.com \
--to=sobin.thomas@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@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