On 19/03/2021 01:17, Patchwork wrote:
Okay with 20s default expiration the hangcheck tests on Tigerlake pass
and we are left with these failures:
IGT changes
Possible regressions
*
igt@gem_ctx_ringsize@idle@bcs0:
o shard-skl: PASS
<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9870/shard-skl10/igt@gem_ctx_ringsize@idle@xxxxxxxxx>
-> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19806/shard-skl7/igt@gem_ctx_ringsize@idle@xxxxxxxxx>
Too many runnable requests on a slow Skylake SKU with command parsing
active. Too many to finish withing the 20s default expiration that is.
This is actually the same root cause as the below tests tries to
explicitly demonstrate:
*
{igt@gem_watchdog@far-fence@bcs0} (NEW):
o shard-glk: NOTRUN -> FAIL
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19806/shard-glk7/igt@gem_watchdog@far-fence@xxxxxxxxx>
*
{igt@gem_watchdog@far-fence@vcs0} (NEW):
o shard-apl: NOTRUN -> FAIL
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19806/shard-apl1/igt@gem_watchdog@far-fence@xxxxxxxxx>
+2 similar issues
*
{igt@gem_watchdog@far-fence@vecs0} (NEW):
o shard-kbl: NOTRUN -> FAIL
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19806/shard-kbl7/igt@gem_watchdog@far-fence@xxxxxxxxxx>
+2 similar issues
The vulnerability default expiration adds compared to the current state
is applicable to heaviliy loaded systems where GPU is shared between
multiple clients.
Otherwise series seems to work. Failing tests can be blacklisted going
forward. Ack to merge and merge itself, after review, I leave to
maintainers since personally I am not supportive of this mechanism.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
