From: Sk Anirban <sk.anirban@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, badal.nilawar@intel.com,
riana.tauro@intel.com, karthik.poosa@intel.com,
raag.jadav@intel.com, soham.purkait@intel.com,
mallesh.koujalagi@intel.com, kamil.konieczny@intel.com,
Sk Anirban <sk.anirban@intel.com>
Subject: [PATCH v2 0/2] tests/intel/xe_survivability: update ignored dmesg regex
Date: Wed, 15 Jul 2026 02:27:48 +0530 [thread overview]
Message-ID: <20260714205747.119025-4-sk.anirban@intel.com> (raw)
The kernel now reports -ENOTRECOVERABLE when the device is wedged.
As runtime-survivability deliberately wedges the device, update
dmesg regex so igt_runner does not treat the expected error logs
as failures.
v2: Keep older error codes (Kamil)
Modify regex (Kamil)
kernel implementation:
https://patchwork.freedesktop.org/series/168780/
Signed-off-by: Sk Anirban <sk.anirban@intel.com>
Sk Anirban (2):
tests/intel/xe_survivability: update ignored dmesg regex
HAX intel-ci: Add xe_survivability to xe-fast-feedback
tests/intel-ci/xe.fast-feedback.testlist | 1 +
tests/intel/xe_survivability.c | 21 +++++++++++++++++++--
2 files changed, 20 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-14 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 20:57 Sk Anirban [this message]
2026-07-14 20:57 ` [PATCH v2 1/2] tests/intel/xe_survivability: update ignored dmesg regex Sk Anirban
2026-07-14 20:57 ` [PATCH v2 2/2] HAX intel-ci: Add xe_survivability to xe-fast-feedback Sk Anirban
2026-07-14 22:04 ` ✗ i915.CI.BAT: failure for tests/intel/xe_survivability: update ignored dmesg regex (rev2) Patchwork
2026-07-14 22:11 ` ✗ Xe.CI.BAT: " Patchwork
2026-07-15 4:43 ` ✗ Xe.CI.FULL: " Patchwork
2026-07-15 17:32 ` ✗ Xe.CI.BAT: failure for tests/intel/xe_survivability: update ignored dmesg regex (rev3) Patchwork
2026-07-15 18:20 ` ✓ i915.CI.BAT: success " Patchwork
2026-07-15 21:25 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-07-16 0:05 ` ✗ i915.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=20260714205747.119025-4-sk.anirban@intel.com \
--to=sk.anirban@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@intel.com \
--cc=karthik.poosa@intel.com \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=soham.purkait@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