Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: himanshu.girotra@intel.com
To: igt-dev@lists.freedesktop.org
Cc: ramadevi.gandi@intel.com, priyanka.dandamudi@intel.com,
	kamil.konieczny@intel.com
Subject: [PATCH i-g-t] tests/intel/xe_exec_threads: ignore expected hang timeout
Date: Thu, 23 Jul 2026 08:02:51 +0530	[thread overview]
Message-ID: <20260723023251.4522-1-himanshu.girotra@intel.com> (raw)

From: Himanshu Girotra <himanshu.girotra@intel.com>

The hang subtests hang a queue and reset to recover. Jobs that were
queued but never started are logged by the KMD at warn level as
"Check job timeout: ... not started".

This warn is expected, but CI flags warn-level dmesg lines and fails
the subtest even though it passes. Whitelist it for the hang subtests.

v2: Rework description and comment to be generic (Priyanka,Kamil)

Signed-off-by: Himanshu Girotra <himanshu.girotra@intel.com>
---
 tests/intel/xe_exec_threads.c | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/tests/intel/xe_exec_threads.c b/tests/intel/xe_exec_threads.c
index 0480df779..2974fc312 100644
--- a/tests/intel/xe_exec_threads.c
+++ b/tests/intel/xe_exec_threads.c
@@ -1468,6 +1468,16 @@ static void threads(int fd, int flags)
 	pthread_barrier_destroy(&barrier);
 }
 
+/*
+ * Hang subtests reset the GPU to recover, so jobs that never started are
+ * logged as "Check job timeout: ... not started". This warn is expected;
+ * whitelist it to avoid spurious dmesg-warn failures in CI.
+ */
+static void ignore_multi_queue_hang_warnings_in_dmesg(void)
+{
+	igt_emit_ignore_dmesg_regex("Check job timeout: .*not started");
+}
+
 int igt_main()
 {
 	const struct section {
@@ -1735,6 +1745,9 @@ int igt_main()
 				igt_assert(!(s->flags & BALANCER));
 			}
 
+			if ((s->flags & MULTI_QUEUE) && (s->flags & HANG))
+				ignore_multi_queue_hang_warnings_in_dmesg();
+
 			threads(fd, s->flags);
 		}
 	}
-- 
2.50.1


             reply	other threads:[~2026-07-23  2:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  2:32 himanshu.girotra [this message]
2026-07-23  3:59 ` ✓ Xe.CI.BAT: success for tests/intel/xe_exec_threads: ignore expected hang timeout Patchwork
2026-07-23  4:04 ` [PATCH i-g-t] " Dandamudi, Priyanka
2026-07-23  4:18 ` ✓ i915.CI.BAT: success for " Patchwork
2026-07-23 14:25 ` [PATCH i-g-t] " Kamil Konieczny
2026-07-23 14:41   ` Girotra, Himanshu
2026-07-23 14:51     ` Kamil Konieczny
2026-07-24  2:13 ` ✓ Xe.CI.FULL: success for " Patchwork
2026-07-24  5:48 ` ✗ i915.CI.Full: failure " 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=20260723023251.4522-1-himanshu.girotra@intel.com \
    --to=himanshu.girotra@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@intel.com \
    --cc=priyanka.dandamudi@intel.com \
    --cc=ramadevi.gandi@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