Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Oak Zeng <oak.zeng@intel.com>
To: intel-xe@lists.freedesktop.org, igt-dev@lists.freedesktop.org
Cc: Thomas.Hellstrom@linux.intel.com
Subject: [i-g-t] tests/intel-ci: Fix a syntax err in xe.blocklist.txt
Date: Tue, 14 Jan 2025 12:35:23 -0500	[thread overview]
Message-ID: <20250114173523.3267049-1-oak.zeng@intel.com> (raw)

The syntax in below lines are wrong:

igt@xe_evict@*-multi-vm-cm*
igt@xe_evict@*-threads-*

With above, those xe_evict tests are not blacklisted from xe.ci.full category.

Fix the issue by adding a dot (.) preceding star (*).

Signed-off-by: Oak Zeng <oak.zeng@intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
---
 tests/intel-ci/xe.blocklist.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/tests/intel-ci/xe.blocklist.txt b/tests/intel-ci/xe.blocklist.txt
index a9b647c1d..fc270198f 100644
--- a/tests/intel-ci/xe.blocklist.txt
+++ b/tests/intel-ci/xe.blocklist.txt
@@ -93,7 +93,7 @@ igt@sriov_basic@bind-unbind-vf$
 # Exclude xe_evict tests that are not expected to succeed
 # due to missing TTM exhaustive eviction
 ##################################################################
-igt@xe_evict@*-multi-vm-cm*
-igt@xe_evict@*-threads-*
-# igt@xe_evict@*-cm* # Rebind and VM_BIND may race.
+igt@xe_evict@.*-multi-vm-cm.*
+igt@xe_evict@.*-threads-.*
+# igt@xe_evict@.*-cm.* # Rebind and VM_BIND may race.
 ##################################################################
-- 
2.26.3


             reply	other threads:[~2025-01-14 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 17:35 Oak Zeng [this message]
2025-01-14 17:28 ` ✗ CI.Patch_applied: failure for tests/intel-ci: Fix a syntax err in xe.blocklist.txt Patchwork
2025-01-15  8:02 ` [i-g-t] " Thomas Hellström
2025-01-15 11:09   ` Kamil Konieczny

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=20250114173523.3267049-1-oak.zeng@intel.com \
    --to=oak.zeng@intel.com \
    --cc=Thomas.Hellstrom@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    /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