public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: aditya.chauhan@intel.com
To: ramadevi.gandi@intel.com, himanshu.girotra@intel.com,
	swati2.sharma@intel.com, igt-dev@lists.freedesktop.org
Subject: [PATCH i-g-t 0/2] tests/intel-ci: Add NVL display and core blocklists
Date: Wed, 11 Mar 2026 17:56:04 +0530	[thread overview]
Message-ID: <20260311122606.42223-1-aditya.chauhan@intel.com> (raw)

From: Aditya Chauhan <aditya.chauhan@intel.com>

This series adds blocklist files for the NVL platform under intel-ci.

Patch 1 introduces the xe.nvl.core.blocklist file and registers it
in meson.build to track known failing core tests on NVL.

Patch 2 fixes a missing meson.build entry for the NVL display blocklist
that was added in commit 04db3b26c52b
("intel-ci: Add NVL display blocklist").

Aditya Chauhan (2):
  tests/intel-ci: Add NVL core blocklist
  tests/ci: Add NVL Display blocklist to meson.build

 tests/intel-ci/meson.build               |  2 +
 tests/intel-ci/xe.nvl.core.blocklist.txt | 69 ++++++++++++++++++++++++
 2 files changed, 71 insertions(+)
 create mode 100644 tests/intel-ci/xe.nvl.core.blocklist.txt

-- 
2.34.1


             reply	other threads:[~2026-03-11 12:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 12:26 aditya.chauhan [this message]
2026-03-11 12:26 ` [PATCH i-g-t 1/2] tests/intel-ci: Add NVL core blocklist aditya.chauhan
2026-03-12  7:09   ` Sharma, Swati2
2026-03-11 12:26 ` [PATCH i-g-t 2/2] tests/ci: Add NVL Display blocklist to meson.build aditya.chauhan
2026-03-12  7:41   ` Sharma, Swati2
2026-03-12  1:02 ` ✓ Xe.CI.BAT: success for tests/intel-ci: Add NVL display and core blocklists Patchwork
2026-03-12  1:07 ` ✓ i915.CI.BAT: " Patchwork
2026-03-12 20:29 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-12 21:03 ` ✓ 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=20260311122606.42223-1-aditya.chauhan@intel.com \
    --to=aditya.chauhan@intel.com \
    --cc=himanshu.girotra@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=ramadevi.gandi@intel.com \
    --cc=swati2.sharma@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