From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Oak Zeng <oak.zeng@intel.com>,
intel-xe@lists.freedesktop.org, igt-dev@lists.freedesktop.org
Subject: Re: [i-g-t] tests/intel-ci: Fix a syntax err in xe.blocklist.txt
Date: Wed, 15 Jan 2025 09:02:20 +0100 [thread overview]
Message-ID: <b0a4127bd7403d4dd9390be78f819f524d36b194.camel@linux.intel.com> (raw)
In-Reply-To: <20250114173523.3267049-1-oak.zeng@intel.com>
On Tue, 2025-01-14 at 12:35 -0500, Oak Zeng wrote:
> 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>
Reviewed-by: 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.
> ##################################################################
next prev parent reply other threads:[~2025-01-15 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 17:35 [i-g-t] tests/intel-ci: Fix a syntax err in xe.blocklist.txt Oak Zeng
2025-01-14 17:28 ` ✗ CI.Patch_applied: failure for " Patchwork
2025-01-15 8:02 ` Thomas Hellström [this message]
2025-01-15 11:09 ` [i-g-t] " 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=b0a4127bd7403d4dd9390be78f819f524d36b194.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=oak.zeng@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