From: Matthew Auld <matthew.auld@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org,
Pallavi Mishra <pallavi.mishra@intel.com>,
Francois Dugast <francois.dugast@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] tests/intel-ci/xe-fast-feedback: add create-invalid-mbz
Date: Thu, 30 Nov 2023 15:00:32 +0000 [thread overview]
Message-ID: <57854b8e-adda-46a6-bf95-327c98fa7486@intel.com> (raw)
In-Reply-To: <20231130135556.crdwx3uzgmcym5qo@kamilkon-desk.igk.intel.com>
On 30/11/2023 13:55, Kamil Konieczny wrote:
> Hi Matthew,
> On 2023-11-30 at 11:17:35 +0000, Matthew Auld wrote:
>> Ensure we have some coverage in BAT for gem_create MBZ fields.
>>
>> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
>> Cc: Pallavi Mishra <pallavi.mishra@intel.com>
>> Cc: Francois Dugast <francois.dugast@intel.com>
>> ---
>> tests/intel-ci/xe-fast-feedback.testlist | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/tests/intel-ci/xe-fast-feedback.testlist b/tests/intel-ci/xe-fast-feedback.testlist
>> index 5c53e249d..a83c17de7 100644
>> --- a/tests/intel-ci/xe-fast-feedback.testlist
>> +++ b/tests/intel-ci/xe-fast-feedback.testlist
>> @@ -2,6 +2,7 @@
>> igt@xe_module_load@load
>>
>> igt@xe_compute@compute-square
>> +igt@xe_create@create-invalid-mbz
>
> Please move it before @create-massive-size,
> it should be sorted alphabetically.
Ok, I didn't realise that was a requirement. I can move it.
Note that there are a bunch of tests in this list not following any kind
of alphabetical sorting, but is more ordered/grouped/structured by
functionality, which I think makes more sense IMO. Like here
create-invalid-mbz is just a really simple sanity check for gem_create
so running it first made sense to me. A better example is maybe
xe_vm@shared-*, since for that it makes sense to run the pte subtest
first, with every next test being the next level up in the paging
structures:
igt@xe_vm@shared-pte-page
igt@xe_vm@shared-pde-page
igt@xe_vm@shared-pde2-page
igt@xe_vm@shared-pde3-page
So here it rather ordered by functionally. Anyway, I think if we intend
to sort this alphabetically we should put a comment at the top of the
file or something, and then also send a patch to sort everything?
>
> Regards,
> Kamil
>
>> igt@xe_create@create-execqueues-noleak
>> igt@xe_create@create-execqueues-leak
>> igt@xe_create@create-massive-size
>> --
>> 2.43.0
>>
next prev parent reply other threads:[~2023-11-30 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 11:17 [igt-dev] [PATCH i-g-t 1/2] tests/intel/xe_create: sanity check all MBZ fields Matthew Auld
2023-11-30 11:17 ` [igt-dev] [PATCH i-g-t 2/2] tests/intel-ci/xe-fast-feedback: add create-invalid-mbz Matthew Auld
2023-11-30 13:55 ` Kamil Konieczny
2023-11-30 15:00 ` Matthew Auld [this message]
2023-11-30 17:07 ` Kamil Konieczny
2023-11-30 13:42 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] tests/intel/xe_create: sanity check all MBZ fields Patchwork
2023-11-30 13:54 ` [igt-dev] [PATCH i-g-t 1/2] " Kamil Konieczny
2023-11-30 14:34 ` Matthew Auld
2023-11-30 17:02 ` Kamil Konieczny
2023-11-30 14:11 ` [igt-dev] ✓ CI.xeBAT: success for series starting with [i-g-t,1/2] " Patchwork
2023-12-01 19:16 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=57854b8e-adda-46a6-bf95-327c98fa7486@intel.com \
--to=matthew.auld@intel.com \
--cc=francois.dugast@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=pallavi.mishra@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