Skip to contentSkip to conversation

tests/kms_cursor_legacy: reduce CI debug output

PATCH In review Jeevan B 2 participants 2 messages Oct 26

lore
Share & tools
lore

Jeevan B

author
#0 lore raw

PATCH 1/1 tests/kms_cursor_legacy: reduce CI debug output

Reduce CI output to avoid exceeding the runner's per-test limit.

---
 tests/kms_cursor_legacy.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
tests/kms_cursor_legacy.c +2 -1
index 62339855e..9c6b63cbd 100644
@@ -1888,7 +1888,8 @@ int igt_main()
 	};
 
 	igt_fixture() {
-		unsigned int debug_mask_if_ci = DRM_UT_KMS;
+		/* KMS debug logs can exceed the CI per-test output limit here. */
+		unsigned int debug_mask_if_ci = 0;
 		display.drm_fd = drm_open_driver_master(DRIVER_ANY);
 		kmstest_set_vt_graphics_mode();
 
Signature · 1 line
2.43.0
#1 lore raw

Hi Jeevan,

Quoted 28 lines

-----Original Message-----
From: igt-dev <[email protected]> On Behalf Of Jeevan B
Sent: Monday, October 26, 2026 3:15 PM
To: [email protected]
Cc: B, Jeevan <[email protected]>
Subject: [PATCH] tests/kms_cursor_legacy: reduce CI debug output

Reduce CI output to avoid exceeding the runner's per-test limit.

---
 tests/kms_cursor_legacy.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
tests/kms_cursor_legacy.c index renamed from tests/kms_cursor_legacy.c +0 -0

62339855e..9c6b63cbd 100644

tests/kms_cursor_legacy.c +1 -1
@@ -1888,7 +1888,8 @@ int igt_main()
 	};
 
 	igt_fixture() {
-		unsigned int debug_mask_if_ci = DRM_UT_KMS;
+		/* KMS debug logs can exceed the CI per-test output limit

here. */

tests/kms_cursor_legacy.c int igt_main() · line 1892

Quoted 1 line
tests/kms_cursor_legacy.c +1 -0
+		unsigned int debug_mask_if_ci = 0;

1. The library's update_debug_mask_if_ci() log message will be wrong. It will always print "reducing the DRM debug mask to 0x4". With this patch it sets 0, so CI logs will claim KMS debug is on when it isn't. Fix it in the same patch/series.

2. Please mention for which subtests (if any specific) this log reduction is applicable in commit message.

3. Rather than turning DRM debug logging off completely, have you tried a lower mask first, e.g., DRM_UT_CORE (0x1) or DRM_UT_DRIVER (0x2)?

	enum drm_debug_category {
		DRM_UT_CORE   = 1 << 0,
		DRM_UT_DRIVER = 1 << 1,
		DRM_UT_KMS    = 1 << 2,

If CORE or DRIVER keeps the output under the limit, we would still have some useful context in the logs.

Regards,
Pranay

Quoted 5 lines
tests/kms_cursor_legacy.c +0 -1
 		display.drm_fd = drm_open_driver_master(DRIVER_ANY);
 		kmstest_set_vt_graphics_mode();
 
--

2.43.0