All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: pranay.samala@intel.com, Jeevan B <jeevan.b@intel.com>
Subject: [PATCH 1/3] tests/kms_cursor_legacy: reduce CI debug output
Date: Mon, 26 Oct 2026 22:48:34 +0530	[thread overview]
Message-ID: <20261026171836.1434992-2-jeevan.b@intel.com> (raw)
In-Reply-To: <20261026171836.1434992-1-jeevan.b@intel.com>

Use DRM_UT_CORE instead of DRM_UT_KMS in CI to reduce log volume while
retaining diagnostics. This applies to all subtests, including the
reported cursorA-vs-flipA-atomic-transitions case.

Log the actual debug mask instead of the hard-coded 0x4.
Intel CI output-limit validation is still pending.

Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/work_items/16961
Signed-off-by: Jeevan B <jeevan.b@intel.com>
---
 lib/igt_sysfs.c           | 3 ++-
 tests/kms_cursor_legacy.c | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/lib/igt_sysfs.c b/lib/igt_sysfs.c
index 9952c1c0d..873015bdc 100644
--- a/lib/igt_sysfs.c
+++ b/lib/igt_sysfs.c
@@ -537,7 +537,8 @@ void update_debug_mask_if_ci(unsigned int debug_mask_if_ci)
 	const char *ci_run = getenv("IGT_CI_RUN");
 
 	if (ci_run && ci_run[0] == '1') {
-		igt_debug("Currently under CI execution, reducing the DRM debug mask to 0x4\n");
+		igt_debug("Currently under CI execution, reducing the DRM debug mask to 0x%x\n",
+			  debug_mask_if_ci);
 		igt_drm_debug_mask_update(debug_mask_if_ci);
 	}
 }
diff --git a/tests/kms_cursor_legacy.c b/tests/kms_cursor_legacy.c
index 62339855e..5d8bcae9e 100644
--- a/tests/kms_cursor_legacy.c
+++ b/tests/kms_cursor_legacy.c
@@ -1888,7 +1888,8 @@ int igt_main()
 	};
 
 	igt_fixture() {
-		unsigned int debug_mask_if_ci = DRM_UT_KMS;
+		/* Keep CORE diagnostics without the high-volume KMS debug logs. */
+		unsigned int debug_mask_if_ci = DRM_UT_CORE;
 		display.drm_fd = drm_open_driver_master(DRIVER_ANY);
 		kmstest_set_vt_graphics_mode();
 
-- 
2.43.0


  reply	other threads:[~2026-10-26 17:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 17:18 [PATCH 0/3] reduce CI debug output Jeevan B
2026-10-26 17:18 ` Jeevan B [this message]
2026-10-26 17:18 ` [PATCH 2/3] tests/kms_plane_cursor: " Jeevan B
2026-10-26 17:18 ` [PATCH 3/3] tests/kms_rotation_crc: reduce multiplane " Jeevan B
2026-10-26 20:19 ` ✓ Xe.CI.BAT: success for reduce " Patchwork
2026-10-26 20:45 ` ✓ i915.CI.BAT: " Patchwork
2026-10-27  3:13 ` ✗ i915.CI.Full: failure " Patchwork
2026-10-27  3:25 ` ✗ 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=20261026171836.1434992-2-jeevan.b@intel.com \
    --to=jeevan.b@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=pranay.samala@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.