[igt-dev] [PATCH i-g-t] lib/igt_kms: only check chamelium's presence in chamelium tests

[igt-dev] [PATCH i-g-t] lib/igt_kms: only check chamelium's presence in chamelium tests

[Kunal Joshi]

Avoid checking if chamelium is present or not in non chamelium
tests as its just an overhead.

Cc: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com>
---
 lib/igt_kms.c | 31 ++++++++++++++++++-------------
 1 file changed, 18 insertions(+), 13 deletions(-)

diff --git a/lib/igt_kms.c b/lib/igt_kms.c
index 08d429a8..397635d8 100644
--- a/lib/igt_kms.c
+++ b/lib/igt_kms.c
@@ -1958,21 +1958,26 @@ void igt_display_require(igt_display_t *display, int drm_fd)
 
 #ifdef HAVE_CHAMELIUM
 	{
-		struct chamelium *chamelium;
-
-		chamelium = chamelium_init_rpc_only();
-		if (chamelium) {
-			igt_abort_on_f(!chamelium_wait_reachable(chamelium, 20),
-				       "cannot reach the configured chamelium!\n");
-			igt_abort_on_f(!chamelium_plug_all(chamelium),
-				       "failed to plug all the chamelium ports!\n");
-			igt_abort_on_f(!chamelium_wait_all_configured_ports_connected(chamelium, drm_fd),
-				       "not all configured chamelium ports are connected!\n");
-			chamelium_deinit_rpc_only(chamelium);
-		}
-	}
+		if (strstr(igt_test_name(), "feature_discovery") != NULL ||
+		    strstr(igt_test_name(), "cham") != NULL) {
+
+			struct chamelium *chamelium;
+
+			chamelium = chamelium_init_rpc_only();
+			if (chamelium) {
+				igt_abort_on_f(!chamelium_wait_reachable(chamelium, 20),
+					       "cannot reach the configured chamelium!\n");
+				igt_abort_on_f(!chamelium_plug_all(chamelium),
+					       "failed to plug all the chamelium ports!\n");
+				igt_abort_on_f(!chamelium_wait_all_configured_ports_connected(chamelium, drm_fd),
+					       "not all configured chamelium ports are connected!\n");
+				chamelium_deinit_rpc_only(chamelium);
+			}
+		}
+	}
 #endif
 
+
 	/*
 	 * With non-contiguous pipes display, crtc mapping is not always same
 	 * as pipe mapping, In i915 pipe is enum id of i915's crtc object.
-- 
2.25.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t] lib/igt_kms: only check chamelium's presence in chamelium tests

[Martin Peres]

On 22/03/2021 07:26, Kunal Joshi wrote:
> Avoid checking if chamelium is present or not in non chamelium
> tests as its just an overhead.

The point of doing this was to stop having screens in CI and instead 
mostly have chameliums. This means that we need to make sure the 
chamelium exposes all the ports before starting a KMS test, since some 
tests may have left the screens disconnected.

Is that making sense?

> 
> Cc: Petri Latvala <petri.latvala@intel.com>
> Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com>
> ---
>   lib/igt_kms.c | 31 ++++++++++++++++++-------------
>   1 file changed, 18 insertions(+), 13 deletions(-)
> 
> diff --git a/lib/igt_kms.c b/lib/igt_kms.c
> index 08d429a8..397635d8 100644
> --- a/lib/igt_kms.c
> +++ b/lib/igt_kms.c
> @@ -1958,21 +1958,26 @@ void igt_display_require(igt_display_t *display, int drm_fd)
>   
>   #ifdef HAVE_CHAMELIUM
>   	{
> -		struct chamelium *chamelium;
> -
> -		chamelium = chamelium_init_rpc_only();
> -		if (chamelium) {
> -			igt_abort_on_f(!chamelium_wait_reachable(chamelium, 20),
> -				       "cannot reach the configured chamelium!\n");
> -			igt_abort_on_f(!chamelium_plug_all(chamelium),
> -				       "failed to plug all the chamelium ports!\n");
> -			igt_abort_on_f(!chamelium_wait_all_configured_ports_connected(chamelium, drm_fd),
> -				       "not all configured chamelium ports are connected!\n");
> -			chamelium_deinit_rpc_only(chamelium);
> -		}
> -	}
> +		if (strstr(igt_test_name(), "feature_discovery") != NULL ||
> +		    strstr(igt_test_name(), "cham") != NULL) {
> +
> +			struct chamelium *chamelium;
> +
> +			chamelium = chamelium_init_rpc_only();
> +			if (chamelium) {
> +				igt_abort_on_f(!chamelium_wait_reachable(chamelium, 20),
> +					       "cannot reach the configured chamelium!\n");
> +				igt_abort_on_f(!chamelium_plug_all(chamelium),
> +					       "failed to plug all the chamelium ports!\n");
> +				igt_abort_on_f(!chamelium_wait_all_configured_ports_connected(chamelium, drm_fd),
> +					       "not all configured chamelium ports are connected!\n");
> +				chamelium_deinit_rpc_only(chamelium);
> +			}
> +		}
> +	}
>   #endif
>   
> +
>   	/*
>   	 * With non-contiguous pipes display, crtc mapping is not always same
>   	 * as pipe mapping, In i915 pipe is enum id of i915's crtc object.
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t] lib/igt_kms: only check chamelium's presence in chamelium tests

[Kunal Joshi]

On 2021-03-22 at 08:29:02 +0200, Martin Peres wrote:
> On 22/03/2021 07:26, Kunal Joshi wrote:
> > Avoid checking if chamelium is present or not in non chamelium
> > tests as its just an overhead.
> 
> The point of doing this was to stop having screens in CI and instead mostly
> have chameliums. This means that we need to make sure the chamelium exposes
> all the ports before starting a KMS test, since some tests may have left the
> screens disconnected.
> 
> Is that making sense?

Thanks martin for having a look and yeah i got your point,

But for checking all the ports are connected we can have a script which
checks it before the execution starts rather than checking it everytime

Currently when chamelium is not reachable we get SIGQUIT on all the
tests

Starting subtest: basic-fence-flip
Received signal SIGQUIT.
Stack trace:
#0 [fatal_sig_handler+0xd6]
#1 [killpg+0x40]
#2 [pselect+0x59]
#3 [xmlrpc_server_info_disallow_auth_ntlm+0x389]
#4 [xmlrpc_server_info_disallow_auth_ntlm+0x786]
#5 [xmlrpc_server_info_disallow_auth_ntlm+0xd1f]
#6 [xmlrpc_client_call2+0xa8]
#7 [xmlrpc_client_call2f_va+0x9e]
#8 [__chamelium_rpc_va+0x87]
#9 [__chamelium_rpc.constprop.8+0x8c]
#10 [chamelium_wait_reachable+0x65]
#11 [igt_display_require+0xbe]
#12 [test_flip+0x4b]
#13 [__real_main1093+0x1c38]
#14 [main+0x27]
#15 [__libc_start_main+0xe7]
#16 [_start+0x2a]

When chamelium is not reachable chamelium_wait_reachable() never returns
back and we have inactivity timeout which kills the test.

Regards
Kunal Joshi
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t] lib/igt_kms: only check chamelium's presence in chamelium tests

[Martin Peres]

On 22/03/2021 09:29, Kunal Joshi wrote:
> On 2021-03-22 at 08:29:02 +0200, Martin Peres wrote:
>> On 22/03/2021 07:26, Kunal Joshi wrote:
>>> Avoid checking if chamelium is present or not in non chamelium
>>> tests as its just an overhead.
>>
>> The point of doing this was to stop having screens in CI and instead mostly
>> have chameliums. This means that we need to make sure the chamelium exposes
>> all the ports before starting a KMS test, since some tests may have left the
>> screens disconnected.
>>
>> Is that making sense?
> 
> Thanks martin for having a look and yeah i got your point,
> 
> But for checking all the ports are connected we can have a script which
> checks it before the execution starts rather than checking it everytime

Yeah, but then that would not protect against tests that would forget to 
re-plug the screens and thus would lead to unstable IGT results when the 
test list is randomized (shard runs).

I think the idea was that the overhead of checking was measured in ms on 
devices that have a chamelium, and no impact at all on machines without 
a chamelium, so the convenience was deemed greater than the cost.

Do you have specific measurements that would contradict this?

> 
> Currently when chamelium is not reachable we get SIGQUIT on all the
> tests
> 
> Starting subtest: basic-fence-flip
> Received signal SIGQUIT.
> Stack trace:
> #0 [fatal_sig_handler+0xd6]
> #1 [killpg+0x40]
> #2 [pselect+0x59]
> #3 [xmlrpc_server_info_disallow_auth_ntlm+0x389]
> #4 [xmlrpc_server_info_disallow_auth_ntlm+0x786]
> #5 [xmlrpc_server_info_disallow_auth_ntlm+0xd1f]
> #6 [xmlrpc_client_call2+0xa8]
> #7 [xmlrpc_client_call2f_va+0x9e]
> #8 [__chamelium_rpc_va+0x87]
> #9 [__chamelium_rpc.constprop.8+0x8c]
> #10 [chamelium_wait_reachable+0x65]
> #11 [igt_display_require+0xbe]
> #12 [test_flip+0x4b]
> #13 [__real_main1093+0x1c38]
> #14 [main+0x27]
> #15 [__libc_start_main+0xe7]
> #16 [_start+0x2a]
> 
> When chamelium is not reachable chamelium_wait_reachable() never returns
> back and we have inactivity timeout which kills the test.

Isn't that exactly what we want? This seems to be a setup error, and we 
get a clear message: we can't check the state of the chamelium, so 
better not run KMS tests which depend on a state we can't check.

> 
> Regards
> Kunal Joshi
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t] lib/igt_kms: only check chamelium's presence in chamelium tests

[Kunal Joshi]

> Yeah, but then that would not protect against tests that would forget to
> re-plug the screens and thus would lead to unstable IGT results when the
> test list is randomized (shard runs).

Correct, but from the recents runs i have observed that chamelium
crashes in between (chameleond stops), There is no reply coming back
and the test gives SIGQUIT.

I will try to come up with a non blocking plug all display,

> I think the idea was that the overhead of checking was measured in ms on
> devices that have a chamelium, and no impact at all on machines without a
> chamelium, so the convenience was deemed greater than the cost.
> 
> Do you have specific measurements that would contradict this?

For this when chamelium is reachable its neglible in ms
When chamelium is not reachable or crashed it takes 1m15.654s to ~4m causing inactivity timeout

The problem is chamelium crashes in between the runs not when the admin
or someone starts it so time wasted is multiplied by all the tests we
run.

So probably we have to find some other way of dealing with this,
Either decreasing xmlrpc timeout below inactivity timeout or non
blocking xmlrpc request.

Thanks for the feedback

Regards
Kunal Joshi
> 
> > 
> > Currently when chamelium is not reachable we get SIGQUIT on all the
> > tests
> > 
> > Starting subtest: basic-fence-flip
> > Received signal SIGQUIT.
> > Stack trace:
> > #0 [fatal_sig_handler+0xd6]
> > #1 [killpg+0x40]
> > #2 [pselect+0x59]
> > #3 [xmlrpc_server_info_disallow_auth_ntlm+0x389]
> > #4 [xmlrpc_server_info_disallow_auth_ntlm+0x786]
> > #5 [xmlrpc_server_info_disallow_auth_ntlm+0xd1f]
> > #6 [xmlrpc_client_call2+0xa8]
> > #7 [xmlrpc_client_call2f_va+0x9e]
> > #8 [__chamelium_rpc_va+0x87]
> > #9 [__chamelium_rpc.constprop.8+0x8c]
> > #10 [chamelium_wait_reachable+0x65]
> > #11 [igt_display_require+0xbe]
> > #12 [test_flip+0x4b]
> > #13 [__real_main1093+0x1c38]
> > #14 [main+0x27]
> > #15 [__libc_start_main+0xe7]
> > #16 [_start+0x2a]
> > 
> > When chamelium is not reachable chamelium_wait_reachable() never returns
> > back and we have inactivity timeout which kills the test.
> 
> Isn't that exactly what we want? This seems to be a setup error, and we get
> a clear message: we can't check the state of the chamelium, so better not
> run KMS tests which depend on a state we can't check.
> 
> > 
> > Regards
> > Kunal Joshi
> > 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t] lib/igt_kms: only check chamelium's presence in chamelium tests

[Martin Peres]

On 22/03/2021 10:39, Kunal Joshi wrote:
>> Yeah, but then that would not protect against tests that would forget to
>> re-plug the screens and thus would lead to unstable IGT results when the
>> test list is randomized (shard runs).
> 
> Correct, but from the recents runs i have observed that chamelium
> crashes in between (chameleond stops), There is no reply coming back
> and the test gives SIGQUIT.
> 
> I will try to come up with a non blocking plug all display,
> 
>> I think the idea was that the overhead of checking was measured in ms on
>> devices that have a chamelium, and no impact at all on machines without a
>> chamelium, so the convenience was deemed greater than the cost.
>>
>> Do you have specific measurements that would contradict this?
> 
> For this when chamelium is reachable its neglible in ms
> When chamelium is not reachable or crashed it takes 1m15.654s to ~4m causing inactivity timeout
> 
> The problem is chamelium crashes in between the runs not when the admin
> or someone starts it so time wasted is multiplied by all the tests we
> run.
> 
> So probably we have to find some other way of dealing with this,
> Either decreasing xmlrpc timeout below inactivity timeout or non
> blocking xmlrpc request.

I think the answer is pretty clear here: fix the problem at the source, 
don't work around it. You know the code is open source, right?

Martin

> 
> Thanks for the feedback
> 
> Regards
> Kunal Joshi
>>
>>>
>>> Currently when chamelium is not reachable we get SIGQUIT on all the
>>> tests
>>>
>>> Starting subtest: basic-fence-flip
>>> Received signal SIGQUIT.
>>> Stack trace:
>>> #0 [fatal_sig_handler+0xd6]
>>> #1 [killpg+0x40]
>>> #2 [pselect+0x59]
>>> #3 [xmlrpc_server_info_disallow_auth_ntlm+0x389]
>>> #4 [xmlrpc_server_info_disallow_auth_ntlm+0x786]
>>> #5 [xmlrpc_server_info_disallow_auth_ntlm+0xd1f]
>>> #6 [xmlrpc_client_call2+0xa8]
>>> #7 [xmlrpc_client_call2f_va+0x9e]
>>> #8 [__chamelium_rpc_va+0x87]
>>> #9 [__chamelium_rpc.constprop.8+0x8c]
>>> #10 [chamelium_wait_reachable+0x65]
>>> #11 [igt_display_require+0xbe]
>>> #12 [test_flip+0x4b]
>>> #13 [__real_main1093+0x1c38]
>>> #14 [main+0x27]
>>> #15 [__libc_start_main+0xe7]
>>> #16 [_start+0x2a]
>>>
>>> When chamelium is not reachable chamelium_wait_reachable() never returns
>>> back and we have inactivity timeout which kills the test.
>>
>> Isn't that exactly what we want? This seems to be a setup error, and we get
>> a clear message: we can't check the state of the chamelium, so better not
>> run KMS tests which depend on a state we can't check.
>>
>>>
>>> Regards
>>> Kunal Joshi
>>>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t] lib/igt_kms: only check chamelium's presence in chamelium tests

[Petri Latvala]

On Mon, Mar 22, 2021 at 12:59:23PM +0530, Kunal Joshi wrote:
> On 2021-03-22 at 08:29:02 +0200, Martin Peres wrote:
> > On 22/03/2021 07:26, Kunal Joshi wrote:
> > > Avoid checking if chamelium is present or not in non chamelium
> > > tests as its just an overhead.
> > 
> > The point of doing this was to stop having screens in CI and instead mostly
> > have chameliums. This means that we need to make sure the chamelium exposes
> > all the ports before starting a KMS test, since some tests may have left the
> > screens disconnected.
> > 
> > Is that making sense?
> 
> Thanks martin for having a look and yeah i got your point,
> 
> But for checking all the ports are connected we can have a script which
> checks it before the execution starts rather than checking it everytime
> 
> Currently when chamelium is not reachable we get SIGQUIT on all the
> tests
> 
> Starting subtest: basic-fence-flip
> Received signal SIGQUIT.
> Stack trace:
> #0 [fatal_sig_handler+0xd6]
> #1 [killpg+0x40]
> #2 [pselect+0x59]
> #3 [xmlrpc_server_info_disallow_auth_ntlm+0x389]
> #4 [xmlrpc_server_info_disallow_auth_ntlm+0x786]
> #5 [xmlrpc_server_info_disallow_auth_ntlm+0xd1f]
> #6 [xmlrpc_client_call2+0xa8]
> #7 [xmlrpc_client_call2f_va+0x9e]
> #8 [__chamelium_rpc_va+0x87]
> #9 [__chamelium_rpc.constprop.8+0x8c]
> #10 [chamelium_wait_reachable+0x65]
> #11 [igt_display_require+0xbe]
> #12 [test_flip+0x4b]
> #13 [__real_main1093+0x1c38]
> #14 [main+0x27]
> #15 [__libc_start_main+0xe7]
> #16 [_start+0x2a]
> 
> When chamelium is not reachable chamelium_wait_reachable() never returns
> back and we have inactivity timeout which kills the test.


If the configured chamelium is not reachable, we don't want to run any
tests on that platform anyway. What we want to do is make it clear
from the results that an admin should go and kick the device to get it
into shape.

The code you're removing is not just checking that ports are
connected, it's _making_sure_ that they are connected. We had a lot of
noise in the results before putting that there, it's a real need, and
we need it to happen in all tests.

You say this is overhead, do you have some runtime numbers how long
this takes on a working chamelium setup?


-- 
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

[igt-dev] ✓ Fi.CI.BAT: success for lib/igt_kms: only check chamelium's presence in chamelium tests

[Patchwork]

[-- Attachment #1.1: Type: text/plain, Size: 2420 bytes --]

== Series Details ==

Series: lib/igt_kms: only check chamelium's presence in chamelium tests
URL   : https://patchwork.freedesktop.org/series/88229/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_9879 -> IGTPW_5631
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/index.html

Known issues
------------

  Here are the changes found in IGTPW_5631 that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@i915_selftest@live@hangcheck:
    - fi-snb-2600:        [PASS][1] -> [INCOMPLETE][2] ([i915#2782])
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/fi-snb-2600/igt@i915_selftest@live@hangcheck.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/fi-snb-2600/igt@i915_selftest@live@hangcheck.html

  * igt@i915_selftest@live@late_gt_pm:
    - fi-tgl-u2:          [PASS][3] -> [DMESG-WARN][4] ([i915#2867]) +1 similar issue
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/fi-tgl-u2/igt@i915_selftest@live@late_gt_pm.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/fi-tgl-u2/igt@i915_selftest@live@late_gt_pm.html

  
#### Possible fixes ####

  * igt@gem_exec_gttfill@basic:
    - fi-kbl-8809g:       [TIMEOUT][5] ([i915#3145]) -> [PASS][6]
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/fi-kbl-8809g/igt@gem_exec_gttfill@basic.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/fi-kbl-8809g/igt@gem_exec_gttfill@basic.html

  
  [i915#2782]: https://gitlab.freedesktop.org/drm/intel/issues/2782
  [i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
  [i915#3145]: https://gitlab.freedesktop.org/drm/intel/issues/3145


Participating hosts (43 -> 39)
------------------------------

  Missing    (4): fi-ilk-m540 fi-dg1-1 fi-bsw-cyan fi-bdw-samus 


Build changes
-------------

  * CI: CI-20190529 -> None
  * IGT: IGT_6039 -> IGTPW_5631

  CI-20190529: 20190529
  CI_DRM_9879: 892960f907bece8a020b30ade522352ded06c94c @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_5631: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/index.html
  IGT_6039: 8c4a2cda2a92bdd87797969ef299ad7f6e8e993b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/index.html

[-- Attachment #1.2: Type: text/html, Size: 3072 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

[igt-dev] ✗ Fi.CI.IGT: failure for lib/igt_kms: only check chamelium's presence in chamelium tests

[Patchwork]

[-- Attachment #1.1: Type: text/plain, Size: 30281 bytes --]

== Series Details ==

Series: lib/igt_kms: only check chamelium's presence in chamelium tests
URL   : https://patchwork.freedesktop.org/series/88229/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_9879_full -> IGTPW_5631_full
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with IGTPW_5631_full absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in IGTPW_5631_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_5631/index.html

Possible new issues
-------------------

  Here are the unknown changes that may have been introduced in IGTPW_5631_full:

### IGT changes ###

#### Possible regressions ####

  * igt@gem_ctx_persistence@engines-mixed-process@rcs0:
    - shard-tglb:         NOTRUN -> [FAIL][1]
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb3/igt@gem_ctx_persistence@engines-mixed-process@rcs0.html

  
Known issues
------------

  Here are the changes found in IGTPW_5631_full that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@feature_discovery@chamelium:
    - shard-tglb:         NOTRUN -> [SKIP][2] ([fdo#111827])
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb7/igt@feature_discovery@chamelium.html
    - shard-iclb:         NOTRUN -> [SKIP][3] ([fdo#111827])
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb5/igt@feature_discovery@chamelium.html

  * igt@gem_create@create-clear:
    - shard-glk:          [PASS][4] -> [FAIL][5] ([i915#3160])
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-glk6/igt@gem_create@create-clear.html
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-glk8/igt@gem_create@create-clear.html

  * igt@gem_create@create-massive:
    - shard-kbl:          NOTRUN -> [DMESG-WARN][6] ([i915#3002])
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl2/igt@gem_create@create-massive.html
    - shard-apl:          NOTRUN -> [DMESG-WARN][7] ([i915#3002])
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl3/igt@gem_create@create-massive.html

  * igt@gem_ctx_persistence@smoketest:
    - shard-snb:          NOTRUN -> [SKIP][8] ([fdo#109271] / [i915#1099]) +4 similar issues
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-snb5/igt@gem_ctx_persistence@smoketest.html

  * igt@gem_eio@unwedge-stress:
    - shard-tglb:         [PASS][9] -> [TIMEOUT][10] ([i915#2369] / [i915#3063])
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-tglb3/igt@gem_eio@unwedge-stress.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb7/igt@gem_eio@unwedge-stress.html

  * igt@gem_exec_fair@basic-deadline:
    - shard-kbl:          NOTRUN -> [FAIL][11] ([i915#2846])
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl1/igt@gem_exec_fair@basic-deadline.html
    - shard-apl:          NOTRUN -> [FAIL][12] ([i915#2846])
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl1/igt@gem_exec_fair@basic-deadline.html

  * igt@gem_exec_fair@basic-flow@rcs0:
    - shard-tglb:         [PASS][13] -> [FAIL][14] ([i915#2842]) +2 similar issues
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-tglb1/igt@gem_exec_fair@basic-flow@rcs0.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb3/igt@gem_exec_fair@basic-flow@rcs0.html

  * igt@gem_exec_fair@basic-none-rrul@rcs0:
    - shard-kbl:          [PASS][15] -> [FAIL][16] ([i915#2842])
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-kbl2/igt@gem_exec_fair@basic-none-rrul@rcs0.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl4/igt@gem_exec_fair@basic-none-rrul@rcs0.html

  * igt@gem_exec_fair@basic-none-solo@rcs0:
    - shard-kbl:          NOTRUN -> [FAIL][17] ([i915#2842])
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl1/igt@gem_exec_fair@basic-none-solo@rcs0.html

  * igt@gem_exec_params@no-vebox:
    - shard-iclb:         NOTRUN -> [SKIP][18] ([fdo#109283])
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb8/igt@gem_exec_params@no-vebox.html
    - shard-tglb:         NOTRUN -> [SKIP][19] ([fdo#109283])
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb7/igt@gem_exec_params@no-vebox.html

  * igt@gem_exec_params@secure-non-root:
    - shard-tglb:         NOTRUN -> [SKIP][20] ([fdo#112283])
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb7/igt@gem_exec_params@secure-non-root.html
    - shard-iclb:         NOTRUN -> [SKIP][21] ([fdo#112283])
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb8/igt@gem_exec_params@secure-non-root.html

  * igt@gem_exec_reloc@basic-many-active@rcs0:
    - shard-tglb:         NOTRUN -> [FAIL][22] ([i915#2389]) +4 similar issues
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb1/igt@gem_exec_reloc@basic-many-active@rcs0.html
    - shard-glk:          NOTRUN -> [FAIL][23] ([i915#2389])
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-glk5/igt@gem_exec_reloc@basic-many-active@rcs0.html
    - shard-iclb:         NOTRUN -> [FAIL][24] ([i915#2389]) +4 similar issues
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb2/igt@gem_exec_reloc@basic-many-active@rcs0.html

  * igt@gem_exec_reloc@basic-many-active@vcs0:
    - shard-kbl:          NOTRUN -> [FAIL][25] ([i915#2389]) +4 similar issues
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl6/igt@gem_exec_reloc@basic-many-active@vcs0.html

  * igt@gem_exec_reloc@basic-parallel:
    - shard-apl:          NOTRUN -> [TIMEOUT][26] ([i915#3183])
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl1/igt@gem_exec_reloc@basic-parallel.html

  * igt@gem_mmap_gtt@cpuset-basic-small-copy-xy:
    - shard-iclb:         [PASS][27] -> [FAIL][28] ([i915#307])
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-iclb2/igt@gem_mmap_gtt@cpuset-basic-small-copy-xy.html
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb3/igt@gem_mmap_gtt@cpuset-basic-small-copy-xy.html

  * igt@gem_pread@exhaustion:
    - shard-apl:          NOTRUN -> [WARN][29] ([i915#2658]) +1 similar issue
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl3/igt@gem_pread@exhaustion.html

  * igt@gem_pwrite@basic-exhaustion:
    - shard-kbl:          NOTRUN -> [WARN][30] ([i915#2658])
   [30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl2/igt@gem_pwrite@basic-exhaustion.html

  * igt@gem_userptr_blits@mmap-offset-invalidate-active@gtt:
    - shard-iclb:         NOTRUN -> [SKIP][31] ([i915#1317]) +3 similar issues
   [31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb1/igt@gem_userptr_blits@mmap-offset-invalidate-active@gtt.html

  * igt@gem_userptr_blits@mmap-offset-invalidate-active@wc:
    - shard-tglb:         NOTRUN -> [SKIP][32] ([i915#1317]) +3 similar issues
   [32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb5/igt@gem_userptr_blits@mmap-offset-invalidate-active@wc.html

  * igt@gem_userptr_blits@process-exit-mmap-busy@wc:
    - shard-apl:          NOTRUN -> [SKIP][33] ([fdo#109271] / [i915#1699]) +3 similar issues
   [33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl1/igt@gem_userptr_blits@process-exit-mmap-busy@wc.html

  * igt@gem_userptr_blits@process-exit-mmap@gtt:
    - shard-kbl:          NOTRUN -> [SKIP][34] ([fdo#109271] / [i915#1699]) +3 similar issues
   [34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl2/igt@gem_userptr_blits@process-exit-mmap@gtt.html

  * igt@gen9_exec_parse@batch-invalid-length:
    - shard-snb:          NOTRUN -> [SKIP][35] ([fdo#109271]) +330 similar issues
   [35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-snb5/igt@gen9_exec_parse@batch-invalid-length.html

  * igt@gen9_exec_parse@batch-zero-length:
    - shard-iclb:         NOTRUN -> [SKIP][36] ([fdo#112306])
   [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb4/igt@gen9_exec_parse@batch-zero-length.html
    - shard-tglb:         NOTRUN -> [SKIP][37] ([fdo#112306])
   [37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb5/igt@gen9_exec_parse@batch-zero-length.html

  * igt@i915_hangman@engine-error@vecs0:
    - shard-kbl:          NOTRUN -> [SKIP][38] ([fdo#109271]) +146 similar issues
   [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl3/igt@i915_hangman@engine-error@vecs0.html

  * igt@i915_pm_dc@dc6-psr:
    - shard-tglb:         NOTRUN -> [FAIL][39] ([i915#454])
   [39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb3/igt@i915_pm_dc@dc6-psr.html

  * igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
    - shard-kbl:          NOTRUN -> [SKIP][40] ([fdo#109271] / [i915#1937])
   [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl6/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp.html
    - shard-apl:          NOTRUN -> [SKIP][41] ([fdo#109271] / [i915#1937])
   [41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl8/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp.html

  * igt@i915_selftest@live@gt_lrc:
    - shard-tglb:         NOTRUN -> [DMESG-FAIL][42] ([i915#2373])
   [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb7/igt@i915_selftest@live@gt_lrc.html

  * igt@i915_selftest@live@gt_pm:
    - shard-tglb:         NOTRUN -> [DMESG-FAIL][43] ([i915#1759] / [i915#2291])
   [43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb7/igt@i915_selftest@live@gt_pm.html

  * igt@i915_suspend@forcewake:
    - shard-kbl:          [PASS][44] -> [DMESG-WARN][45] ([i915#180]) +5 similar issues
   [44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-kbl2/igt@i915_suspend@forcewake.html
   [45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl4/igt@i915_suspend@forcewake.html

  * igt@kms_big_fb@linear-16bpp-rotate-270:
    - shard-tglb:         NOTRUN -> [SKIP][46] ([fdo#111614])
   [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb1/igt@kms_big_fb@linear-16bpp-rotate-270.html
    - shard-iclb:         NOTRUN -> [SKIP][47] ([fdo#110725] / [fdo#111614])
   [47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb5/igt@kms_big_fb@linear-16bpp-rotate-270.html

  * igt@kms_big_fb@yf-tiled-8bpp-rotate-180:
    - shard-tglb:         NOTRUN -> [SKIP][48] ([fdo#111615]) +2 similar issues
   [48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb7/igt@kms_big_fb@yf-tiled-8bpp-rotate-180.html
    - shard-iclb:         NOTRUN -> [SKIP][49] ([fdo#110723]) +1 similar issue
   [49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb3/igt@kms_big_fb@yf-tiled-8bpp-rotate-180.html

  * igt@kms_big_joiner@basic:
    - shard-apl:          NOTRUN -> [SKIP][50] ([fdo#109271] / [i915#2705]) +1 similar issue
   [50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl7/igt@kms_big_joiner@basic.html

  * igt@kms_chamelium@dp-hpd-storm-disable:
    - shard-glk:          NOTRUN -> [SKIP][51] ([fdo#109271] / [fdo#111827]) +1 similar issue
   [51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-glk5/igt@kms_chamelium@dp-hpd-storm-disable.html

  * igt@kms_chamelium@hdmi-edid-change-during-suspend:
    - shard-apl:          NOTRUN -> [SKIP][52] ([fdo#109271] / [fdo#111827]) +27 similar issues
   [52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl7/igt@kms_chamelium@hdmi-edid-change-during-suspend.html

  * igt@kms_chamelium@hdmi-mode-timings:
    - shard-snb:          NOTRUN -> [SKIP][53] ([fdo#109271] / [fdo#111827]) +16 similar issues
   [53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-snb6/igt@kms_chamelium@hdmi-mode-timings.html

  * igt@kms_chamelium@vga-hpd-fast:
    - shard-tglb:         NOTRUN -> [SKIP][54] ([fdo#109284] / [fdo#111827]) +5 similar issues
   [54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb1/igt@kms_chamelium@vga-hpd-fast.html

  * igt@kms_color@pipe-b-degamma:
    - shard-iclb:         NOTRUN -> [FAIL][55] ([i915#1149])
   [55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb6/igt@kms_color@pipe-b-degamma.html

  * igt@kms_color@pipe-d-ctm-0-25:
    - shard-iclb:         NOTRUN -> [SKIP][56] ([fdo#109278] / [i915#1149])
   [56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb8/igt@kms_color@pipe-d-ctm-0-25.html

  * igt@kms_color_chamelium@pipe-a-ctm-blue-to-red:
    - shard-kbl:          NOTRUN -> [SKIP][57] ([fdo#109271] / [fdo#111827]) +9 similar issues
   [57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl3/igt@kms_color_chamelium@pipe-a-ctm-blue-to-red.html
    - shard-iclb:         NOTRUN -> [SKIP][58] ([fdo#109284] / [fdo#111827]) +5 similar issues
   [58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb6/igt@kms_color_chamelium@pipe-a-ctm-blue-to-red.html

  * igt@kms_content_protection@lic:
    - shard-apl:          NOTRUN -> [TIMEOUT][59] ([i915#1319]) +1 similar issue
   [59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl8/igt@kms_content_protection@lic.html

  * igt@kms_cursor_crc@pipe-b-cursor-512x512-random:
    - shard-iclb:         NOTRUN -> [SKIP][60] ([fdo#109278] / [fdo#109279]) +2 similar issues
   [60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb7/igt@kms_cursor_crc@pipe-b-cursor-512x512-random.html

  * igt@kms_cursor_crc@pipe-d-cursor-256x256-random:
    - shard-glk:          NOTRUN -> [SKIP][61] ([fdo#109271]) +30 similar issues
   [61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-glk4/igt@kms_cursor_crc@pipe-d-cursor-256x256-random.html

  * igt@kms_cursor_crc@pipe-d-cursor-512x512-rapid-movement:
    - shard-tglb:         NOTRUN -> [SKIP][62] ([fdo#109279]) +4 similar issues
   [62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb5/igt@kms_cursor_crc@pipe-d-cursor-512x512-rapid-movement.html

  * igt@kms_cursor_edge_walk@pipe-a-64x64-bottom-edge:
    - shard-snb:          [PASS][63] -> [SKIP][64] ([fdo#109271]) +1 similar issue
   [63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-snb7/igt@kms_cursor_edge_walk@pipe-a-64x64-bottom-edge.html
   [64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-snb6/igt@kms_cursor_edge_walk@pipe-a-64x64-bottom-edge.html

  * igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy:
    - shard-iclb:         NOTRUN -> [SKIP][65] ([fdo#109274] / [fdo#109278]) +1 similar issue
   [65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb1/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy.html

  * igt@kms_cursor_legacy@pipe-d-torture-bo:
    - shard-apl:          NOTRUN -> [SKIP][66] ([fdo#109271] / [i915#533]) +1 similar issue
   [66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl2/igt@kms_cursor_legacy@pipe-d-torture-bo.html

  * igt@kms_flip@2x-flip-vs-rmfb:
    - shard-iclb:         NOTRUN -> [SKIP][67] ([fdo#109274]) +2 similar issues
   [67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb4/igt@kms_flip@2x-flip-vs-rmfb.html

  * igt@kms_flip@flip-vs-suspend-interruptible@b-dp1:
    - shard-apl:          [PASS][68] -> [DMESG-WARN][69] ([i915#180])
   [68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-apl1/igt@kms_flip@flip-vs-suspend-interruptible@b-dp1.html
   [69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl6/igt@kms_flip@flip-vs-suspend-interruptible@b-dp1.html

  * igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs:
    - shard-kbl:          NOTRUN -> [FAIL][70] ([i915#2641]) +1 similar issue
   [70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl3/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs.html

  * igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs:
    - shard-kbl:          NOTRUN -> [SKIP][71] ([fdo#109271] / [i915#2672]) +1 similar issue
   [71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl1/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs.html
    - shard-apl:          NOTRUN -> [SKIP][72] ([fdo#109271] / [i915#2672])
   [72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl3/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs.html
    - shard-glk:          NOTRUN -> [SKIP][73] ([fdo#109271] / [i915#2672])
   [73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-glk8/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs.html
    - shard-iclb:         NOTRUN -> [SKIP][74] ([i915#2587])
   [74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb5/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs.html

  * igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile:
    - shard-apl:          NOTRUN -> [FAIL][75] ([i915#2641]) +1 similar issue
   [75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl8/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile.html

  * igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-indfb-plflip-blt:
    - shard-tglb:         NOTRUN -> [SKIP][76] ([fdo#111825]) +24 similar issues
   [76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb1/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-indfb-plflip-blt.html

  * igt@kms_frontbuffer_tracking@psr-2p-primscrn-shrfb-pgflip-blt:
    - shard-iclb:         NOTRUN -> [SKIP][77] ([fdo#109280]) +18 similar issues
   [77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb8/igt@kms_frontbuffer_tracking@psr-2p-primscrn-shrfb-pgflip-blt.html

  * igt@kms_invalid_dotclock:
    - shard-tglb:         NOTRUN -> [SKIP][78] ([fdo#110577])
   [78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb3/igt@kms_invalid_dotclock.html

  * igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
    - shard-apl:          NOTRUN -> [FAIL][79] ([fdo#108145] / [i915#265]) +5 similar issues
   [79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl7/igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb.html
    - shard-glk:          NOTRUN -> [FAIL][80] ([fdo#108145] / [i915#265])
   [80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-glk4/igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb.html
    - shard-kbl:          NOTRUN -> [FAIL][81] ([fdo#108145] / [i915#265])
   [81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl3/igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb.html

  * igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb:
    - shard-apl:          NOTRUN -> [FAIL][82] ([i915#265]) +1 similar issue
   [82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl8/igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb.html

  * igt@kms_plane_alpha_blend@pipe-d-constant-alpha-min:
    - shard-iclb:         NOTRUN -> [SKIP][83] ([fdo#109278]) +8 similar issues
   [83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb8/igt@kms_plane_alpha_blend@pipe-d-constant-alpha-min.html

  * igt@kms_plane_lowres@pipe-d-tiling-yf:
    - shard-tglb:         NOTRUN -> [SKIP][84] ([fdo#112054])
   [84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb1/igt@kms_plane_lowres@pipe-d-tiling-yf.html

  * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3:
    - shard-kbl:          NOTRUN -> [SKIP][85] ([fdo#109271] / [i915#658]) +5 similar issues
   [85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl7/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3.html

  * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4:
    - shard-apl:          NOTRUN -> [SKIP][86] ([fdo#109271] / [i915#658]) +6 similar issues
   [86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl1/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4.html

  * igt@kms_psr2_sf@plane-move-sf-dmg-area-1:
    - shard-iclb:         NOTRUN -> [SKIP][87] ([i915#2920])
   [87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb2/igt@kms_psr2_sf@plane-move-sf-dmg-area-1.html

  * igt@kms_psr@psr2_cursor_mmap_cpu:
    - shard-iclb:         NOTRUN -> [SKIP][88] ([fdo#109441])
   [88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb6/igt@kms_psr@psr2_cursor_mmap_cpu.html

  * igt@kms_psr@psr2_primary_page_flip:
    - shard-iclb:         [PASS][89] -> [SKIP][90] ([fdo#109441]) +2 similar issues
   [89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
   [90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb8/igt@kms_psr@psr2_primary_page_flip.html

  * igt@kms_writeback@writeback-check-output:
    - shard-apl:          NOTRUN -> [SKIP][91] ([fdo#109271] / [i915#2437]) +1 similar issue
   [91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl2/igt@kms_writeback@writeback-check-output.html

  * igt@kms_writeback@writeback-pixel-formats:
    - shard-kbl:          NOTRUN -> [SKIP][92] ([fdo#109271] / [i915#2437]) +1 similar issue
   [92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl2/igt@kms_writeback@writeback-pixel-formats.html

  * igt@nouveau_crc@pipe-c-ctx-flip-detection:
    - shard-tglb:         NOTRUN -> [SKIP][93] ([i915#2530]) +1 similar issue
   [93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb2/igt@nouveau_crc@pipe-c-ctx-flip-detection.html

  * igt@nouveau_crc@pipe-c-source-rg:
    - shard-iclb:         NOTRUN -> [SKIP][94] ([i915#2530])
   [94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb5/igt@nouveau_crc@pipe-c-source-rg.html

  * igt@prime_nv_api@i915_nv_import_twice:
    - shard-iclb:         NOTRUN -> [SKIP][95] ([fdo#109291]) +2 similar issues
   [95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb7/igt@prime_nv_api@i915_nv_import_twice.html

  * igt@prime_nv_api@i915_nv_reimport_twice_check_flink_name:
    - shard-apl:          NOTRUN -> [SKIP][96] ([fdo#109271]) +241 similar issues
   [96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl1/igt@prime_nv_api@i915_nv_reimport_twice_check_flink_name.html

  * igt@prime_nv_test@i915_import_pread_pwrite:
    - shard-tglb:         NOTRUN -> [SKIP][97] ([fdo#109291]) +1 similar issue
   [97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb7/igt@prime_nv_test@i915_import_pread_pwrite.html

  * igt@sysfs_clients@busy@vecs0:
    - shard-kbl:          [PASS][98] -> [FAIL][99] ([i915#3009])
   [98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-kbl7/igt@sysfs_clients@busy@vecs0.html
   [99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl6/igt@sysfs_clients@busy@vecs0.html

  * igt@sysfs_clients@recycle:
    - shard-kbl:          [PASS][100] -> [FAIL][101] ([i915#3028])
   [100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-kbl3/igt@sysfs_clients@recycle.html
   [101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl4/igt@sysfs_clients@recycle.html

  * igt@sysfs_clients@split-10@bcs0:
    - shard-glk:          NOTRUN -> [SKIP][102] ([fdo#109271] / [i915#3026])
   [102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-glk9/igt@sysfs_clients@split-10@bcs0.html
    - shard-apl:          NOTRUN -> [SKIP][103] ([fdo#109271] / [i915#3026])
   [103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl3/igt@sysfs_clients@split-10@bcs0.html
    - shard-kbl:          NOTRUN -> [SKIP][104] ([fdo#109271] / [i915#3026])
   [104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl2/igt@sysfs_clients@split-10@bcs0.html

  
#### Possible fixes ####

  * igt@feature_discovery@psr2:
    - shard-iclb:         [SKIP][105] ([i915#658]) -> [PASS][106]
   [105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-iclb7/igt@feature_discovery@psr2.html
   [106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb2/igt@feature_discovery@psr2.html

  * igt@gem_exec_balancer@hang:
    - shard-iclb:         [INCOMPLETE][107] ([i915#1895] / [i915#3031]) -> [PASS][108]
   [107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-iclb4/igt@gem_exec_balancer@hang.html
   [108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb6/igt@gem_exec_balancer@hang.html

  * igt@gem_exec_fair@basic-none-solo@rcs0:
    - shard-glk:          [FAIL][109] ([i915#2842]) -> [PASS][110] +1 similar issue
   [109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-glk9/igt@gem_exec_fair@basic-none-solo@rcs0.html
   [110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-glk5/igt@gem_exec_fair@basic-none-solo@rcs0.html

  * igt@gem_exec_fair@basic-pace-share@rcs0:
    - shard-tglb:         [FAIL][111] ([i915#2842]) -> [PASS][112] +1 similar issue
   [111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-tglb7/igt@gem_exec_fair@basic-pace-share@rcs0.html
   [112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb3/igt@gem_exec_fair@basic-pace-share@rcs0.html

  * igt@gem_exec_schedule@u-fairslice@rcs0:
    - shard-kbl:          [DMESG-WARN][113] ([i915#1610] / [i915#2803]) -> [PASS][114]
   [113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-kbl7/igt@gem_exec_schedule@u-fairslice@rcs0.html
   [114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl2/igt@gem_exec_schedule@u-fairslice@rcs0.html

  * igt@gem_exec_schedule@u-fairslice@vecs0:
    - shard-apl:          [DMESG-WARN][115] ([i915#1610]) -> [PASS][116]
   [115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-apl7/igt@gem_exec_schedule@u-fairslice@vecs0.html
   [116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl3/igt@gem_exec_schedule@u-fairslice@vecs0.html

  * igt@kms_cursor_crc@pipe-a-cursor-64x21-random:
    - shard-glk:          [FAIL][117] ([i915#54]) -> [PASS][118]
   [117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-glk9/igt@kms_cursor_crc@pipe-a-cursor-64x21-random.html
   [118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-glk7/igt@kms_cursor_crc@pipe-a-cursor-64x21-random.html

  * igt@kms_flip@flip-vs-suspend-interruptible@a-edp1:
    - shard-tglb:         [DMESG-WARN][119] ([i915#1436] / [i915#1602] / [i915#1887] / [i915#2411]) -> [PASS][120]
   [119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-tglb8/igt@kms_flip@flip-vs-suspend-interruptible@a-edp1.html
   [120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb5/igt@kms_flip@flip-vs-suspend-interruptible@a-edp1.html

  * igt@kms_flip@flip-vs-suspend@a-dp1:
    - shard-apl:          [DMESG-WARN][121] ([i915#180]) -> [PASS][122] +1 similar issue
   [121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-apl3/igt@kms_flip@flip-vs-suspend@a-dp1.html
   [122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl8/igt@kms_flip@flip-vs-suspend@a-dp1.html

  * igt@kms_flip@flip-vs-suspend@c-dp1:
    - shard-kbl:          [DMESG-WARN][123] ([i915#180]) -> [PASS][124] +5 similar issues
   [123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-kbl2/igt@kms_flip@flip-vs-suspend@c-dp1.html
   [124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl6/igt@kms_flip@flip-vs-suspend@c-dp1.html

  * igt@kms_frontbuffer_tracking@fbcpsr-indfb-scaledprimary:
    - shard-tglb:         [SKIP][125] ([i915#668]) -> [PASS][126] +3 similar issues
   [125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-tglb1/igt@kms_frontbuffer_tracking@fbcpsr-indfb-scaledprimary.html
   [126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-tglb5/igt@kms_frontbuffer_tracking@fbcpsr-indfb-scaledprimary.html

  * igt@kms_psr@psr2_sprite_plane_onoff:
    - shard-iclb:         [SKIP][127] ([fdo#109441]) -> [PASS][128]
   [127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-iclb3/igt@kms_psr@psr2_sprite_plane_onoff.html
   [128]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb2/igt@kms_psr@psr2_sprite_plane_onoff.html

  * igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend:
    - shard-kbl:          [INCOMPLETE][129] ([i915#155]) -> [PASS][130]
   [129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-kbl3/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html
   [130]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-kbl7/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html

  * igt@sysfs_clients@recycle-many:
    - shard-apl:          [FAIL][131] ([i915#3028]) -> [PASS][132]
   [131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-apl2/igt@sysfs_clients@recycle-many.html
   [132]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-apl7/igt@sysfs_clients@recycle-many.html
    - shard-iclb:         [FAIL][133] ([i915#3028]) -> [PASS][134]
   [133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-iclb1/igt@sysfs_clients@recycle-many.html
   [134]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb6/igt@sysfs_clients@recycle-many.html

  
#### Warnings ####

  * igt@i915_pm_rc6_residency@rc6-fence:
    - shard-iclb:         [WARN][135] ([i915#1804] / [i915#2684]) -> [WARN][136] ([i915#2684]) +1 similar issue
   [135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-iclb4/igt@i915_pm_rc6_residency@rc6-fence.html
   [136]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb2/igt@i915_pm_rc6_residency@rc6-fence.html

  * igt@kms_content_protection@content_type_change:
    - shard-iclb:         [FAIL][137] ([i915#3144]) -> [SKIP][138] ([fdo#109300] / [fdo#111066])
   [137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9879/shard-iclb1/igt@kms_content_protection@content_type_change.html
   [138]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/shard-iclb7/igt@kms_content_protection@content_type_change.html

  * igt@kms_content_protection@type1:
    - shard-iclb:         [SKIP][139] ([fdo#109300] / [fdo#111066]) -> [FAIL][140] ([i915#3144])
   [139]: https:

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5631/index.html

[-- Attachment #1.2: Type: text/html, Size: 33814 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev