From: Nirmoy Das <nirmoy.das@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH i-g-t] tests/intel-ci: Remove xe_bo_shrink_kunit
Date: Thu, 14 Nov 2024 11:31:17 +0100 [thread overview]
Message-ID: <ae905771-92ac-4ef9-993d-fca3508461ab@intel.com> (raw)
In-Reply-To: <486092b4-ed88-4868-bc91-43e952086c57@intel.com>
On 11/14/2024 11:21 AM, Matthew Auld wrote:
> On 14/11/2024 09:32, Nirmoy Das wrote:
>> Remove xe_bo_shrink_kunit which takes a while to run on various
>> machines. There is no good way to make it faster.
>
> Do we also add this to the blacklist? Otherwise I assume non-BAT will still run it.
I will add it to the blacklist to be safe.
Thanks,
Nirmoy
>
>>
>> Cc: Matthew Auld <matthew.auld@intel.com>
>> Suggested-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>> Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/2998
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>> ---
>> tests/intel-ci/xe-fast-feedback.testlist | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/tests/intel-ci/xe-fast-feedback.testlist b/tests/intel-ci/xe-fast-feedback.testlist
>> index d9fb98aab..c263473e0 100644
>> --- a/tests/intel-ci/xe-fast-feedback.testlist
>> +++ b/tests/intel-ci/xe-fast-feedback.testlist
>> @@ -217,7 +217,8 @@ igt@xe_waitfence@reltime
>> igt@core_hotunplug@unbind-rebind
>> # Run KUnit tests at the end
>> -igt@xe_live_ktest@xe_bo
>> +igt@xe_live_ktest@xe_bo@xe_ccs_migrate_kunit
>> +igt@xe_live_ktest@xe_bo@xe_bo_evict_kunit
>> igt@xe_live_ktest@xe_dma_buf
>> igt@xe_live_ktest@xe_migrate
>>
>
prev parent reply other threads:[~2024-11-14 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 9:32 [PATCH i-g-t] tests/intel-ci: Remove xe_bo_shrink_kunit Nirmoy Das
2024-11-14 10:21 ` Matthew Auld
2024-11-14 10:31 ` Nirmoy Das [this message]
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=ae905771-92ac-4ef9-993d-fca3508461ab@intel.com \
--to=nirmoy.das@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@linux.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