* [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan
@ 2023-09-01 5:18 Bhanuprakash Modem
2023-09-01 6:17 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
` (7 more replies)
0 siblings, 8 replies; 13+ messages in thread
From: Bhanuprakash Modem @ 2023-09-01 5:18 UTC (permalink / raw)
To: igt-dev
As non-Intel vendors also contributing to KMS tests, allow
them to re-use the existing testplan documentation along with
their own definitions of field:values pair in test config json.
Instead of aborting, just throw a warning about this unrecognized
field:values.
Example:
tests/kms_color.c:994: Warning: unrecognized field in tests/kms_test_config.json ==> Foo: bla
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
---
scripts/test_list.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/test_list.py b/scripts/test_list.py
index 0bcc96869..517c4d067 100755
--- a/scripts/test_list.py
+++ b/scripts/test_list.py
@@ -1219,8 +1219,8 @@ class TestList:
continue
file_line.rstrip(r"\n")
- sys.exit(f"{fname}:{file_ln + 1}: Error: unrecognized line. Need to add field at %s?\n\t==> %s" %
- (self.config_fname, file_line))
+ print(f"{'/'.join(fname.split('/')[-2:])}:{file_ln + 1}: Warning: unrecognized field in %s ==> %s" %
+ ('/'.join(self.config_fname.split('/')[-2:]), file_line))
def show_subtests(self, sort_field):
--
2.40.0
^ permalink raw reply related [flat|nested] 13+ messages in thread
* [igt-dev] ✗ GitLab.Pipeline: warning for scripts/test_list: Allow unrecognized field:values in testplan
2023-09-01 5:18 [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan Bhanuprakash Modem
@ 2023-09-01 6:17 ` Patchwork
2023-09-01 6:51 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
` (6 subsequent siblings)
7 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2023-09-01 6:17 UTC (permalink / raw)
To: Bhanuprakash Modem; +Cc: igt-dev
== Series Details ==
Series: scripts/test_list: Allow unrecognized field:values in testplan
URL : https://patchwork.freedesktop.org/series/123144/
State : warning
== Summary ==
Pipeline status: FAILED.
see https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/975141 for the overview.
build-containers:build-debian has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/48349379):
Reinitialized existing Git repository in /builds/gfx-ci/igt-ci-tags/.git/
Checking out afe798e2 as detached HEAD (ref is intel/IGTPW_9703)...
Skipping Git submodules setup
section_end:1693548546:get_sources
section_start:1693548546:step_script
Executing "step_script" stage of the job script
Using docker image sha256:594aa868d31ee3304dee8cae8a3433c89a6fcfcf6c7d420c04cce22f60147176 for registry.freedesktop.org/wayland/ci-templates/buildah:2019-08-13.0 with digest registry.freedesktop.org/wayland/ci-templates/buildah@sha256:7dbcf22cd2c1c7d49db0dc7b4ab207c3d6a4a09bd81cc3b71a688d3727d8749f ...
$ /host/bin/curl -s -L --cacert /host/ca-certificates.crt --retry 4 -f --retry-delay 60 https://gitlab.freedesktop.org/freedesktop/helm-gitlab-infra/-/raw/main/runner-gating/runner-gating.sh | sh
Checking if the user of the pipeline is allowed...
Checking if the job's project is part of a well-known group...
Thank you for contributing to freedesktop.org
$ podman login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
Error: error authenticating creds for "registry.freedesktop.org": Get https://registry.freedesktop.org/v2/: dial tcp 147.75.198.156:443: i/o timeout
section_end:1693548578:step_script
section_start:1693548578:cleanup_file_variables
Cleaning up project directory and file based variables
section_end:1693548578:cleanup_file_variables
ERROR: Job failed: exit code 1
build-containers:build-fedora has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/48349383):
time="2023-09-01T06:10:01Z" level=fatal msg="Error determining repository tags: Get https://registry.freedesktop.org/v2/gfx-ci/igt-ci-tags/build-fedora/tags/list?last=commit-f4bc80ad977d70a3486e32efae18e1d681e642b1&n=100: dial tcp 147.75.198.156:443: i/o timeout"
Building!
STEP 1: FROM fedora:31
Getting image source signatures
Copying blob sha256:854946d575a439a894349addd141568875d7c1e673d3286b08250f3dde002e6a
Copying config sha256:7e94ed77b448a8d2ff08b92d3ca743e4e862c744892d6886c73487581eb5863a
Writing manifest to image destination
Storing signatures
STEP 2: RUN dnf install -y gcc flex bison libatomic meson ninja-build xdotool 'pkgconfig(libdrm)' 'pkgconfig(pciaccess)' 'pkgconfig(libkmod)' 'pkgconfig(libprocps)' 'pkgconfig(libunwind)' 'pkgconfig(libdw)' 'pkgconfig(pixman-1)' 'pkgconfig(valgrind)' 'pkgconfig(cairo)' 'pkgconfig(libudev)' 'pkgconfig(glib-2.0)' 'pkgconfig(gsl)' 'pkgconfig(alsa)' 'pkgconfig(xmlrpc)' 'pkgconfig(xmlrpc_util)' 'pkgconfig(xmlrpc_client)' 'pkgconfig(json-c)' 'pkgconfig(gtk-doc)' 'pkgconfig(xv)' 'pkgconfig(xrandr)' python3-docutils
error running container: error creating container for [/bin/sh -c dnf install -y gcc flex bison libatomic meson ninja-build xdotool 'pkgconfig(libdrm)' 'pkgconfig(pciaccess)' 'pkgconfig(libkmod)' 'pkgconfig(libprocps)' 'pkgconfig(libunwind)' 'pkgconfig(libdw)' 'pkgconfig(pixman-1)' 'pkgconfig(valgrind)' 'pkgconfig(cairo)' 'pkgconfig(libudev)' 'pkgconfig(glib-2.0)' 'pkgconfig(gsl)' 'pkgconfig(alsa)' 'pkgconfig(xmlrpc)' 'pkgconfig(xmlrpc_util)' 'pkgconfig(xmlrpc_client)' 'pkgconfig(json-c)' 'pkgconfig(gtk-doc)' 'pkgconfig(xv)' 'pkgconfig(xrandr)' python3-docutils]: time="2023-09-01T06:10:12Z" level=warning msg="signal: killed"
time="2023-09-01T06:10:12Z" level=error msg="container_linux.go:346: starting container process caused \"process_linux.go:297: applying cgroup configuration for process caused \\\"mountpoint for cgroup not found\\\"\"\n"
container_linux.go:346: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused \"mountpoint for cgroup not found\""
: exit status 1
Error: error building at STEP "RUN dnf install -y gcc flex bison libatomic meson ninja-build xdotool 'pkgconfig(libdrm)' 'pkgconfig(pciaccess)' 'pkgconfig(libkmod)' 'pkgconfig(libprocps)' 'pkgconfig(libunwind)' 'pkgconfig(libdw)' 'pkgconfig(pixman-1)' 'pkgconfig(valgrind)' 'pkgconfig(cairo)' 'pkgconfig(libudev)' 'pkgconfig(glib-2.0)' 'pkgconfig(gsl)' 'pkgconfig(alsa)' 'pkgconfig(xmlrpc)' 'pkgconfig(xmlrpc_util)' 'pkgconfig(xmlrpc_client)' 'pkgconfig(json-c)' 'pkgconfig(gtk-doc)' 'pkgconfig(xv)' 'pkgconfig(xrandr)' python3-docutils": error while running runtime: exit status 1
section_end:1693548612:step_script
section_start:1693548612:cleanup_file_variables
Cleaning up project directory and file based variables
section_end:1693548613:cleanup_file_variables
ERROR: Job failed: exit code 1
== Logs ==
For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/975141
^ permalink raw reply [flat|nested] 13+ messages in thread
* [igt-dev] ✓ CI.xeBAT: success for scripts/test_list: Allow unrecognized field:values in testplan
2023-09-01 5:18 [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan Bhanuprakash Modem
2023-09-01 6:17 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
@ 2023-09-01 6:51 ` Patchwork
2023-09-01 6:51 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
` (5 subsequent siblings)
7 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2023-09-01 6:51 UTC (permalink / raw)
To: Bhanuprakash Modem; +Cc: igt-dev
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
== Series Details ==
Series: scripts/test_list: Allow unrecognized field:values in testplan
URL : https://patchwork.freedesktop.org/series/123144/
State : success
== Summary ==
CI Bug Log - changes from XEIGT_7462_BAT -> XEIGTPW_9703_BAT
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (4 -> 4)
------------------------------
No changes in participating hosts
Changes
-------
No changes found
Build changes
-------------
* IGT: IGT_7462 -> IGTPW_9703
IGTPW_9703: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9703/index.html
IGT_7462: 6269a2cccba725641814f8cbc53f2661bc5b04cf @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
xe-351-bca3262d221e1402c03a89bb4ba520d6aa610505: bca3262d221e1402c03a89bb4ba520d6aa610505
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_9703/index.html
[-- Attachment #2: Type: text/html, Size: 1477 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* [igt-dev] ✗ Fi.CI.BAT: failure for scripts/test_list: Allow unrecognized field:values in testplan
2023-09-01 5:18 [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan Bhanuprakash Modem
2023-09-01 6:17 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2023-09-01 6:51 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
@ 2023-09-01 6:51 ` Patchwork
2023-09-01 7:20 ` [igt-dev] [i-g-t] " Mauro Carvalho Chehab
` (4 subsequent siblings)
7 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2023-09-01 6:51 UTC (permalink / raw)
To: Bhanuprakash Modem; +Cc: igt-dev
[-- Attachment #1: Type: text/plain, Size: 4351 bytes --]
== Series Details ==
Series: scripts/test_list: Allow unrecognized field:values in testplan
URL : https://patchwork.freedesktop.org/series/123144/
State : failure
== Summary ==
CI Bug Log - changes from IGT_7462 -> IGTPW_9703
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_9703 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_9703, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9703/index.html
Participating hosts (40 -> 39)
------------------------------
Missing (1): fi-snb-2520m
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_9703:
### IGT changes ###
#### Possible regressions ####
* igt@gem_exec_suspend@basic-s0@smem:
- fi-blb-e6850: [PASS][1] -> [ABORT][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7462/fi-blb-e6850/igt@gem_exec_suspend@basic-s0@smem.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9703/fi-blb-e6850/igt@gem_exec_suspend@basic-s0@smem.html
Known issues
------------
Here are the changes found in IGTPW_9703 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_suspend@basic-s2idle-without-i915:
- fi-skl-guc: [PASS][3] -> [ABORT][4] ([i915#8299])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7462/fi-skl-guc/igt@i915_suspend@basic-s2idle-without-i915.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9703/fi-skl-guc/igt@i915_suspend@basic-s2idle-without-i915.html
* igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-d-edp-1:
- bat-rplp-1: [PASS][5] -> [ABORT][6] ([i915#8442] / [i915#8668])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7462/bat-rplp-1/igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-d-edp-1.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9703/bat-rplp-1/igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-d-edp-1.html
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s0@smem:
- bat-jsl-3: [ABORT][7] ([i915#5122]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7462/bat-jsl-3/igt@gem_exec_suspend@basic-s0@smem.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9703/bat-jsl-3/igt@gem_exec_suspend@basic-s0@smem.html
* igt@i915_suspend@basic-s3-without-i915:
- bat-jsl-3: [FAIL][9] ([fdo#103375]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7462/bat-jsl-3/igt@i915_suspend@basic-s3-without-i915.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9703/bat-jsl-3/igt@i915_suspend@basic-s3-without-i915.html
* igt@kms_pipe_crc_basic@suspend-read-crc@pipe-a-hdmi-a-1:
- fi-rkl-11600: [FAIL][11] ([fdo#103375]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7462/fi-rkl-11600/igt@kms_pipe_crc_basic@suspend-read-crc@pipe-a-hdmi-a-1.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9703/fi-rkl-11600/igt@kms_pipe_crc_basic@suspend-read-crc@pipe-a-hdmi-a-1.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[i915#5122]: https://gitlab.freedesktop.org/drm/intel/issues/5122
[i915#7952]: https://gitlab.freedesktop.org/drm/intel/issues/7952
[i915#8299]: https://gitlab.freedesktop.org/drm/intel/issues/8299
[i915#8442]: https://gitlab.freedesktop.org/drm/intel/issues/8442
[i915#8668]: https://gitlab.freedesktop.org/drm/intel/issues/8668
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_7462 -> IGTPW_9703
CI-20190529: 20190529
CI_DRM_13583: f299d7585a085ee36999da219c292e265da35886 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_9703: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9703/index.html
IGT_7462: 6269a2cccba725641814f8cbc53f2661bc5b04cf @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9703/index.html
[-- Attachment #2: Type: text/html, Size: 5108 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan
2023-09-01 5:18 [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan Bhanuprakash Modem
` (2 preceding siblings ...)
2023-09-01 6:51 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
@ 2023-09-01 7:20 ` Mauro Carvalho Chehab
2023-09-01 9:02 ` Modem, Bhanuprakash
2023-09-01 10:22 ` [igt-dev] ✗ GitLab.Pipeline: warning for scripts/test_list: Allow unrecognized field:values in testplan (rev2) Patchwork
` (3 subsequent siblings)
7 siblings, 1 reply; 13+ messages in thread
From: Mauro Carvalho Chehab @ 2023-09-01 7:20 UTC (permalink / raw)
To: Bhanuprakash Modem; +Cc: igt-dev
On Fri, 1 Sep 2023 10:48:08 +0530
Bhanuprakash Modem <bhanuprakash.modem@intel.com> wrote:
> As non-Intel vendors also contributing to KMS tests, allow
> them to re-use the existing testplan documentation along with
> their own definitions of field:values pair in test config json.
>
> Instead of aborting, just throw a warning about this unrecognized
> field:values.
>
> Example:
> tests/kms_color.c:994: Warning: unrecognized field in tests/kms_test_config.json ==> Foo: bla
IMO, there's no need to to that. I mean, if someone wants to add
a new field, he can just patch tests/kms_test_config.json, adding the
new "Foo" field at kms_test_config.json:
diff --git a/tests/kms_test_config.json b/tests/kms_test_config.json
index 9219ae4ebd9d..1dfca84dd73c 100644
--- a/tests/kms_test_config.json
+++ b/tests/kms_test_config.json
@@ -35,6 +35,7 @@
"description": "Defines the test category. Usually used at subtest level."
}
},
+ "Foo" : { },
"Description" : {
"_properties_": {
"description": "Provides a description for the test/subtest."
NOTE: It would probably make sense to add a description to it, to make
clear what such "Foo" field means, in a similar way to the descriptions
added to the other fields.
As the fields are optional, this won't require any changes at the
existing tests, and will provide an extra benefit that the meaning of
the "Foo" field can be documented via _properties_/description field.
Regards,
Mauro
>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> ---
> scripts/test_list.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/test_list.py b/scripts/test_list.py
> index 0bcc96869..517c4d067 100755
> --- a/scripts/test_list.py
> +++ b/scripts/test_list.py
> @@ -1219,8 +1219,8 @@ class TestList:
> continue
>
> file_line.rstrip(r"\n")
> - sys.exit(f"{fname}:{file_ln + 1}: Error: unrecognized line. Need to add field at %s?\n\t==> %s" %
> - (self.config_fname, file_line))
> + print(f"{'/'.join(fname.split('/')[-2:])}:{file_ln + 1}: Warning: unrecognized field in %s ==> %s" %
> + ('/'.join(self.config_fname.split('/')[-2:]), file_line))
>
> def show_subtests(self, sort_field):
>
^ permalink raw reply related [flat|nested] 13+ messages in thread
* Re: [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan
2023-09-01 7:20 ` [igt-dev] [i-g-t] " Mauro Carvalho Chehab
@ 2023-09-01 9:02 ` Modem, Bhanuprakash
2023-09-01 10:08 ` Mauro Carvalho Chehab
0 siblings, 1 reply; 13+ messages in thread
From: Modem, Bhanuprakash @ 2023-09-01 9:02 UTC (permalink / raw)
To: Mauro Carvalho Chehab; +Cc: igt-dev
Hi Mauro,
On Fri-01-09-2023 12:50 pm, Mauro Carvalho Chehab wrote:
> On Fri, 1 Sep 2023 10:48:08 +0530
> Bhanuprakash Modem <bhanuprakash.modem@intel.com> wrote:
>
>> As non-Intel vendors also contributing to KMS tests, allow
>> them to re-use the existing testplan documentation along with
>> their own definitions of field:values pair in test config json.
>>
>> Instead of aborting, just throw a warning about this unrecognized
>> field:values.
>>
>> Example:
>> tests/kms_color.c:994: Warning: unrecognized field in tests/kms_test_config.json ==> Foo: bla
>
> IMO, there's no need to to that. I mean, if someone wants to add
> a new field, he can just patch tests/kms_test_config.json, adding the
> new "Foo" field at kms_test_config.json:
Non-Intel people may not use kms_test_config.json since it is designed
for Intel supported (tests/kms_*.c & tests/intel/kms_*.c) tests
(Probably we may need to rename it to intel_kms_test_config.json).
So, non-Intel vendors are also allowed to include few kms tests
(tests/kms_*.c) in their own testplan. Also, we can't restrict them to
use the same testplan as kms_test_config.json.
Example:
Suppose, some non-Intel vendor (xyz) created a xyz_kms_test_config.json
with the "Foo" field defined in it, and updated the documentation of
tests/kms_*.c accordingly. Since Intel's kms_test_config.json is also
using tests/kms_*.c and not aware of "Foo" can lead the failure.
The problem statement is to have different testplans with their own set
of field:values and share the documentation.
- Bhanu
>
> diff --git a/tests/kms_test_config.json b/tests/kms_test_config.json
> index 9219ae4ebd9d..1dfca84dd73c 100644
> --- a/tests/kms_test_config.json
> +++ b/tests/kms_test_config.json
> @@ -35,6 +35,7 @@
> "description": "Defines the test category. Usually used at subtest level."
> }
> },
> + "Foo" : { },
> "Description" : {
> "_properties_": {
> "description": "Provides a description for the test/subtest."
>
> NOTE: It would probably make sense to add a description to it, to make
> clear what such "Foo" field means, in a similar way to the descriptions
> added to the other fields.
>
> As the fields are optional, this won't require any changes at the
> existing tests, and will provide an extra benefit that the meaning of
> the "Foo" field can be documented via _properties_/description field >
> Regards,
> Mauro
>
>>
>> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
>> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
>> ---
>> scripts/test_list.py | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/scripts/test_list.py b/scripts/test_list.py
>> index 0bcc96869..517c4d067 100755
>> --- a/scripts/test_list.py
>> +++ b/scripts/test_list.py
>> @@ -1219,8 +1219,8 @@ class TestList:
>> continue
>>
>> file_line.rstrip(r"\n")
>> - sys.exit(f"{fname}:{file_ln + 1}: Error: unrecognized line. Need to add field at %s?\n\t==> %s" %
>> - (self.config_fname, file_line))
>> + print(f"{'/'.join(fname.split('/')[-2:])}:{file_ln + 1}: Warning: unrecognized field in %s ==> %s" %
>> + ('/'.join(self.config_fname.split('/')[-2:]), file_line))
>>
>> def show_subtests(self, sort_field):
>>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan
2023-09-01 9:02 ` Modem, Bhanuprakash
@ 2023-09-01 10:08 ` Mauro Carvalho Chehab
2023-09-01 12:39 ` Modem, Bhanuprakash
0 siblings, 1 reply; 13+ messages in thread
From: Mauro Carvalho Chehab @ 2023-09-01 10:08 UTC (permalink / raw)
To: Modem, Bhanuprakash; +Cc: igt-dev
On Fri, 1 Sep 2023 14:32:09 +0530
"Modem, Bhanuprakash" <bhanuprakash.modem@intel.com> wrote:
> Hi Mauro,
>
> On Fri-01-09-2023 12:50 pm, Mauro Carvalho Chehab wrote:
> > On Fri, 1 Sep 2023 10:48:08 +0530
> > Bhanuprakash Modem <bhanuprakash.modem@intel.com> wrote:
> >
> >> As non-Intel vendors also contributing to KMS tests, allow
> >> them to re-use the existing testplan documentation along with
> >> their own definitions of field:values pair in test config json.
> >>
> >> Instead of aborting, just throw a warning about this unrecognized
> >> field:values.
> >>
> >> Example:
> >> tests/kms_color.c:994: Warning: unrecognized field in tests/kms_test_config.json ==> Foo: bla
> >
> > IMO, there's no need to to that. I mean, if someone wants to add
> > a new field, he can just patch tests/kms_test_config.json, adding the
> > new "Foo" field at kms_test_config.json:
>
> Non-Intel people may not use kms_test_config.json since it is designed
> for Intel supported (tests/kms_*.c & tests/intel/kms_*.c) tests
> (Probably we may need to rename it to intel_kms_test_config.json).
The infra is designed to be generic, and not Intel driver specific.
I'm even sending patches to Kernel upstream to also use it:
https://lore.kernel.org/linux-doc/cover.1693550658.git.mchehab@kernel.org/T/#t
> So, non-Intel vendors are also allowed to include few kms tests
> (tests/kms_*.c) in their own testplan. Also, we can't restrict them to
> use the same testplan as kms_test_config.json.
Hmm... so you're thinking about having a tests/kms_foo.c file that will
be included on both:
vendor_a/kms_test_config.json
and:
vendor_b/kms_test_config.json
Yes, that's possible. We actually have one or two cases at i915
and xe for some tests that aren't driver-specific. As the i915
JSON config file has an extra field ("Feature"), I added it to
Xe driver as well. This is used currently only for those
generic tests that are used on both.
> Example:
> Suppose, some non-Intel vendor (xyz) created a xyz_kms_test_config.json
> with the "Foo" field defined in it, and updated the documentation of
> tests/kms_*.c accordingly. Since Intel's kms_test_config.json is also
> using tests/kms_*.c and not aware of "Foo" can lead the failure.
Currently, the developer who created/updated vendor_a/kms_test_config.json
and tests/kms_foo.c will have a compilation error pointing to it. Such
developer will then know that the new field also needs to be at
vendor_b/kms_test_config.json and can submit a patch against it to
solve the error.
If we apply your patch, it means that it will generate a warning and
someone from vendor_b will need later to identify what happened and
copy the (possible) definition from vendor_a/kms_test_config.json to
suppress the warning.
It works, but it means an extra step. So, while I would prefer to not
merge this change, I won't oppose on converting it into a warning.
If you decide to go ahead and merge it, you can add my acked-by.
> The problem statement is to have different testplans with their own set
> of field:values and share the documentation.
>
> - Bhanu
>
> >
> > diff --git a/tests/kms_test_config.json b/tests/kms_test_config.json
> > index 9219ae4ebd9d..1dfca84dd73c 100644
> > --- a/tests/kms_test_config.json
> > +++ b/tests/kms_test_config.json
> > @@ -35,6 +35,7 @@
> > "description": "Defines the test category. Usually used at subtest level."
> > }
> > },
> > + "Foo" : { },
> > "Description" : {
> > "_properties_": {
> > "description": "Provides a description for the test/subtest."
> >
> > NOTE: It would probably make sense to add a description to it, to make
> > clear what such "Foo" field means, in a similar way to the descriptions
> > added to the other fields.
> >
> > As the fields are optional, this won't require any changes at the
> > existing tests, and will provide an extra benefit that the meaning of
> > the "Foo" field can be documented via _properties_/description field >
> > Regards,
> > Mauro
> >
> >>
> >> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> >> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> >> ---
> >> scripts/test_list.py | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/scripts/test_list.py b/scripts/test_list.py
> >> index 0bcc96869..517c4d067 100755
> >> --- a/scripts/test_list.py
> >> +++ b/scripts/test_list.py
> >> @@ -1219,8 +1219,8 @@ class TestList:
> >> continue
> >>
> >> file_line.rstrip(r"\n")
> >> - sys.exit(f"{fname}:{file_ln + 1}: Error: unrecognized line. Need to add field at %s?\n\t==> %s" %
> >> - (self.config_fname, file_line))
> >> + print(f"{'/'.join(fname.split('/')[-2:])}:{file_ln + 1}: Warning: unrecognized field in %s ==> %s" %
> >> + ('/'.join(self.config_fname.split('/')[-2:]), file_line))
> >>
> >> def show_subtests(self, sort_field):
> >>
^ permalink raw reply [flat|nested] 13+ messages in thread
* [igt-dev] ✗ GitLab.Pipeline: warning for scripts/test_list: Allow unrecognized field:values in testplan (rev2)
2023-09-01 5:18 [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan Bhanuprakash Modem
` (3 preceding siblings ...)
2023-09-01 7:20 ` [igt-dev] [i-g-t] " Mauro Carvalho Chehab
@ 2023-09-01 10:22 ` Patchwork
2023-09-01 10:49 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
` (2 subsequent siblings)
7 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2023-09-01 10:22 UTC (permalink / raw)
To: Mauro Carvalho Chehab; +Cc: igt-dev
== Series Details ==
Series: scripts/test_list: Allow unrecognized field:values in testplan (rev2)
URL : https://patchwork.freedesktop.org/series/123144/
State : warning
== Summary ==
Pipeline status: FAILED.
see https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/975341 for the overview.
build-containers:build-debian-arm64 has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/48362972):
time="2023-09-01T10:20:10Z" level=fatal msg="Error determining repository tags: Get https://registry.freedesktop.org/v2/gfx-ci/igt-ci-tags/build-debian-arm64/tags/list?last=commit-ef0457462daa0fc8c5b22fec3fc95f1623ac160f&n=100: dial tcp 147.75.198.156:443: i/o timeout"
Building!
STEP 1: FROM debian:buster
Getting image source signatures
Copying blob sha256:d6b7393fb4f375905c31c483d81ce2a2905f88aba8cb198874da2b54035bc41d
Copying config sha256:de08540e8ff0e470ff7956df4bed403725a5f45c186e9bf495da5344ff8fbe84
Writing manifest to image destination
Storing signatures
STEP 2: RUN apt-get update
error running container: error creating container for [/bin/sh -c apt-get update]: time="2023-09-01T10:20:19Z" level=warning msg="signal: killed"
time="2023-09-01T10:20:19Z" level=error msg="container_linux.go:346: starting container process caused \"process_linux.go:297: applying cgroup configuration for process caused \\\"mountpoint for cgroup not found\\\"\"\n"
container_linux.go:346: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused \"mountpoint for cgroup not found\""
: exit status 1
Error: error building at STEP "RUN apt-get update": error while running runtime: exit status 1
section_end:1693563626:step_script
section_start:1693563626:cleanup_file_variables
Cleaning up project directory and file based variables
section_end:1693563626:cleanup_file_variables
ERROR: Job failed: exit code 1
build-containers:build-debian-armhf has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/48362971):
time="2023-09-01T10:19:42Z" level=fatal msg="Error determining repository tags: Get https://registry.freedesktop.org/v2/gfx-ci/igt-ci-tags/build-debian-armhf/tags/list?last=commit-373581d98eb1e41772854afcc73c7a9501bcd08a&n=100: dial tcp 147.75.198.156:443: i/o timeout"
Building!
STEP 1: FROM debian:buster
Getting image source signatures
Copying blob sha256:d6b7393fb4f375905c31c483d81ce2a2905f88aba8cb198874da2b54035bc41d
Copying config sha256:de08540e8ff0e470ff7956df4bed403725a5f45c186e9bf495da5344ff8fbe84
Writing manifest to image destination
Storing signatures
STEP 2: RUN apt-get update
error running container: error creating container for [/bin/sh -c apt-get update]: time="2023-09-01T10:19:57Z" level=warning msg="signal: killed"
time="2023-09-01T10:19:57Z" level=error msg="container_linux.go:346: starting container process caused \"process_linux.go:297: applying cgroup configuration for process caused \\\"mountpoint for cgroup not found\\\"\"\n"
container_linux.go:346: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused \"mountpoint for cgroup not found\""
: exit status 1
Error: error building at STEP "RUN apt-get update": error while running runtime: exit status 1
section_end:1693563597:step_script
section_start:1693563597:cleanup_file_variables
Cleaning up project directory and file based variables
section_end:1693563598:cleanup_file_variables
ERROR: Job failed: exit code 1
build-containers:build-debian-mips has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/48362973):
Reinitialized existing Git repository in /builds/gfx-ci/igt-ci-tags/.git/
Checking out 812c29d0 as detached HEAD (ref is intel/IGTPW_9704)...
Skipping Git submodules setup
section_end:1693563589:get_sources
section_start:1693563589:step_script
Executing "step_script" stage of the job script
Using docker image sha256:594aa868d31ee3304dee8cae8a3433c89a6fcfcf6c7d420c04cce22f60147176 for registry.freedesktop.org/wayland/ci-templates/buildah:2019-08-13.0 with digest registry.freedesktop.org/wayland/ci-templates/buildah@sha256:7dbcf22cd2c1c7d49db0dc7b4ab207c3d6a4a09bd81cc3b71a688d3727d8749f ...
$ /host/bin/curl -s -L --cacert /host/ca-certificates.crt --retry 4 -f --retry-delay 60 https://gitlab.freedesktop.org/freedesktop/helm-gitlab-infra/-/raw/main/runner-gating/runner-gating.sh | sh
Checking if the user of the pipeline is allowed...
Checking if the job's project is part of a well-known group...
Thank you for contributing to freedesktop.org
$ podman login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
Error: error authenticating creds for "registry.freedesktop.org": Get https://gitlab.freedesktop.org/jwt/auth?account=gitlab-ci-token&service=container_registry: dial tcp 147.75.198.156:443: i/o timeout
section_end:1693563621:step_script
section_start:1693563621:cleanup_file_variables
Cleaning up project directory and file based variables
section_end:1693563622:cleanup_file_variables
ERROR: Job failed: exit code 1
build-containers:build-fedora has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/48362974):
"Created": "2019-11-11T12:55:05.209459628Z",
"DockerVersion": "",
"Labels": {
"maintainer": "Clement Verna \u003ccverna@fedoraproject.org\u003e"
},
"Architecture": "amd64",
"Os": "linux",
"Layers": [
"sha256:b39735705e69a2516323755ff4698ea5cd86b08b31d8c8287bc83d76d34c3bfc"
]
}
Skipping, already built
Getting image source signatures
time="2023-09-01T10:20:39Z" level=fatal msg="Error trying to reuse blob sha256:b39735705e69a2516323755ff4698ea5cd86b08b31d8c8287bc83d76d34c3bfc at destination: Get https://gitlab.freedesktop.org/jwt/auth?account=gitlab-ci-token&scope=repository%3Agfx-ci%2Figt-ci-tags%2Fbuild-fedora%3Apull%2Cpush&service=container_registry: dial tcp 147.75.198.156:443: i/o timeout"
section_end:1693563639:step_script
section_start:1693563639:cleanup_file_variables
Cleaning up project directory and file based variables
section_end:1693563640:cleanup_file_variables
ERROR: Job failed: exit code 1
== Logs ==
For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/975341
^ permalink raw reply [flat|nested] 13+ messages in thread
* [igt-dev] ✓ CI.xeBAT: success for scripts/test_list: Allow unrecognized field:values in testplan (rev2)
2023-09-01 5:18 [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan Bhanuprakash Modem
` (4 preceding siblings ...)
2023-09-01 10:22 ` [igt-dev] ✗ GitLab.Pipeline: warning for scripts/test_list: Allow unrecognized field:values in testplan (rev2) Patchwork
@ 2023-09-01 10:49 ` Patchwork
2023-09-01 10:50 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-09-01 19:30 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
7 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2023-09-01 10:49 UTC (permalink / raw)
To: Mauro Carvalho Chehab; +Cc: igt-dev
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
== Series Details ==
Series: scripts/test_list: Allow unrecognized field:values in testplan (rev2)
URL : https://patchwork.freedesktop.org/series/123144/
State : success
== Summary ==
CI Bug Log - changes from XEIGT_7463_BAT -> XEIGTPW_9704_BAT
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (4 -> 4)
------------------------------
No changes in participating hosts
Known issues
------------
Here are the changes found in XEIGTPW_9704_BAT that come from known issues:
### IGT changes ###
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[Intel XE#524]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/524
Build changes
-------------
* IGT: IGT_7463 -> IGTPW_9704
* Linux: xe-351-bca3262d221e1402c03a89bb4ba520d6aa610505 -> xe-353-e4a0387635ffa6ccbc6207c9195896bcc4e59de2
IGTPW_9704: 9704
IGT_7463: 7463
xe-351-bca3262d221e1402c03a89bb4ba520d6aa610505: bca3262d221e1402c03a89bb4ba520d6aa610505
xe-353-e4a0387635ffa6ccbc6207c9195896bcc4e59de2: e4a0387635ffa6ccbc6207c9195896bcc4e59de2
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_9704/index.html
[-- Attachment #2: Type: text/html, Size: 1796 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for scripts/test_list: Allow unrecognized field:values in testplan (rev2)
2023-09-01 5:18 [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan Bhanuprakash Modem
` (5 preceding siblings ...)
2023-09-01 10:49 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
@ 2023-09-01 10:50 ` Patchwork
2023-09-01 19:30 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
7 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2023-09-01 10:50 UTC (permalink / raw)
To: Mauro Carvalho Chehab; +Cc: igt-dev
[-- Attachment #1: Type: text/plain, Size: 2784 bytes --]
== Series Details ==
Series: scripts/test_list: Allow unrecognized field:values in testplan (rev2)
URL : https://patchwork.freedesktop.org/series/123144/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13587 -> IGTPW_9704
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/index.html
Participating hosts (39 -> 38)
------------------------------
Missing (1): fi-snb-2520m
Known issues
------------
Here are the changes found in IGTPW_9704 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_suspend@basic-s0@smem:
- bat-dg2-9: [PASS][1] -> [INCOMPLETE][2] ([i915#6311])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/bat-dg2-9/igt@gem_exec_suspend@basic-s0@smem.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/bat-dg2-9/igt@gem_exec_suspend@basic-s0@smem.html
* igt@i915_selftest@live@gt_heartbeat:
- fi-apl-guc: [PASS][3] -> [DMESG-FAIL][4] ([i915#5334])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
#### Possible fixes ####
* igt@kms_flip@basic-flip-vs-wf_vblank@a-hdmi-a1:
- fi-elk-e7500: [FAIL][5] ([i915#2122]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/fi-elk-e7500/igt@kms_flip@basic-flip-vs-wf_vblank@a-hdmi-a1.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/fi-elk-e7500/igt@kms_flip@basic-flip-vs-wf_vblank@a-hdmi-a1.html
#### Warnings ####
* igt@kms_psr@primary_page_flip:
- bat-rplp-1: [SKIP][7] ([i915#1072]) -> [ABORT][8] ([i915#8860])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/bat-rplp-1/igt@kms_psr@primary_page_flip.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/bat-rplp-1/igt@kms_psr@primary_page_flip.html
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#6311]: https://gitlab.freedesktop.org/drm/intel/issues/6311
[i915#8860]: https://gitlab.freedesktop.org/drm/intel/issues/8860
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_7463 -> IGTPW_9704
CI-20190529: 20190529
CI_DRM_13587: 8152aa47d7b14683059ec856ffa99e2d86acfc8b @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_9704: 9704
IGT_7463: 7463
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/index.html
[-- Attachment #2: Type: text/html, Size: 3457 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan
2023-09-01 10:08 ` Mauro Carvalho Chehab
@ 2023-09-01 12:39 ` Modem, Bhanuprakash
2023-09-04 8:13 ` Mauro Carvalho Chehab
0 siblings, 1 reply; 13+ messages in thread
From: Modem, Bhanuprakash @ 2023-09-01 12:39 UTC (permalink / raw)
To: Mauro Carvalho Chehab; +Cc: igt-dev
Hi Mauro,
On Fri-01-09-2023 03:38 pm, Mauro Carvalho Chehab wrote:
> On Fri, 1 Sep 2023 14:32:09 +0530
> "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com> wrote:
>
>> Hi Mauro,
>>
>> On Fri-01-09-2023 12:50 pm, Mauro Carvalho Chehab wrote:
>>> On Fri, 1 Sep 2023 10:48:08 +0530
>>> Bhanuprakash Modem <bhanuprakash.modem@intel.com> wrote:
>>>
>>>> As non-Intel vendors also contributing to KMS tests, allow
>>>> them to re-use the existing testplan documentation along with
>>>> their own definitions of field:values pair in test config json.
>>>>
>>>> Instead of aborting, just throw a warning about this unrecognized
>>>> field:values.
>>>>
>>>> Example:
>>>> tests/kms_color.c:994: Warning: unrecognized field in tests/kms_test_config.json ==> Foo: bla
>>>
>>> IMO, there's no need to to that. I mean, if someone wants to add
>>> a new field, he can just patch tests/kms_test_config.json, adding the
>>> new "Foo" field at kms_test_config.json:
>>
>> Non-Intel people may not use kms_test_config.json since it is designed
>> for Intel supported (tests/kms_*.c & tests/intel/kms_*.c) tests
>> (Probably we may need to rename it to intel_kms_test_config.json).
>
> The infra is designed to be generic, and not Intel driver specific.
> I'm even sending patches to Kernel upstream to also use it:
>
> https://lore.kernel.org/linux-doc/cover.1693550658.git.mchehab@kernel.org/T/#t
>
>> So, non-Intel vendors are also allowed to include few kms tests
>> (tests/kms_*.c) in their own testplan. Also, we can't restrict them to
>> use the same testplan as kms_test_config.json.
>
> Hmm... so you're thinking about having a tests/kms_foo.c file that will
> be included on both:
>
> vendor_a/kms_test_config.json
>
> and:
>
> vendor_b/kms_test_config.json
>
> Yes, that's possible. We actually have one or two cases at i915
> and xe for some tests that aren't driver-specific. As the i915
> JSON config file has an extra field ("Feature"), I added it to
> Xe driver as well. This is used currently only for those
> generic tests that are used on both.
>
>> Example:
>> Suppose, some non-Intel vendor (xyz) created a xyz_kms_test_config.json
>> with the "Foo" field defined in it, and updated the documentation of
>> tests/kms_*.c accordingly. Since Intel's kms_test_config.json is also
>> using tests/kms_*.c and not aware of "Foo" can lead the failure.
>
> Currently, the developer who created/updated vendor_a/kms_test_config.json
> and tests/kms_foo.c will have a compilation error pointing to it. Such
> developer will then know that the new field also needs to be at
> vendor_b/kms_test_config.json and can submit a patch against it to
> solve the error.
Agreed, but the vendor_b needs to maintain something (field:values) that
he don't even know/care about.
>
> If we apply your patch, it means that it will generate a warning and
> someone from vendor_b will need later to identify what happened and
> copy the (possible) definition from vendor_a/kms_test_config.json to
> suppress the warning.
Yeah, There is no way to suppress the warning except maintaining the
definitions in both places.
>
> It works, but it means an extra step. So, while I would prefer to not
> merge this change, I won't oppose on converting it into a warning.
> If you decide to go ahead and merge it, you can add my acked-by.
We can hold this for sometime, till we get the better solution.
- Bhanu
>
>> The problem statement is to have different testplans with their own set
>> of field:values and share the documentation.
>>
>> - Bhanu
>>
>>>
>>> diff --git a/tests/kms_test_config.json b/tests/kms_test_config.json
>>> index 9219ae4ebd9d..1dfca84dd73c 100644
>>> --- a/tests/kms_test_config.json
>>> +++ b/tests/kms_test_config.json
>>> @@ -35,6 +35,7 @@
>>> "description": "Defines the test category. Usually used at subtest level."
>>> }
>>> },
>>> + "Foo" : { },
>>> "Description" : {
>>> "_properties_": {
>>> "description": "Provides a description for the test/subtest."
>>>
>>> NOTE: It would probably make sense to add a description to it, to make
>>> clear what such "Foo" field means, in a similar way to the descriptions
>>> added to the other fields.
>>>
>>> As the fields are optional, this won't require any changes at the
>>> existing tests, and will provide an extra benefit that the meaning of
>>> the "Foo" field can be documented via _properties_/description field >
>>> Regards,
>>> Mauro
>>>
>>>>
>>>> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
>>>> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
>>>> ---
>>>> scripts/test_list.py | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/scripts/test_list.py b/scripts/test_list.py
>>>> index 0bcc96869..517c4d067 100755
>>>> --- a/scripts/test_list.py
>>>> +++ b/scripts/test_list.py
>>>> @@ -1219,8 +1219,8 @@ class TestList:
>>>> continue
>>>>
>>>> file_line.rstrip(r"\n")
>>>> - sys.exit(f"{fname}:{file_ln + 1}: Error: unrecognized line. Need to add field at %s?\n\t==> %s" %
>>>> - (self.config_fname, file_line))
>>>> + print(f"{'/'.join(fname.split('/')[-2:])}:{file_ln + 1}: Warning: unrecognized field in %s ==> %s" %
>>>> + ('/'.join(self.config_fname.split('/')[-2:]), file_line))
>>>>
>>>> def show_subtests(self, sort_field):
>>>>
^ permalink raw reply [flat|nested] 13+ messages in thread
* [igt-dev] ✗ Fi.CI.IGT: failure for scripts/test_list: Allow unrecognized field:values in testplan (rev2)
2023-09-01 5:18 [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan Bhanuprakash Modem
` (6 preceding siblings ...)
2023-09-01 10:50 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
@ 2023-09-01 19:30 ` Patchwork
7 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2023-09-01 19:30 UTC (permalink / raw)
To: Mauro Carvalho Chehab; +Cc: igt-dev
[-- Attachment #1: Type: text/plain, Size: 73653 bytes --]
== Series Details ==
Series: scripts/test_list: Allow unrecognized field:values in testplan (rev2)
URL : https://patchwork.freedesktop.org/series/123144/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13587_full -> IGTPW_9704_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_9704_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_9704_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/index.html
Participating hosts (9 -> 9)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_9704_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_dirtyfb@dirtyfb-ioctl@psr-hdmi-a-1:
- shard-dg2: NOTRUN -> [SKIP][1] +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-10/igt@kms_dirtyfb@dirtyfb-ioctl@psr-hdmi-a-1.html
* igt@kms_dirtyfb@dirtyfb-ioctl@psr-hdmi-a-4:
- shard-dg1: NOTRUN -> [SKIP][2] +1 similar issue
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-17/igt@kms_dirtyfb@dirtyfb-ioctl@psr-hdmi-a-4.html
* igt@kms_draw_crc@draw-method-blt@xrgb8888-ytiled:
- shard-glk: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-glk6/igt@kms_draw_crc@draw-method-blt@xrgb8888-ytiled.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-glk7/igt@kms_draw_crc@draw-method-blt@xrgb8888-ytiled.html
Known issues
------------
Here are the changes found in IGTPW_9704_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@api_intel_bb@blit-reloc-purge-cache:
- shard-dg2: NOTRUN -> [SKIP][5] ([i915#8411])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@api_intel_bb@blit-reloc-purge-cache.html
* igt@device_reset@cold-reset-bound:
- shard-dg2: NOTRUN -> [SKIP][6] ([i915#7701])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-11/igt@device_reset@cold-reset-bound.html
* igt@drm_fdinfo@busy@ccs0:
- shard-dg2: NOTRUN -> [SKIP][7] ([i915#8414]) +20 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@drm_fdinfo@busy@ccs0.html
* igt@drm_fdinfo@most-busy-check-all@rcs0:
- shard-rkl: [PASS][8] -> [FAIL][9] ([i915#7742])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-rkl-1/igt@drm_fdinfo@most-busy-check-all@rcs0.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-1/igt@drm_fdinfo@most-busy-check-all@rcs0.html
* igt@feature_discovery@chamelium:
- shard-dg2: NOTRUN -> [SKIP][10] ([i915#4854])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@feature_discovery@chamelium.html
* igt@gem_bad_reloc@negative-reloc:
- shard-dg1: NOTRUN -> [SKIP][11] ([i915#3281])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-19/igt@gem_bad_reloc@negative-reloc.html
* igt@gem_ccs@block-multicopy-inplace:
- shard-rkl: NOTRUN -> [SKIP][12] ([i915#3555] / [i915#5325])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@gem_ccs@block-multicopy-inplace.html
- shard-tglu: NOTRUN -> [SKIP][13] ([i915#3555] / [i915#5325])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-5/igt@gem_ccs@block-multicopy-inplace.html
* igt@gem_close_race@multigpu-basic-threads:
- shard-dg2: NOTRUN -> [SKIP][14] ([i915#7697])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@gem_close_race@multigpu-basic-threads.html
* igt@gem_ctx_exec@basic-nohangcheck:
- shard-rkl: [PASS][15] -> [FAIL][16] ([i915#6268])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-rkl-6/igt@gem_ctx_exec@basic-nohangcheck.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-1/igt@gem_ctx_exec@basic-nohangcheck.html
* igt@gem_ctx_isolation@preservation-s3@vecs0:
- shard-dg1: [PASS][17] -> [DMESG-WARN][18] ([i915#4423])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg1-16/igt@gem_ctx_isolation@preservation-s3@vecs0.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-13/igt@gem_ctx_isolation@preservation-s3@vecs0.html
* igt@gem_ctx_param@set-priority-not-supported:
- shard-tglu: NOTRUN -> [SKIP][19] ([fdo#109314])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-2/igt@gem_ctx_param@set-priority-not-supported.html
- shard-rkl: NOTRUN -> [SKIP][20] ([fdo#109314])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@gem_ctx_param@set-priority-not-supported.html
* igt@gem_ctx_persistence@file:
- shard-snb: NOTRUN -> [SKIP][21] ([fdo#109271] / [i915#1099]) +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-snb4/igt@gem_ctx_persistence@file.html
* igt@gem_ctx_persistence@heartbeat-stop:
- shard-dg2: NOTRUN -> [SKIP][22] ([i915#8555])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@gem_ctx_persistence@heartbeat-stop.html
* igt@gem_ctx_persistence@legacy-engines-hostile@vebox:
- shard-mtlp: [PASS][23] -> [FAIL][24] ([i915#2410]) +2 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-2/igt@gem_ctx_persistence@legacy-engines-hostile@vebox.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-4/igt@gem_ctx_persistence@legacy-engines-hostile@vebox.html
* igt@gem_eio@in-flight-contexts-10ms:
- shard-mtlp: [PASS][25] -> [ABORT][26] ([i915#7941])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-4/igt@gem_eio@in-flight-contexts-10ms.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-3/igt@gem_eio@in-flight-contexts-10ms.html
* igt@gem_eio@reset-stress:
- shard-dg2: NOTRUN -> [FAIL][27] ([i915#5784])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-2/igt@gem_eio@reset-stress.html
* igt@gem_exec_balancer@bonded-dual:
- shard-dg2: NOTRUN -> [SKIP][28] ([i915#4771])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-11/igt@gem_exec_balancer@bonded-dual.html
* igt@gem_exec_balancer@sliced:
- shard-dg2: NOTRUN -> [SKIP][29] ([i915#4812]) +2 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-2/igt@gem_exec_balancer@sliced.html
* igt@gem_exec_capture@capture-invisible@smem0:
- shard-rkl: NOTRUN -> [SKIP][30] ([i915#6334])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@gem_exec_capture@capture-invisible@smem0.html
- shard-tglu: NOTRUN -> [SKIP][31] ([i915#6334])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-9/igt@gem_exec_capture@capture-invisible@smem0.html
* igt@gem_exec_fair@basic-none-rrul:
- shard-dg1: NOTRUN -> [SKIP][32] ([i915#3539] / [i915#4852])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-16/igt@gem_exec_fair@basic-none-rrul.html
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-rkl: NOTRUN -> [FAIL][33] ([i915#2842])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@gem_exec_fair@basic-none-rrul@rcs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-apl: [PASS][34] -> [FAIL][35] ([i915#2842])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-apl4/igt@gem_exec_fair@basic-pace-share@rcs0.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-apl6/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-glk: [PASS][36] -> [FAIL][37] ([i915#2842])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-glk6/igt@gem_exec_fair@basic-pace-solo@rcs0.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-glk3/igt@gem_exec_fair@basic-pace-solo@rcs0.html
* igt@gem_exec_fair@basic-sync:
- shard-dg2: NOTRUN -> [SKIP][38] ([i915#3539]) +1 similar issue
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@gem_exec_fair@basic-sync.html
* igt@gem_exec_flush@basic-uc-ro-default:
- shard-dg2: NOTRUN -> [SKIP][39] ([i915#3539] / [i915#4852]) +3 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-2/igt@gem_exec_flush@basic-uc-ro-default.html
* igt@gem_exec_params@rsvd2-dirt:
- shard-mtlp: NOTRUN -> [SKIP][40] ([i915#5107])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-6/igt@gem_exec_params@rsvd2-dirt.html
* igt@gem_exec_reloc@basic-concurrent16:
- shard-mtlp: NOTRUN -> [SKIP][41] ([i915#3281]) +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-6/igt@gem_exec_reloc@basic-concurrent16.html
* igt@gem_exec_reloc@basic-write-wc-active:
- shard-rkl: NOTRUN -> [SKIP][42] ([i915#3281]) +4 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-6/igt@gem_exec_reloc@basic-write-wc-active.html
* igt@gem_exec_reloc@basic-write-wc-noreloc:
- shard-dg2: NOTRUN -> [SKIP][43] ([i915#3281]) +7 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@gem_exec_reloc@basic-write-wc-noreloc.html
* igt@gem_exec_schedule@preempt-queue:
- shard-dg1: NOTRUN -> [SKIP][44] ([i915#4812])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-18/igt@gem_exec_schedule@preempt-queue.html
- shard-mtlp: NOTRUN -> [SKIP][45] ([i915#4537] / [i915#4812])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-5/igt@gem_exec_schedule@preempt-queue.html
- shard-dg2: NOTRUN -> [SKIP][46] ([i915#4537] / [i915#4812])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@gem_exec_schedule@preempt-queue.html
* igt@gem_exec_suspend@basic-s4-devices@lmem0:
- shard-dg2: NOTRUN -> [ABORT][47] ([i915#7975] / [i915#8213])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-2/igt@gem_exec_suspend@basic-s4-devices@lmem0.html
* igt@gem_exec_suspend@basic-s4-devices@smem:
- shard-tglu: [PASS][48] -> [ABORT][49] ([i915#7975] / [i915#8213])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-tglu-6/igt@gem_exec_suspend@basic-s4-devices@smem.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-10/igt@gem_exec_suspend@basic-s4-devices@smem.html
* igt@gem_fence_thrash@bo-write-verify-x:
- shard-dg2: NOTRUN -> [SKIP][50] ([i915#4860])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@gem_fence_thrash@bo-write-verify-x.html
* igt@gem_lmem_evict@dontneed-evict-race:
- shard-apl: NOTRUN -> [SKIP][51] ([fdo#109271] / [i915#4613])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-apl6/igt@gem_lmem_evict@dontneed-evict-race.html
* igt@gem_lmem_swapping@heavy-verify-multi-ccs:
- shard-tglu: NOTRUN -> [SKIP][52] ([i915#4613])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-5/igt@gem_lmem_swapping@heavy-verify-multi-ccs.html
* igt@gem_lmem_swapping@heavy-verify-random-ccs:
- shard-rkl: NOTRUN -> [SKIP][53] ([i915#4613]) +3 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-1/igt@gem_lmem_swapping@heavy-verify-random-ccs.html
* igt@gem_lmem_swapping@smem-oom@lmem0:
- shard-dg2: NOTRUN -> [TIMEOUT][54] ([i915#5493])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@gem_lmem_swapping@smem-oom@lmem0.html
* igt@gem_lmem_swapping@verify-random-ccs:
- shard-mtlp: NOTRUN -> [SKIP][55] ([i915#4613]) +1 similar issue
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-6/igt@gem_lmem_swapping@verify-random-ccs.html
* igt@gem_lmem_swapping@verify-random-ccs@lmem0:
- shard-dg1: NOTRUN -> [SKIP][56] ([i915#4565])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-16/igt@gem_lmem_swapping@verify-random-ccs@lmem0.html
* igt@gem_mmap@bad-offset:
- shard-mtlp: NOTRUN -> [SKIP][57] ([i915#4083]) +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-2/igt@gem_mmap@bad-offset.html
* igt@gem_mmap_gtt@basic-write-read:
- shard-mtlp: NOTRUN -> [SKIP][58] ([i915#4077]) +4 similar issues
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-6/igt@gem_mmap_gtt@basic-write-read.html
- shard-dg1: NOTRUN -> [SKIP][59] ([i915#4077])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-14/igt@gem_mmap_gtt@basic-write-read.html
* igt@gem_mmap_wc@write-read-distinct:
- shard-dg2: NOTRUN -> [SKIP][60] ([i915#4083]) +4 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@gem_mmap_wc@write-read-distinct.html
* igt@gem_partial_pwrite_pread@reads-uncached:
- shard-dg2: NOTRUN -> [SKIP][61] ([i915#3282]) +3 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@gem_partial_pwrite_pread@reads-uncached.html
* igt@gem_pwrite@basic-exhaustion:
- shard-rkl: NOTRUN -> [SKIP][62] ([i915#3282])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@gem_pwrite@basic-exhaustion.html
* igt@gem_pxp@protected-encrypted-src-copy-not-readible:
- shard-dg2: NOTRUN -> [SKIP][63] ([i915#4270])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@gem_pxp@protected-encrypted-src-copy-not-readible.html
* igt@gem_pxp@verify-pxp-stale-ctx-execution:
- shard-rkl: NOTRUN -> [SKIP][64] ([i915#4270])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@gem_pxp@verify-pxp-stale-ctx-execution.html
* igt@gem_render_copy@y-tiled-ccs-to-y-tiled-ccs:
- shard-mtlp: NOTRUN -> [SKIP][65] ([i915#8428])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-6/igt@gem_render_copy@y-tiled-ccs-to-y-tiled-ccs.html
* igt@gem_set_tiling_vs_blt@tiled-to-untiled:
- shard-dg2: NOTRUN -> [SKIP][66] ([i915#4079])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@gem_set_tiling_vs_blt@tiled-to-untiled.html
* igt@gem_tiled_blits@basic:
- shard-dg2: NOTRUN -> [SKIP][67] ([i915#4077]) +11 similar issues
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-5/igt@gem_tiled_blits@basic.html
* igt@gem_userptr_blits@coherency-sync:
- shard-rkl: NOTRUN -> [SKIP][68] ([fdo#110542])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-1/igt@gem_userptr_blits@coherency-sync.html
- shard-tglu: NOTRUN -> [SKIP][69] ([fdo#110542])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-6/igt@gem_userptr_blits@coherency-sync.html
* igt@gem_userptr_blits@huge-split:
- shard-apl: [PASS][70] -> [FAIL][71] ([i915#3318])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-apl6/igt@gem_userptr_blits@huge-split.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-apl6/igt@gem_userptr_blits@huge-split.html
* igt@gem_userptr_blits@map-fixed-invalidate-overlap:
- shard-dg2: NOTRUN -> [SKIP][72] ([i915#3297] / [i915#4880])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-5/igt@gem_userptr_blits@map-fixed-invalidate-overlap.html
* igt@gem_userptr_blits@vma-merge:
- shard-rkl: NOTRUN -> [FAIL][73] ([i915#3318])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@gem_userptr_blits@vma-merge.html
- shard-tglu: NOTRUN -> [FAIL][74] ([i915#3318])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-6/igt@gem_userptr_blits@vma-merge.html
* igt@gen3_render_linear_blits:
- shard-rkl: NOTRUN -> [SKIP][75] ([fdo#109289]) +2 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@gen3_render_linear_blits.html
- shard-tglu: NOTRUN -> [SKIP][76] ([fdo#109289]) +1 similar issue
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-8/igt@gen3_render_linear_blits.html
* igt@gen7_exec_parse@basic-allocation:
- shard-mtlp: NOTRUN -> [SKIP][77] ([fdo#109289])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-5/igt@gen7_exec_parse@basic-allocation.html
- shard-dg2: NOTRUN -> [SKIP][78] ([fdo#109289]) +3 similar issues
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@gen7_exec_parse@basic-allocation.html
* igt@gen9_exec_parse@valid-registers:
- shard-dg2: NOTRUN -> [SKIP][79] ([i915#2856]) +3 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@gen9_exec_parse@valid-registers.html
- shard-rkl: NOTRUN -> [SKIP][80] ([i915#2527]) +1 similar issue
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-6/igt@gen9_exec_parse@valid-registers.html
* igt@i915_pm_backlight@basic-brightness:
- shard-dg2: NOTRUN -> [SKIP][81] ([i915#5354] / [i915#7561]) +1 similar issue
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@i915_pm_backlight@basic-brightness.html
* igt@i915_pm_rc6_residency@rc6-idle@rcs0:
- shard-dg1: [PASS][82] -> [FAIL][83] ([i915#3591])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg1-15/igt@i915_pm_rc6_residency@rc6-idle@rcs0.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-13/igt@i915_pm_rc6_residency@rc6-idle@rcs0.html
* igt@i915_pm_rpm@gem-execbuf-stress-pc8:
- shard-mtlp: NOTRUN -> [SKIP][84] ([fdo#109293])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-2/igt@i915_pm_rpm@gem-execbuf-stress-pc8.html
* igt@i915_pm_rpm@modeset-lpsp:
- shard-dg2: [PASS][85] -> [SKIP][86] ([i915#1397])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg2-12/igt@i915_pm_rpm@modeset-lpsp.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@i915_pm_rpm@modeset-lpsp.html
* igt@i915_pm_rpm@modeset-lpsp-stress-no-wait:
- shard-dg2: NOTRUN -> [SKIP][87] ([i915#1397]) +1 similar issue
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-5/igt@i915_pm_rpm@modeset-lpsp-stress-no-wait.html
* igt@i915_pm_rpm@modeset-non-lpsp:
- shard-tglu: NOTRUN -> [SKIP][88] ([fdo#111644] / [i915#1397])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-9/igt@i915_pm_rpm@modeset-non-lpsp.html
* igt@i915_query@query-topology-coherent-slice-mask:
- shard-dg2: NOTRUN -> [SKIP][89] ([i915#6188])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@i915_query@query-topology-coherent-slice-mask.html
* igt@i915_query@query-topology-known-pci-ids:
- shard-dg2: NOTRUN -> [SKIP][90] ([fdo#109303])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@i915_query@query-topology-known-pci-ids.html
* igt@kms_async_flips@alternate-sync-async-flip@pipe-a-edp-1:
- shard-mtlp: [PASS][91] -> [FAIL][92] ([i915#2521])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-8/igt@kms_async_flips@alternate-sync-async-flip@pipe-a-edp-1.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-7/igt@kms_async_flips@alternate-sync-async-flip@pipe-a-edp-1.html
* igt@kms_async_flips@async-flip-with-page-flip-events@pipe-c-hdmi-a-4-y-rc_ccs:
- shard-dg1: NOTRUN -> [SKIP][93] ([i915#8502]) +7 similar issues
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-17/igt@kms_async_flips@async-flip-with-page-flip-events@pipe-c-hdmi-a-4-y-rc_ccs.html
* igt@kms_atomic_transition@plane-all-modeset-transition-fencing-internal-panels:
- shard-dg2: NOTRUN -> [SKIP][94] ([i915#1769] / [i915#3555]) +1 similar issue
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@kms_atomic_transition@plane-all-modeset-transition-fencing-internal-panels.html
* igt@kms_big_fb@4-tiled-64bpp-rotate-90:
- shard-rkl: NOTRUN -> [SKIP][95] ([i915#5286]) +1 similar issue
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@kms_big_fb@4-tiled-64bpp-rotate-90.html
- shard-dg1: NOTRUN -> [SKIP][96] ([i915#4538] / [i915#5286])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-13/igt@kms_big_fb@4-tiled-64bpp-rotate-90.html
* igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-mtlp: [PASS][97] -> [FAIL][98] ([i915#5138])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-4/igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0-hflip.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-2/igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0-hflip.html
* igt@kms_big_fb@linear-32bpp-rotate-90:
- shard-mtlp: NOTRUN -> [SKIP][99] ([fdo#111614]) +3 similar issues
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-6/igt@kms_big_fb@linear-32bpp-rotate-90.html
* igt@kms_big_fb@x-tiled-64bpp-rotate-90:
- shard-rkl: NOTRUN -> [SKIP][100] ([fdo#111614] / [i915#3638])
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@kms_big_fb@x-tiled-64bpp-rotate-90.html
* igt@kms_big_fb@x-tiled-8bpp-rotate-270:
- shard-dg2: NOTRUN -> [SKIP][101] ([fdo#111614]) +1 similar issue
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-2/igt@kms_big_fb@x-tiled-8bpp-rotate-270.html
* igt@kms_big_fb@y-tiled-addfb-size-offset-overflow:
- shard-dg2: NOTRUN -> [SKIP][102] ([i915#5190]) +12 similar issues
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-2/igt@kms_big_fb@y-tiled-addfb-size-offset-overflow.html
- shard-mtlp: NOTRUN -> [SKIP][103] ([i915#6187])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-5/igt@kms_big_fb@y-tiled-addfb-size-offset-overflow.html
* igt@kms_big_fb@yf-tiled-32bpp-rotate-180:
- shard-dg1: NOTRUN -> [SKIP][104] ([i915#4538])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-13/igt@kms_big_fb@yf-tiled-32bpp-rotate-180.html
- shard-mtlp: NOTRUN -> [SKIP][105] ([fdo#111615]) +2 similar issues
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-8/igt@kms_big_fb@yf-tiled-32bpp-rotate-180.html
* igt@kms_big_fb@yf-tiled-8bpp-rotate-90:
- shard-dg2: NOTRUN -> [SKIP][106] ([i915#4538] / [i915#5190]) +6 similar issues
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@kms_big_fb@yf-tiled-8bpp-rotate-90.html
- shard-rkl: NOTRUN -> [SKIP][107] ([fdo#110723]) +3 similar issues
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@kms_big_fb@yf-tiled-8bpp-rotate-90.html
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-async-flip:
- shard-snb: NOTRUN -> [SKIP][108] ([fdo#109271]) +181 similar issues
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-snb1/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-async-flip.html
* igt@kms_ccs@pipe-a-bad-rotation-90-4_tiled_dg2_rc_ccs_cc:
- shard-mtlp: NOTRUN -> [SKIP][109] ([i915#6095]) +7 similar issues
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-4/igt@kms_ccs@pipe-a-bad-rotation-90-4_tiled_dg2_rc_ccs_cc.html
* igt@kms_ccs@pipe-a-bad-rotation-90-yf_tiled_ccs:
- shard-rkl: NOTRUN -> [SKIP][110] ([i915#3734] / [i915#5354] / [i915#6095])
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@kms_ccs@pipe-a-bad-rotation-90-yf_tiled_ccs.html
- shard-dg1: NOTRUN -> [SKIP][111] ([i915#3689] / [i915#5354] / [i915#6095])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-18/igt@kms_ccs@pipe-a-bad-rotation-90-yf_tiled_ccs.html
* igt@kms_ccs@pipe-a-crc-primary-basic-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][112] ([fdo#109271] / [i915#3886])
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-apl3/igt@kms_ccs@pipe-a-crc-primary-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-4_tiled_mtl_mc_ccs:
- shard-rkl: NOTRUN -> [SKIP][113] ([i915#5354] / [i915#6095]) +5 similar issues
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-1/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-4_tiled_mtl_mc_ccs.html
* igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-rkl: NOTRUN -> [SKIP][114] ([i915#3886] / [i915#5354] / [i915#6095]) +2 similar issues
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-6/igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-b-crc-sprite-planes-basic-4_tiled_dg2_rc_ccs:
- shard-dg1: NOTRUN -> [SKIP][115] ([i915#5354] / [i915#6095])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-17/igt@kms_ccs@pipe-b-crc-sprite-planes-basic-4_tiled_dg2_rc_ccs.html
* igt@kms_ccs@pipe-c-bad-pixel-format-y_tiled_gen12_mc_ccs:
- shard-dg2: NOTRUN -> [SKIP][116] ([i915#3689] / [i915#3886] / [i915#5354]) +7 similar issues
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-2/igt@kms_ccs@pipe-c-bad-pixel-format-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-c-crc-primary-rotation-180-4_tiled_mtl_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][117] ([fdo#109271]) +65 similar issues
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-apl3/igt@kms_ccs@pipe-c-crc-primary-rotation-180-4_tiled_mtl_mc_ccs.html
* igt@kms_ccs@pipe-c-random-ccs-data-yf_tiled_ccs:
- shard-rkl: NOTRUN -> [SKIP][118] ([i915#5354]) +10 similar issues
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@kms_ccs@pipe-c-random-ccs-data-yf_tiled_ccs.html
* igt@kms_ccs@pipe-d-crc-primary-basic-y_tiled_gen12_rc_ccs:
- shard-dg2: NOTRUN -> [SKIP][119] ([i915#3689] / [i915#5354]) +17 similar issues
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@kms_ccs@pipe-d-crc-primary-basic-y_tiled_gen12_rc_ccs.html
* igt@kms_ccs@pipe-d-crc-primary-rotation-180-4_tiled_dg2_rc_ccs_cc:
- shard-tglu: NOTRUN -> [SKIP][120] ([i915#5354] / [i915#6095])
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-4/igt@kms_ccs@pipe-d-crc-primary-rotation-180-4_tiled_dg2_rc_ccs_cc.html
* igt@kms_cdclk@mode-transition@pipe-d-hdmi-a-3:
- shard-dg2: NOTRUN -> [SKIP][121] ([i915#4087] / [i915#7213]) +4 similar issues
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@kms_cdclk@mode-transition@pipe-d-hdmi-a-3.html
* igt@kms_cdclk@plane-scaling@pipe-c-dp-2:
- shard-dg2: NOTRUN -> [SKIP][122] ([i915#4087]) +3 similar issues
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@kms_cdclk@plane-scaling@pipe-c-dp-2.html
* igt@kms_chamelium_frames@dp-frame-dump:
- shard-dg2: NOTRUN -> [SKIP][123] ([i915#7828]) +9 similar issues
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-10/igt@kms_chamelium_frames@dp-frame-dump.html
- shard-rkl: NOTRUN -> [SKIP][124] ([i915#7828]) +4 similar issues
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@kms_chamelium_frames@dp-frame-dump.html
- shard-dg1: NOTRUN -> [SKIP][125] ([i915#7828])
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-17/igt@kms_chamelium_frames@dp-frame-dump.html
* igt@kms_color@deep-color:
- shard-dg2: NOTRUN -> [SKIP][126] ([i915#3555]) +3 similar issues
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@kms_color@deep-color.html
* igt@kms_content_protection@atomic@pipe-a-dp-1:
- shard-apl: NOTRUN -> [TIMEOUT][127] ([i915#7173])
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-apl3/igt@kms_content_protection@atomic@pipe-a-dp-1.html
* igt@kms_content_protection@dp-mst-lic-type-1:
- shard-rkl: NOTRUN -> [SKIP][128] ([i915#3116])
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@kms_content_protection@dp-mst-lic-type-1.html
* igt@kms_content_protection@lic:
- shard-dg2: NOTRUN -> [SKIP][129] ([i915#7118])
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@kms_content_protection@lic.html
* igt@kms_content_protection@srm@pipe-a-dp-4:
- shard-dg2: NOTRUN -> [TIMEOUT][130] ([i915#7173])
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-11/igt@kms_content_protection@srm@pipe-a-dp-4.html
* igt@kms_cursor_crc@cursor-rapid-movement-512x170:
- shard-dg2: NOTRUN -> [SKIP][131] ([i915#3359])
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@kms_cursor_crc@cursor-rapid-movement-512x170.html
* igt@kms_cursor_crc@cursor-suspend@pipe-b-vga-1:
- shard-snb: NOTRUN -> [DMESG-WARN][132] ([i915#8841]) +4 similar issues
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-snb6/igt@kms_cursor_crc@cursor-suspend@pipe-b-vga-1.html
* igt@kms_cursor_legacy@2x-flip-vs-cursor-atomic:
- shard-mtlp: NOTRUN -> [SKIP][133] ([fdo#111767] / [i915#3546])
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-2/igt@kms_cursor_legacy@2x-flip-vs-cursor-atomic.html
* igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic:
- shard-mtlp: NOTRUN -> [SKIP][134] ([i915#3546])
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-1/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- shard-rkl: NOTRUN -> [SKIP][135] ([i915#4103])
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-6/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
- shard-tglu: NOTRUN -> [SKIP][136] ([i915#4103])
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-4/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
* igt@kms_cursor_legacy@cursor-vs-flip-toggle:
- shard-mtlp: [PASS][137] -> [FAIL][138] ([i915#8248])
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-2/igt@kms_cursor_legacy@cursor-vs-flip-toggle.html
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-3/igt@kms_cursor_legacy@cursor-vs-flip-toggle.html
* igt@kms_cursor_legacy@cursorb-vs-flipa-varying-size:
- shard-dg2: NOTRUN -> [SKIP][139] ([fdo#109274] / [i915#5354]) +6 similar issues
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@kms_cursor_legacy@cursorb-vs-flipa-varying-size.html
* igt@kms_cursor_legacy@cursorb-vs-flipb-toggle:
- shard-apl: NOTRUN -> [SKIP][140] ([fdo#109271] / [fdo#111767])
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-apl6/igt@kms_cursor_legacy@cursorb-vs-flipb-toggle.html
- shard-snb: NOTRUN -> [SKIP][141] ([fdo#109271] / [fdo#111767]) +2 similar issues
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-snb4/igt@kms_cursor_legacy@cursorb-vs-flipb-toggle.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-apl: [PASS][142] -> [FAIL][143] ([i915#2346]) +1 similar issue
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-apl3/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-apl3/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_dirtyfb@dirtyfb-ioctl@fbc-hdmi-a-1:
- shard-dg2: NOTRUN -> [SKIP][144] ([i915#9227])
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-10/igt@kms_dirtyfb@dirtyfb-ioctl@fbc-hdmi-a-1.html
* igt@kms_dirtyfb@dirtyfb-ioctl@fbc-hdmi-a-4:
- shard-dg1: NOTRUN -> [SKIP][145] ([i915#9227])
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-17/igt@kms_dirtyfb@dirtyfb-ioctl@fbc-hdmi-a-4.html
* igt@kms_dither@fb-8bpc-vs-panel-6bpc@pipe-a-hdmi-a-2:
- shard-rkl: NOTRUN -> [SKIP][146] ([i915#3804])
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@kms_dither@fb-8bpc-vs-panel-6bpc@pipe-a-hdmi-a-2.html
* igt@kms_draw_crc@draw-method-mmap-gtt:
- shard-dg2: NOTRUN -> [SKIP][147] ([i915#8812])
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@kms_draw_crc@draw-method-mmap-gtt.html
* igt@kms_dsc@dsc-with-bpc-formats:
- shard-mtlp: NOTRUN -> [SKIP][148] ([i915#3555] / [i915#3840])
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-5/igt@kms_dsc@dsc-with-bpc-formats.html
* igt@kms_fbcon_fbt@psr-suspend:
- shard-dg2: NOTRUN -> [SKIP][149] ([i915#3469])
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-11/igt@kms_fbcon_fbt@psr-suspend.html
* igt@kms_flip@2x-flip-vs-blocking-wf-vblank:
- shard-rkl: NOTRUN -> [SKIP][150] ([fdo#111767] / [fdo#111825]) +1 similar issue
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@kms_flip@2x-flip-vs-blocking-wf-vblank.html
* igt@kms_flip@2x-flip-vs-fences-interruptible:
- shard-dg2: NOTRUN -> [SKIP][151] ([i915#8381])
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-10/igt@kms_flip@2x-flip-vs-fences-interruptible.html
* igt@kms_flip@2x-flip-vs-suspend-interruptible:
- shard-rkl: NOTRUN -> [SKIP][152] ([fdo#111825]) +1 similar issue
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@kms_flip@2x-flip-vs-suspend-interruptible.html
* igt@kms_flip@2x-modeset-vs-vblank-race:
- shard-dg2: NOTRUN -> [SKIP][153] ([fdo#109274]) +6 similar issues
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@kms_flip@2x-modeset-vs-vblank-race.html
* igt@kms_flip@2x-nonexisting-fb:
- shard-mtlp: NOTRUN -> [SKIP][154] ([i915#3637]) +1 similar issue
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-5/igt@kms_flip@2x-nonexisting-fb.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-dp1:
- shard-apl: [PASS][155] -> [FAIL][156] ([i915#79])
[155]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-apl3/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-dp1.html
[156]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-apl3/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-dp1.html
* igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-downscaling@pipe-a-default-mode:
- shard-mtlp: NOTRUN -> [SKIP][157] ([i915#2672])
[157]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-1/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-downscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-64bpp-ytile-upscaling@pipe-a-valid-mode:
- shard-dg2: NOTRUN -> [SKIP][158] ([i915#2672]) +4 similar issues
[158]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-64bpp-ytile-upscaling@pipe-a-valid-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling@pipe-a-valid-mode:
- shard-dg2: NOTRUN -> [SKIP][159] ([i915#2672] / [i915#3555])
[159]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-5/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling@pipe-a-valid-mode.html
* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-render:
- shard-dg2: [PASS][160] -> [FAIL][161] ([i915#6880]) +2 similar issues
[160]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg2-1/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-render.html
[161]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-render.html
* igt@kms_frontbuffer_tracking@fbc-2p-indfb-fliptrack-mmap-gtt:
- shard-mtlp: NOTRUN -> [SKIP][162] ([i915#8708]) +1 similar issue
[162]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-8/igt@kms_frontbuffer_tracking@fbc-2p-indfb-fliptrack-mmap-gtt.html
- shard-dg1: NOTRUN -> [SKIP][163] ([i915#8708])
[163]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-13/igt@kms_frontbuffer_tracking@fbc-2p-indfb-fliptrack-mmap-gtt.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-draw-blt:
- shard-dg2: NOTRUN -> [SKIP][164] ([i915#5354]) +42 similar issues
[164]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-draw-mmap-wc:
- shard-dg2: NOTRUN -> [SKIP][165] ([i915#8708]) +18 similar issues
[165]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@fbc-tiling-y:
- shard-dg2: NOTRUN -> [SKIP][166] ([i915#5460])
[166]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-11/igt@kms_frontbuffer_tracking@fbc-tiling-y.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-move:
- shard-rkl: NOTRUN -> [SKIP][167] ([i915#3023]) +12 similar issues
[167]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-move.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-onoff:
- shard-mtlp: NOTRUN -> [SKIP][168] ([i915#1825]) +8 similar issues
[168]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-8/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-onoff.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-pgflip-blt:
- shard-rkl: NOTRUN -> [SKIP][169] ([fdo#111825] / [i915#1825]) +11 similar issues
[169]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-pgflip-blt.html
- shard-tglu: NOTRUN -> [SKIP][170] ([fdo#109280]) +1 similar issue
[170]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-7/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-pgflip-blt.html
* igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-mmap-cpu:
- shard-tglu: NOTRUN -> [SKIP][171] ([fdo#110189]) +3 similar issues
[171]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-9/igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-mmap-cpu.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render:
- shard-dg2: NOTRUN -> [SKIP][172] ([i915#3458]) +14 similar issues
[172]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render.html
* igt@kms_frontbuffer_tracking@psr-indfb-scaledprimary:
- shard-dg1: NOTRUN -> [SKIP][173] ([i915#3458])
[173]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-12/igt@kms_frontbuffer_tracking@psr-indfb-scaledprimary.html
* igt@kms_hdr@static-toggle:
- shard-dg2: NOTRUN -> [SKIP][174] ([i915#3555] / [i915#8228])
[174]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@kms_hdr@static-toggle.html
- shard-rkl: NOTRUN -> [SKIP][175] ([i915#3555] / [i915#8228])
[175]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@kms_hdr@static-toggle.html
* igt@kms_hdr@static-toggle-dpms:
- shard-mtlp: NOTRUN -> [SKIP][176] ([i915#3555] / [i915#8228])
[176]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-5/igt@kms_hdr@static-toggle-dpms.html
* igt@kms_plane_lowres@tiling-y:
- shard-mtlp: NOTRUN -> [SKIP][177] ([i915#8821])
[177]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-5/igt@kms_plane_lowres@tiling-y.html
* igt@kms_plane_multiple@tiling-yf:
- shard-rkl: NOTRUN -> [SKIP][178] ([i915#3555]) +3 similar issues
[178]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@kms_plane_multiple@tiling-yf.html
* igt@kms_plane_scaling@intel-max-src-size:
- shard-dg2: NOTRUN -> [SKIP][179] ([i915#6953])
[179]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@kms_plane_scaling@intel-max-src-size.html
* igt@kms_plane_scaling@intel-max-src-size@pipe-a-hdmi-a-1:
- shard-dg1: NOTRUN -> [FAIL][180] ([i915#8292])
[180]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-19/igt@kms_plane_scaling@intel-max-src-size@pipe-a-hdmi-a-1.html
* igt@kms_plane_scaling@plane-downscale-with-modifiers-factor-0-25@pipe-d-dp-4:
- shard-dg2: NOTRUN -> [SKIP][181] ([i915#5176]) +7 similar issues
[181]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-11/igt@kms_plane_scaling@plane-downscale-with-modifiers-factor-0-25@pipe-d-dp-4.html
* igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation@pipe-d-hdmi-a-1:
- shard-dg1: NOTRUN -> [SKIP][182] ([i915#5176]) +19 similar issues
[182]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-19/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation@pipe-d-hdmi-a-1.html
* igt@kms_plane_scaling@plane-upscale-with-rotation-20x20@pipe-a-hdmi-a-1:
- shard-rkl: NOTRUN -> [SKIP][183] ([i915#5176]) +7 similar issues
[183]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@kms_plane_scaling@plane-upscale-with-rotation-20x20@pipe-a-hdmi-a-1.html
- shard-tglu: NOTRUN -> [SKIP][184] ([i915#5176]) +3 similar issues
[184]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-5/igt@kms_plane_scaling@plane-upscale-with-rotation-20x20@pipe-a-hdmi-a-1.html
* igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-factor-0-25@pipe-b-hdmi-a-2:
- shard-rkl: NOTRUN -> [SKIP][185] ([i915#5235]) +5 similar issues
[185]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-6/igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-factor-0-25@pipe-b-hdmi-a-2.html
* igt@kms_plane_scaling@planes-downscale-factor-0-25@pipe-d-hdmi-a-3:
- shard-dg2: NOTRUN -> [SKIP][186] ([i915#5235]) +11 similar issues
[186]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@kms_plane_scaling@planes-downscale-factor-0-25@pipe-d-hdmi-a-3.html
* igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25@pipe-a-hdmi-a-3:
- shard-dg1: NOTRUN -> [SKIP][187] ([i915#5235]) +11 similar issues
[187]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-13/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25@pipe-a-hdmi-a-3.html
* igt@kms_psr2_sf@cursor-plane-move-continuous-exceed-fully-sf:
- shard-rkl: NOTRUN -> [SKIP][188] ([i915#658]) +1 similar issue
[188]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@kms_psr2_sf@cursor-plane-move-continuous-exceed-fully-sf.html
* igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-fully-sf:
- shard-tglu: NOTRUN -> [SKIP][189] ([i915#658])
[189]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-8/igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-fully-sf.html
* igt@kms_psr2_su@page_flip-nv12:
- shard-apl: NOTRUN -> [SKIP][190] ([fdo#109271] / [i915#658])
[190]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-apl4/igt@kms_psr2_su@page_flip-nv12.html
* igt@kms_psr2_su@page_flip-xrgb8888:
- shard-dg2: NOTRUN -> [SKIP][191] ([i915#658]) +4 similar issues
[191]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-5/igt@kms_psr2_su@page_flip-xrgb8888.html
* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-rkl: NOTRUN -> [SKIP][192] ([i915#1072]) +2 similar issues
[192]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@kms_psr@psr2_cursor_plane_onoff.html
* igt@kms_psr@psr2_dpms:
- shard-dg2: NOTRUN -> [SKIP][193] ([i915#1072]) +4 similar issues
[193]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@kms_psr@psr2_dpms.html
* igt@kms_rotation_crc@primary-rotation-90:
- shard-dg2: NOTRUN -> [SKIP][194] ([i915#4235])
[194]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-5/igt@kms_rotation_crc@primary-rotation-90.html
* igt@kms_rotation_crc@primary-y-tiled-reflect-x-90:
- shard-dg2: NOTRUN -> [SKIP][195] ([i915#4235] / [i915#5190])
[195]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-2/igt@kms_rotation_crc@primary-y-tiled-reflect-x-90.html
* igt@kms_selftest@drm_cmdline:
- shard-dg2: NOTRUN -> [SKIP][196] ([i915#8661])
[196]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@kms_selftest@drm_cmdline.html
* igt@kms_setmode@basic-clone-single-crtc:
- shard-rkl: NOTRUN -> [SKIP][197] ([i915#3555] / [i915#4098])
[197]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-2/igt@kms_setmode@basic-clone-single-crtc.html
* igt@kms_sysfs_edid_timing:
- shard-dg2: [PASS][198] -> [FAIL][199] ([IGT#2])
[198]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg2-12/igt@kms_sysfs_edid_timing.html
[199]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@kms_sysfs_edid_timing.html
* igt@kms_tv_load_detect@load-detect:
- shard-dg2: NOTRUN -> [SKIP][200] ([fdo#109309])
[200]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@kms_tv_load_detect@load-detect.html
* igt@kms_vblank@pipe-c-ts-continuation-modeset-rpm:
- shard-rkl: NOTRUN -> [SKIP][201] ([i915#4070] / [i915#6768]) +1 similar issue
[201]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@kms_vblank@pipe-c-ts-continuation-modeset-rpm.html
* igt@kms_vblank@pipe-d-query-forked-busy-hang:
- shard-rkl: NOTRUN -> [SKIP][202] ([i915#4070] / [i915#533] / [i915#6768]) +2 similar issues
[202]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@kms_vblank@pipe-d-query-forked-busy-hang.html
* igt@kms_vrr@flip-basic:
- shard-mtlp: NOTRUN -> [SKIP][203] ([i915#3555] / [i915#8808])
[203]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-1/igt@kms_vrr@flip-basic.html
* igt@perf@non-zero-reason@0-rcs0:
- shard-dg2: [PASS][204] -> [FAIL][205] ([i915#7484])
[204]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg2-3/igt@perf@non-zero-reason@0-rcs0.html
[205]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-10/igt@perf@non-zero-reason@0-rcs0.html
* igt@perf@unprivileged-single-ctx-counters:
- shard-rkl: NOTRUN -> [SKIP][206] ([i915#2433])
[206]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-1/igt@perf@unprivileged-single-ctx-counters.html
* igt@perf_pmu@cpu-hotplug:
- shard-dg2: NOTRUN -> [SKIP][207] ([i915#8850])
[207]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@perf_pmu@cpu-hotplug.html
* igt@perf_pmu@most-busy-idle-check-all@rcs0:
- shard-mtlp: [PASS][208] -> [FAIL][209] ([i915#5234])
[208]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-1/igt@perf_pmu@most-busy-idle-check-all@rcs0.html
[209]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-7/igt@perf_pmu@most-busy-idle-check-all@rcs0.html
* igt@perf_pmu@rc6@other-idle-gt0:
- shard-dg2: NOTRUN -> [SKIP][210] ([i915#8516])
[210]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-11/igt@perf_pmu@rc6@other-idle-gt0.html
* igt@prime_vgem@basic-write:
- shard-rkl: NOTRUN -> [SKIP][211] ([fdo#109295] / [i915#3291] / [i915#3708])
[211]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-2/igt@prime_vgem@basic-write.html
* igt@prime_vgem@fence-flip-hang:
- shard-rkl: NOTRUN -> [SKIP][212] ([fdo#109295] / [i915#3708])
[212]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@prime_vgem@fence-flip-hang.html
* igt@sysfs_heartbeat_interval@precise@vecs0:
- shard-mtlp: [PASS][213] -> [FAIL][214] ([i915#8332])
[213]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-1/igt@sysfs_heartbeat_interval@precise@vecs0.html
[214]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-5/igt@sysfs_heartbeat_interval@precise@vecs0.html
* igt@v3d/v3d_get_param@get-bad-flags:
- shard-mtlp: NOTRUN -> [SKIP][215] ([i915#2575]) +1 similar issue
[215]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-1/igt@v3d/v3d_get_param@get-bad-flags.html
* igt@v3d/v3d_job_submission@array-job-submission:
- shard-dg2: NOTRUN -> [SKIP][216] ([i915#2575]) +8 similar issues
[216]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-2/igt@v3d/v3d_job_submission@array-job-submission.html
* igt@v3d/v3d_perfmon@get-values-valid-perfmon:
- shard-rkl: NOTRUN -> [SKIP][217] ([fdo#109315]) +3 similar issues
[217]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-1/igt@v3d/v3d_perfmon@get-values-valid-perfmon.html
- shard-tglu: NOTRUN -> [SKIP][218] ([fdo#109315] / [i915#2575])
[218]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-5/igt@v3d/v3d_perfmon@get-values-valid-perfmon.html
* igt@vc4/vc4_label_bo@set-bad-handle:
- shard-tglu: NOTRUN -> [SKIP][219] ([i915#2575]) +1 similar issue
[219]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-10/igt@vc4/vc4_label_bo@set-bad-handle.html
* igt@vc4/vc4_label_bo@set-kernel-name:
- shard-mtlp: NOTRUN -> [SKIP][220] ([i915#7711])
[220]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-2/igt@vc4/vc4_label_bo@set-kernel-name.html
* igt@vc4/vc4_mmap@mmap-bo:
- shard-dg2: NOTRUN -> [SKIP][221] ([i915#7711]) +5 similar issues
[221]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-11/igt@vc4/vc4_mmap@mmap-bo.html
* igt@vc4/vc4_wait_seqno@bad-seqno-1ns:
- shard-rkl: NOTRUN -> [SKIP][222] ([i915#7711]) +5 similar issues
[222]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@vc4/vc4_wait_seqno@bad-seqno-1ns.html
#### Possible fixes ####
* igt@gem_ctx_exec@basic-nohangcheck:
- shard-mtlp: [FAIL][223] ([i915#6121]) -> [PASS][224]
[223]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-5/igt@gem_ctx_exec@basic-nohangcheck.html
[224]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-8/igt@gem_ctx_exec@basic-nohangcheck.html
* igt@gem_ctx_persistence@engines-hang@vcs0:
- shard-mtlp: [FAIL][225] ([i915#2410]) -> [PASS][226] +1 similar issue
[225]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-3/igt@gem_ctx_persistence@engines-hang@vcs0.html
[226]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-2/igt@gem_ctx_persistence@engines-hang@vcs0.html
* igt@gem_exec_endless@dispatch@bcs0:
- shard-dg2: [TIMEOUT][227] ([i915#3778] / [i915#7016] / [i915#7921]) -> [PASS][228]
[227]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg2-11/igt@gem_exec_endless@dispatch@bcs0.html
[228]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-3/igt@gem_exec_endless@dispatch@bcs0.html
* igt@gem_exec_fair@basic-deadline:
- shard-rkl: [FAIL][229] ([i915#2846]) -> [PASS][230]
[229]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-rkl-2/igt@gem_exec_fair@basic-deadline.html
[230]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-4/igt@gem_exec_fair@basic-deadline.html
- shard-glk: [FAIL][231] ([i915#2846]) -> [PASS][232]
[231]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-glk8/igt@gem_exec_fair@basic-deadline.html
[232]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-glk4/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-glk: [FAIL][233] ([i915#2842]) -> [PASS][234] +1 similar issue
[233]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-glk1/igt@gem_exec_fair@basic-pace@rcs0.html
[234]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-glk8/igt@gem_exec_fair@basic-pace@rcs0.html
* igt@i915_pm_rpm@dpms-non-lpsp:
- shard-dg2: [SKIP][235] ([i915#1397]) -> [PASS][236]
[235]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg2-12/igt@i915_pm_rpm@dpms-non-lpsp.html
[236]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-6/igt@i915_pm_rpm@dpms-non-lpsp.html
* igt@i915_pm_rpm@modeset-lpsp:
- shard-rkl: [SKIP][237] ([i915#1397]) -> [PASS][238] +1 similar issue
[237]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-rkl-4/igt@i915_pm_rpm@modeset-lpsp.html
[238]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@i915_pm_rpm@modeset-lpsp.html
* igt@i915_pm_rpm@modeset-non-lpsp-stress:
- shard-dg1: [SKIP][239] ([i915#1397]) -> [PASS][240] +1 similar issue
[239]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg1-19/igt@i915_pm_rpm@modeset-non-lpsp-stress.html
[240]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-12/igt@i915_pm_rpm@modeset-non-lpsp-stress.html
* igt@kms_big_fb@4-tiled-max-hw-stride-32bpp-rotate-0-async-flip:
- shard-mtlp: [FAIL][241] ([i915#3743]) -> [PASS][242] +2 similar issues
[241]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-8/igt@kms_big_fb@4-tiled-max-hw-stride-32bpp-rotate-0-async-flip.html
[242]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-6/igt@kms_big_fb@4-tiled-max-hw-stride-32bpp-rotate-0-async-flip.html
* igt@kms_pipe_crc_basic@suspend-read-crc@pipe-a-dp-1:
- shard-apl: [ABORT][243] ([i915#180]) -> [PASS][244]
[243]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-apl2/igt@kms_pipe_crc_basic@suspend-read-crc@pipe-a-dp-1.html
[244]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-apl1/igt@kms_pipe_crc_basic@suspend-read-crc@pipe-a-dp-1.html
* igt@kms_plane_scaling@intel-max-src-size@pipe-a-hdmi-a-1:
- shard-tglu: [FAIL][245] ([i915#8292]) -> [PASS][246]
[245]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-tglu-6/igt@kms_plane_scaling@intel-max-src-size@pipe-a-hdmi-a-1.html
[246]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-8/igt@kms_plane_scaling@intel-max-src-size@pipe-a-hdmi-a-1.html
* igt@kms_plane_scaling@plane-upscale-with-modifiers-20x20@pipe-a-hdmi-a-2:
- shard-rkl: [ABORT][247] -> [PASS][248]
[247]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-rkl-4/igt@kms_plane_scaling@plane-upscale-with-modifiers-20x20@pipe-a-hdmi-a-2.html
[248]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-2/igt@kms_plane_scaling@plane-upscale-with-modifiers-20x20@pipe-a-hdmi-a-2.html
* igt@kms_vblank@pipe-c-query-forked-busy-hang:
- shard-dg2: [DMESG-WARN][249] -> [PASS][250]
[249]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg2-3/igt@kms_vblank@pipe-c-query-forked-busy-hang.html
[250]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-11/igt@kms_vblank@pipe-c-query-forked-busy-hang.html
* igt@perf_pmu@busy-double-start@vcs1:
- shard-mtlp: [FAIL][251] ([i915#4349]) -> [PASS][252] +2 similar issues
[251]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-1/igt@perf_pmu@busy-double-start@vcs1.html
[252]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-3/igt@perf_pmu@busy-double-start@vcs1.html
* igt@sysfs_timeslice_duration@timeout@vecs0:
- shard-mtlp: [ABORT][253] ([i915#8521] / [i915#8865]) -> [PASS][254]
[253]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-3/igt@sysfs_timeslice_duration@timeout@vecs0.html
[254]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-1/igt@sysfs_timeslice_duration@timeout@vecs0.html
#### Warnings ####
* igt@gem_lmem_swapping@smem-oom@lmem0:
- shard-dg1: [DMESG-WARN][255] ([i915#4936] / [i915#5493]) -> [TIMEOUT][256] ([i915#5493])
[255]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg1-16/igt@gem_lmem_swapping@smem-oom@lmem0.html
[256]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-14/igt@gem_lmem_swapping@smem-oom@lmem0.html
* igt@gem_spin_batch@user-each:
- shard-mtlp: [DMESG-FAIL][257] ([i915#9121]) -> [DMESG-FAIL][258] ([i915#8962] / [i915#9121])
[257]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-4/igt@gem_spin_batch@user-each.html
[258]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-4/igt@gem_spin_batch@user-each.html
* igt@kms_async_flips@crc@pipe-a-edp-1:
- shard-mtlp: [DMESG-FAIL][259] ([i915#1982] / [i915#8561]) -> [DMESG-FAIL][260] ([i915#8561])
[259]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-6/igt@kms_async_flips@crc@pipe-a-edp-1.html
[260]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-8/igt@kms_async_flips@crc@pipe-a-edp-1.html
* igt@kms_content_protection@content_type_change:
- shard-dg2: [SKIP][261] ([i915#7118]) -> [SKIP][262] ([i915#7118] / [i915#7162])
[261]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg2-6/igt@kms_content_protection@content_type_change.html
[262]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-12/igt@kms_content_protection@content_type_change.html
* igt@kms_content_protection@mei_interface:
- shard-rkl: [SKIP][263] ([i915#7118]) -> [SKIP][264] ([fdo#109300])
[263]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-rkl-4/igt@kms_content_protection@mei_interface.html
[264]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@kms_content_protection@mei_interface.html
- shard-dg1: [SKIP][265] ([i915#7116]) -> [SKIP][266] ([fdo#109300])
[265]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg1-17/igt@kms_content_protection@mei_interface.html
[266]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-16/igt@kms_content_protection@mei_interface.html
- shard-tglu: [SKIP][267] ([i915#6944] / [i915#7116] / [i915#7118]) -> [SKIP][268] ([fdo#109300])
[267]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-tglu-7/igt@kms_content_protection@mei_interface.html
[268]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-tglu-5/igt@kms_content_protection@mei_interface.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-mtlp: [DMESG-FAIL][269] ([i915#2017] / [i915#5954]) -> [FAIL][270] ([i915#2346])
[269]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-mtlp-4/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[270]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-mtlp-7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_force_connector_basic@force-load-detect:
- shard-rkl: [SKIP][271] ([fdo#109285] / [i915#4098]) -> [SKIP][272] ([fdo#109285])
[271]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-rkl-4/igt@kms_force_connector_basic@force-load-detect.html
[272]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-rkl-7/igt@kms_force_connector_basic@force-load-detect.html
* igt@kms_psr@primary_page_flip:
- shard-dg1: [SKIP][273] ([i915#1072]) -> [SKIP][274] ([i915#1072] / [i915#4078])
[273]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg1-15/igt@kms_psr@primary_page_flip.html
[274]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg1-18/igt@kms_psr@primary_page_flip.html
* igt@prime_mmap@test_aperture_limit@test_aperture_limit-smem:
- shard-dg2: [INCOMPLETE][275] ([i915#5493]) -> [CRASH][276] ([i915#7331])
[275]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13587/shard-dg2-6/igt@prime_mmap@test_aperture_limit@test_aperture_limit-smem.html
[276]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/shard-dg2-11/igt@prime_mmap@test_aperture_limit@test_aperture_limit-smem.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[IGT#2]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/2
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109293]: https://bugs.freedesktop.org/show_bug.cgi?id=109293
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#109300]: https://bugs.freedesktop.org/show_bug.cgi?id=109300
[fdo#109303]: https://bugs.freedesktop.org/show_bug.cgi?id=109303
[fdo#109309]: https://bugs.freedesktop.org/show_bug.cgi?id=109309
[fdo#109314]: https://bugs.freedesktop.org/show_bug.cgi?id=109314
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#110542]: https://bugs.freedesktop.org/show_bug.cgi?id=110542
[fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615
[fdo#111644]: https://bugs.freedesktop.org/show_bug.cgi?id=111644
[fdo#111767]: https://bugs.freedesktop.org/show_bug.cgi?id=111767
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1099]: https://gitlab.freedesktop.org/drm/intel/issues/1099
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#1769]: https://gitlab.freedesktop.org/drm/intel/issues/1769
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2017]: https://gitlab.freedesktop.org/drm/intel/issues/2017
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2410]: https://gitlab.freedesktop.org/drm/intel/issues/2410
[i915#2433]: https://gitlab.freedesktop.org/drm/intel/issues/2433
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846
[i915#2856]: https://gitlab.freedesktop.org/drm/intel/issues/2856
[i915#3023]: https://gitlab.freedesktop.org/drm/intel/issues/3023
[i915#3116]: https://gitlab.freedesktop.org/drm/intel/issues/3116
[i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297
[i915#3318]: https://gitlab.freedesktop.org/drm/intel/issues/3318
[i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359
[i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458
[i915#3469]: https://gitlab.freedesktop.org/drm/intel/issues/3469
[i915#3539]: https://gitlab.freedesktop.org/drm/intel/issues/3539
[i915#3546]: https://gitlab.freedesktop.org/drm/intel/issues/3546
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3591]: https://gitlab.freedesktop.org/drm/intel/issues/3591
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734
[i915#3743]: https://gitlab.freedesktop.org/drm/intel/issues/3743
[i915#3778]: https://gitlab.freedesktop.org/drm/intel/issues/3778
[i915#3804]: https://gitlab.freedesktop.org/drm/intel/issues/3804
[i915#3840]: https://gitlab.freedesktop.org/drm/intel/issues/3840
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[i915#4079]: https://gitlab.freedesktop.org/drm/intel/issues/4079
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4087]: https://gitlab.freedesktop.org/drm/intel/issues/4087
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4235]: https://gitlab.freedesktop.org/drm/intel/issues/4235
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#4349]: https://gitlab.freedesktop.org/drm/intel/issues/4349
[i915#4423]: https://gitlab.freedesktop.org/drm/intel/issues/4423
[i915#4537]: https://gitlab.freedesktop.org/drm/intel/issues/4537
[i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538
[i915#4565]: https://gitlab.freedesktop.org/drm/intel/issues/4565
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4771]: https://gitlab.freedesktop.org/drm/intel/issues/4771
[i915#4812]: https://gitlab.freedesktop.org/drm/intel/issues/4812
[i915#4852]: https://gitlab.freedesktop.org/drm/intel/issues/4852
[i915#4854]: https://gitlab.freedesktop.org/drm/intel/issues/4854
[i915#4860]: https://gitlab.freedesktop.org/drm/intel/issues/4860
[i915#4880]: https://gitlab.freedesktop.org/drm/intel/issues/4880
[i915#4936]: https://gitlab.freedesktop.org/drm/intel/issues/4936
[i915#5107]: https://gitlab.freedesktop.org/drm/intel/issues/5107
[i915#5138]: https://gitlab.freedesktop.org/drm/intel/issues/5138
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5190]: https://gitlab.freedesktop.org/drm/intel/issues/5190
[i915#5234]: https://gitlab.freedesktop.org/drm/intel/issues/5234
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5325]: https://gitlab.freedesktop.org/drm/intel/issues/5325
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5354]: https://gitlab.freedesktop.org/drm/intel/issues/5354
[i915#5460]: https://gitlab.freedesktop.org/drm/intel/issues/5460
[i915#5493]: https://gitlab.freedesktop.org/drm/intel/issues/5493
[i915#5784]: https://gitlab.freedesktop.org/drm/intel/issues/5784
[i915#5954]: https://gitlab.freedesktop.org/drm/intel/issues/5954
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6121]: https://gitlab.freedesktop.org/drm/intel/issues/6121
[i915#6187]: https://gitlab.freedesktop.org/drm/intel/issues/6187
[i915#6188]: https://gitlab.freedesktop.org/drm/intel/issues/6188
[i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268
[i915#6334]: https://gitlab.freedesktop.org/drm/intel/issues/6334
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6768]: https://gitlab.freedesktop.org/drm/intel/issues/6768
[i915#6880]: https://gitlab.freedesktop.org/drm/intel/issues/6880
[i915#6944]: https://gitlab.freedesktop.org/drm/intel/issues/6944
[i915#6953]: https://gitlab.freedesktop.org/drm/intel/issues/6953
[i915#7016]: https://gitlab.freedesktop.org/drm/intel/issues/7016
[i915#7116]: https://gitlab.freedesktop.org/drm/intel/issues/7116
[i915#7118]: https://gitlab.freedesktop.org/drm/intel/issues/7118
[i915#7162]: https://gitlab.freedesktop.org/drm/intel/issues/7162
[i915#7173]: https://gitlab.freedesktop.org/drm/intel/issues/7173
[i915#7213]: https://gitlab.freedesktop.org/drm/intel/issues/7213
[i915#7331]: https://gitlab.freedesktop.org/drm/intel/issues/7331
[i915#7484]: https://gitlab.freedesktop.org/drm/intel/issues/7484
[i915#7561]: https://gitlab.freedesktop.org/drm/intel/issues/7561
[i915#7697]: https://gitlab.freedesktop.org/drm/intel/issues/7697
[i915#7701]: https://gitlab.freedesktop.org/drm/intel/issues/7701
[i915#7711]: https://gitlab.freedesktop.org/drm/intel/issues/7711
[i915#7742]: https://gitlab.freedesktop.org/drm/intel/issues/7742
[i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#7921]: https://gitlab.freedesktop.org/drm/intel/issues/7921
[i915#7941]: https://gitlab.freedesktop.org/drm/intel/issues/7941
[i915#7975]: https://gitlab.freedesktop.org/drm/intel/issues/7975
[i915#8213]: https://gitlab.freedesktop.org/drm/intel/issues/8213
[i915#8228]: https://gitlab.freedesktop.org/drm/intel/issues/8228
[i915#8248]: https://gitlab.freedesktop.org/drm/intel/issues/8248
[i915#8292]: https://gitlab.freedesktop.org/drm/intel/issues/8292
[i915#8332]: https://gitlab.freedesktop.org/drm/intel/issues/8332
[i915#8381]: https://gitlab.freedesktop.org/drm/intel/issues/8381
[i915#8411]: https://gitlab.freedesktop.org/drm/intel/issues/8411
[i915#8414]: https://gitlab.freedesktop.org/drm/intel/issues/8414
[i915#8428]: https://gitlab.freedesktop.org/drm/intel/issues/8428
[i915#8502]: https://gitlab.freedesktop.org/drm/intel/issues/8502
[i915#8516]: https://gitlab.freedesktop.org/drm/intel/issues/8516
[i915#8521]: https://gitlab.freedesktop.org/drm/intel/issues/8521
[i915#8555]: https://gitlab.freedesktop.org/drm/intel/issues/8555
[i915#8561]: https://gitlab.freedesktop.org/drm/intel/issues/8561
[i915#8661]: https://gitlab.freedesktop.org/drm/intel/issues/8661
[i915#8708]: https://gitlab.freedesktop.org/drm/intel/issues/8708
[i915#8808]: https://gitlab.freedesktop.org/drm/intel/issues/8808
[i915#8812]: https://gitlab.freedesktop.org/drm/intel/issues/8812
[i915#8821]: https://gitlab.freedesktop.org/drm/intel/issues/8821
[i915#8841]: https://gitlab.freedesktop.org/drm/intel/issues/8841
[i915#8850]: https://gitlab.freedesktop.org/drm/intel/issues/8850
[i915#8865]: https://gitlab.freedesktop.org/drm/intel/issues/8865
[i915#8962]: https://gitlab.freedesktop.org/drm/intel/issues/8962
[i915#9067]: https://gitlab.freedesktop.org/drm/intel/issues/9067
[i915#9121]: https://gitlab.freedesktop.org/drm/intel/issues/9121
[i915#9227]: https://gitlab.freedesktop.org/drm/intel/issues/9227
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_7463 -> IGTPW_9704
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_13587: 8152aa47d7b14683059ec856ffa99e2d86acfc8b @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_9704: 9704
IGT_7463: 7463
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9704/index.html
[-- Attachment #2: Type: text/html, Size: 89067 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan
2023-09-01 12:39 ` Modem, Bhanuprakash
@ 2023-09-04 8:13 ` Mauro Carvalho Chehab
0 siblings, 0 replies; 13+ messages in thread
From: Mauro Carvalho Chehab @ 2023-09-04 8:13 UTC (permalink / raw)
To: Modem, Bhanuprakash; +Cc: igt-dev
On Fri, 1 Sep 2023 18:09:30 +0530
"Modem, Bhanuprakash" <bhanuprakash.modem@intel.com> wrote:
> Hi Mauro,
>
> On Fri-01-09-2023 03:38 pm, Mauro Carvalho Chehab wrote:
> > On Fri, 1 Sep 2023 14:32:09 +0530
> > "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com> wrote:
> >
> >> Hi Mauro,
> >>
> >> On Fri-01-09-2023 12:50 pm, Mauro Carvalho Chehab wrote:
> >>> On Fri, 1 Sep 2023 10:48:08 +0530
> >>> Bhanuprakash Modem <bhanuprakash.modem@intel.com> wrote:
> >>>
> >>>> As non-Intel vendors also contributing to KMS tests, allow
> >>>> them to re-use the existing testplan documentation along with
> >>>> their own definitions of field:values pair in test config json.
> >>>>
> >>>> Instead of aborting, just throw a warning about this unrecognized
> >>>> field:values.
> >>>>
> >>>> Example:
> >>>> tests/kms_color.c:994: Warning: unrecognized field in tests/kms_test_config.json ==> Foo: bla
> >>>
> >>> IMO, there's no need to to that. I mean, if someone wants to add
> >>> a new field, he can just patch tests/kms_test_config.json, adding the
> >>> new "Foo" field at kms_test_config.json:
> >>
> >> Non-Intel people may not use kms_test_config.json since it is designed
> >> for Intel supported (tests/kms_*.c & tests/intel/kms_*.c) tests
> >> (Probably we may need to rename it to intel_kms_test_config.json).
> >
> > The infra is designed to be generic, and not Intel driver specific.
> > I'm even sending patches to Kernel upstream to also use it:
> >
> > https://lore.kernel.org/linux-doc/cover.1693550658.git.mchehab@kernel.org/T/#t
> >
> >> So, non-Intel vendors are also allowed to include few kms tests
> >> (tests/kms_*.c) in their own testplan. Also, we can't restrict them to
> >> use the same testplan as kms_test_config.json.
> >
> > Hmm... so you're thinking about having a tests/kms_foo.c file that will
> > be included on both:
> >
> > vendor_a/kms_test_config.json
> >
> > and:
> >
> > vendor_b/kms_test_config.json
> >
> > Yes, that's possible. We actually have one or two cases at i915
> > and xe for some tests that aren't driver-specific. As the i915
> > JSON config file has an extra field ("Feature"), I added it to
> > Xe driver as well. This is used currently only for those
> > generic tests that are used on both.
> >
> >> Example:
> >> Suppose, some non-Intel vendor (xyz) created a xyz_kms_test_config.json
> >> with the "Foo" field defined in it, and updated the documentation of
> >> tests/kms_*.c accordingly. Since Intel's kms_test_config.json is also
> >> using tests/kms_*.c and not aware of "Foo" can lead the failure.
> >
> > Currently, the developer who created/updated vendor_a/kms_test_config.json
> > and tests/kms_foo.c will have a compilation error pointing to it. Such
> > developer will then know that the new field also needs to be at
> > vendor_b/kms_test_config.json and can submit a patch against it to
> > solve the error.
>
> Agreed, but the vendor_b needs to maintain something (field:values) that
> he don't even know/care about.
Well, it is either documenting something on a test he'll be using, or
the new test should be excluded from vendor_b/kms_test_config.json.
> >
> > If we apply your patch, it means that it will generate a warning and
> > someone from vendor_b will need later to identify what happened and
> > copy the (possible) definition from vendor_a/kms_test_config.json to
> > suppress the warning.
>
> Yeah, There is no way to suppress the warning except maintaining the
> definitions in both places.
There is an alternative: have one or more "core" ("common"?) json files
for tests that are driver agnostic. I almost did that instead of adding
a couple of core tests to both xe and i915.
> > It works, but it means an extra step. So, while I would prefer to not
> > merge this change, I won't oppose on converting it into a warning.
> > If you decide to go ahead and merge it, you can add my acked-by.
>
> We can hold this for sometime, till we get the better solution.
Ok.
Regards,
Mauro
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2023-09-04 8:13 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-09-01 5:18 [igt-dev] [i-g-t] scripts/test_list: Allow unrecognized field:values in testplan Bhanuprakash Modem
2023-09-01 6:17 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2023-09-01 6:51 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-09-01 6:51 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2023-09-01 7:20 ` [igt-dev] [i-g-t] " Mauro Carvalho Chehab
2023-09-01 9:02 ` Modem, Bhanuprakash
2023-09-01 10:08 ` Mauro Carvalho Chehab
2023-09-01 12:39 ` Modem, Bhanuprakash
2023-09-04 8:13 ` Mauro Carvalho Chehab
2023-09-01 10:22 ` [igt-dev] ✗ GitLab.Pipeline: warning for scripts/test_list: Allow unrecognized field:values in testplan (rev2) Patchwork
2023-09-01 10:49 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-09-01 10:50 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-09-01 19:30 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.