From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Pravalika Gurram <pravalika.gurram@intel.com>,
Katarzyna Piecielska <katarzyna.piecielska@intel.com>
Subject: Re: [v1] tests/intel: Remove TEST field from test documentation
Date: Fri, 20 Dec 2024 16:24:03 +0100 [thread overview]
Message-ID: <Z2WME8F8v5sYf2kU@kamilkon-DESK1> (raw)
In-Reply-To: <20241220093914.706003-1-pravalika.gurram@intel.com>
Hi Pravalika,
On 2024-12-20 at 15:09:14 +0530, Pravalika Gurram wrote:
I would suggest changeing subject into having test name in prefix,
also shorten it into:
[i-g-t v1] tests/intel/xe_vm: Fixed documentation
> Each test should contain only one TEST field.
>
> Add the Functionality field in the TEST section
> to fix the warnings during the addition of subtests.
>
Here you could add Fixes: tag like
Fixes: 4d630db8b8cf ("tests/intel/xe_vm: Check negative cases for vm_create/destroy ioctl")
but imho if it is very recent it could be skipped. We also
do not have stable branches so it is not required.
Add also here:
Cc: Katarzyna Piecielska <katarzyna.piecielska@intel.com>
> Signed-off-by: Pravalika Gurram <pravalika.gurram@intel.com>
> ---
> tests/intel/xe_vm.c | 10 +---------
> 1 file changed, 1 insertion(+), 9 deletions(-)
>
> diff --git a/tests/intel/xe_vm.c b/tests/intel/xe_vm.c
> index b10269191..b5519c9fc 100644
> --- a/tests/intel/xe_vm.c
> +++ b/tests/intel/xe_vm.c
> @@ -8,6 +8,7 @@
> * Category: Core
> * Mega feature: General Core features
> * Sub-category: VMA
> + * Functionality: ioctl
imho this should be added at each new subtests you introduced
in your previous change. Maybe more proper name would be:
* Functionality: input_validation
or
* Functionality: ioctl_input_validation
What do you think about this, Kasia?
Regards,
Kamil
> */
>
> #include "igt.h"
> @@ -2247,15 +2248,6 @@ static void bind_flag_invalid(int fd)
> xe_vm_destroy(fd, vm);
> }
>
> -/**
> - * TEST: Negative test for vm create/destroy ioctl
> - * Category: Core
> - * Mega feature: General Core features
> - * Sub-category: Synchronization
> - * Functionality: vm create
> - * Test category: negative test
> - */
> -
> /**
> * SUBTEST: invalid-flag-%s
> * Description: function %arg[1] used in vm create IOCTL to make it fail
next prev parent reply other threads:[~2024-12-20 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 9:39 [PATCH v1] tests/intel: Remove TEST field from test documentation Pravalika Gurram
2024-12-20 11:49 ` ✓ i915.CI.BAT: success for " Patchwork
2024-12-20 11:58 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-20 15:14 ` [PATCH v1] " Piecielska, Katarzyna
2024-12-20 15:24 ` Kamil Konieczny [this message]
2024-12-21 14:26 ` ✗ Xe.CI.Full: failure for " Patchwork
2024-12-21 15:06 ` ✗ i915.CI.Full: " 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=Z2WME8F8v5sYf2kU@kamilkon-DESK1 \
--to=kamil.konieczny@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=katarzyna.piecielska@intel.com \
--cc=pravalika.gurram@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