Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>, igt-dev@lists.freedesktop.org
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Subject: Re: [PATCH i-g-t] intel-ci/xe.blocklist: Block the updated shrink test
Date: Wed, 18 Dec 2024 15:06:08 +0100	[thread overview]
Message-ID: <ac26dc00-e0c6-4e48-bc0e-2c041c292898@linux.intel.com> (raw)
In-Reply-To: <20241218142407.2558613-1-nirmoy.das@intel.com>


On 12/18/2024 3:24 PM, Nirmoy Das wrote:
> xe_bo_shrink_kunit, sub-dynamic test is now updated to be a subtest
> in the kernel so update this blocklist accordingly.
>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> ---


Kernel patch is waiting for CI  results for merging, https://patchwork.freedesktop.org/series/142786/

>  tests/intel-ci/xe.blocklist.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/intel-ci/xe.blocklist.txt b/tests/intel-ci/xe.blocklist.txt
> index e29e745a0..189cc25a7 100644
> --- a/tests/intel-ci/xe.blocklist.txt
> +++ b/tests/intel-ci/xe.blocklist.txt
> @@ -31,7 +31,7 @@ igt@kms_selftest.*
>  ##################################################################
>  # Exclude slow KUnit test which should run as manual test
>  ##################################################################
> -igt@xe_live_ktest@xe_bo@xe_bo_shrink_kunit
> +igt@xe_live_ktest@xe_bo_shrink
>  ##################################################################
>  # Exclude all other non-Xe tests
>  ##################################################################

  reply	other threads:[~2024-12-18 14:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 14:24 [PATCH i-g-t] intel-ci/xe.blocklist: Block the updated shrink test Nirmoy Das
2024-12-18 14:06 ` Nirmoy Das [this message]
2024-12-18 15:01 ` 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=ac26dc00-e0c6-4e48-bc0e-2c041c292898@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=nirmoy.das@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