drm/i915: fix broken build
Subsystems (2)
PATCH 1/2 drm/i915: fix broken build
I guess this was missed in the conversion or something.
--- drivers/gpu/drm/i915/i915_deps.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_deps.c +1 -1
@@ -226,7 +226,7 @@ int i915_deps_add_resv(struct i915_deps *deps, struct dma_resv *resv,struct dma_fence *fence;dma_resv_assert_held (resv); -dma_resv_for_each_fence (&iter, resv, true, fence) { +dma_resv_for_each_fence (&iter, resv,dma_resv_usage_rw (true), fence) {int ret =i915_deps_add_dependency (deps, fence, ctx);if (ret)
Signature · 1 line
2.34.1
PATCH 2/2 drm/i915: fix i915_gem_object_wait_moving_fence
All of CI is just failing with the following, which prevents loading of the module:
i915 0000:03:00.0: [drm] *ERROR* Scratch setup failed
Best guess is that this comes from the pin_map() for the scratch page, which does an i915_gem_object_wait_moving_fence() somewhere. It looks like this now calls into dma_resv_wait_timeout() which can return the remaining timeout, leading to the caller thinking this is an error.
--- drivers/gpu/drm/i915/gem/i915_gem_object.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_object.c +7 -2
@@ -772,9 +772,14 @@ int i915_gem_object_get_moving_fence(struct drm_i915_gem_object *obj,int i915_gem_object_wait_moving_fence (struct drm_i915_gem_object *obj,bool intr) { +long ret; +assert_object_held (obj); -return dma_resv_wait_timeout (obj->base. resv,DMA_RESV_USAGE_KERNEL , - intr,MAX_SCHEDULE_TIMEOUT ); + + ret =dma_resv_wait_timeout (obj->base. resv,DMA_RESV_USAGE_KERNEL , + intr,MAX_SCHEDULE_TIMEOUT ); + +return ret <0 ? ret :0 ; }#if IS_ENABLED (CONFIG_DRM_I915_SELFTEST )
Signature · 1 line
2.34.1
Re: [Intel-gfx] [PATCH 2/2] drm/i915: fix i915_gem_object_wait_moving_fence
Quoted 10 lines · Matthew Auld
All of CI is just failing with the following, which prevents loading of the module:
i915 0000:03:00.0: [drm] *ERROR* Scratch setup failedBest guess is that this comes from the
pin_map()for the scratch page, which does ani915_gem_object_wait_moving_fence()somewhere. It looks like this now calls intodma_resv_wait_timeout()which can return the remaining timeout, leading to the caller thinking this is an error.
Quoted 4 lines
Fixes 1d7f5e6c5240 ("drm/i915: drop bo->moving dependency")Signed-off-by Matthew Auld <[email protected]>Cc Christian König <[email protected]>Cc Daniel Vetter <[email protected]>
This indeed brings CI back to life.
thanks
Lucas De Marchi
Re: [Intel-gfx] [PATCH 2/2] drm/i915: fix i915_gem_object_wait_moving_fence
In reply to Matthew AuldQuoted 26 lines · Matthew Auld
All of CI is just failing with the following, which prevents loading of the module:
i915 0000:03:00.0: [drm] *ERROR* Scratch setup failedBest guess is that this comes from the
pin_map()for the scratch page, which does ani915_gem_object_wait_moving_fence()somewhere. It looks like this now calls intodma_resv_wait_timeout()which can return the remaining timeout, leading to the caller thinking this is an error.Fixes 1d7f5e6c5240 ("drm/i915: drop bo->moving dependency")Signed-off-by Matthew Auld <[email protected]>Cc Christian König <[email protected]>Cc Daniel Vetter <[email protected]>---
drivers/gpu/drm/i915/gem/i915_gem_object.c| 9 +++++++--1 file changed, 7 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/gem/i915_gem_object.c +0
-0@@ -772,9 +772,14 @@ int i915_gem_object_get_moving_fence(struct drm_i915_gem_object *obj,int i915_gem_object_wait_moving_fence (struct drm_i915_gem_object *obj,bool intr) {
drivers/gpu/drm/i915/gem/i915_gem_object.c int i915_gem_object_get_moving_fence(struct drm_i915_gem_object *obj, · line 782
Quoted 10 lines
drivers/gpu/drm/i915/gem/i915_gem_object.c +7
-2+long ret; +assert_object_held (obj); -return dma_resv_wait_timeout (obj->base. resv,DMA_RESV_USAGE_KERNEL , - intr,MAX_SCHEDULE_TIMEOUT ); + + ret =dma_resv_wait_timeout (obj->base. resv,DMA_RESV_USAGE_KERNEL , + intr,MAX_SCHEDULE_TIMEOUT ); + +return ret <0 ? ret :0 ;
shouldn't == 0 also be an error since it would be a timeout?
Lucas De Marchi
Re: [Intel-gfx] [PATCH 2/2] drm/i915: fix i915_gem_object_wait_moving_fence
Quoted 32 lines · Lucas De Marchi
Quoted 31 lines · Matthew Auld
All of CI is just failing with the following, which prevents loading of the module:
i915 0000:03:00.0: [drm] *ERROR* Scratch setup failed
Best guess is that this comes from the
pin_map()for the scratch page, which does ani915_gem_object_wait_moving_fence()somewhere. It looks like this now calls intodma_resv_wait_timeout()which can return the remaining timeout, leading to the caller thinking this is an error.Fixes 1d7f5e6c5240 ("drm/i915: drop bo->moving dependency")Signed-off-by Matthew Auld <[email protected]>Cc Christian König <[email protected]>Cc Daniel Vetter <[email protected]>---
drivers/gpu/drm/i915/gem/i915_gem_object.c| 9 +++++++--1 file changed, 7 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/gem/i915_gem_object.c +2
-1@@ -772,9 +772,14 @@ int i915_gem_object_get_moving_fence(structdrm_i915_gem_object *obj, int i915_gem_object_wait_moving_fence(struct drm_i915_gem_object *obj, bool intr) { + long ret; + assert_object_held(obj); - return dma_resv_wait_timeout(obj->base. resv, DMA_RESV_USAGE_KERNEL,
Quoted 8 lines
drivers/gpu/drm/i915/gem/i915_gem_object.c int i915_gem_object_get_moving_fence(struct drm_i915_gem_object *obj, · line 782
Quoted 6 lines
drivers/gpu/drm/i915/gem/i915_gem_object.c +5
-1- intr, MAX_SCHEDULE_TIMEOUT); + + ret = dma_resv_wait_timeout(obj->base. resv, DMA_RESV_USAGE_KERNEL, + intr, MAX_SCHEDULE_TIMEOUT); + + return ret < 0 ? ret : 0;shouldn't == 0 also be an error since it would be a timeout?
Hmm, I guess so...
Quoted 2 lines
Lucas De Marchi
Re: [Intel-gfx] [PATCH 2/2] drm/i915: fix i915_gem_object_wait_moving_fence
In reply to Matthew AuldQuoted 11 lines · Matthew Auld
All of CI is just failing with the following, which prevents loading of the module:
i915 0000:03:00.0: [drm] *ERROR* Scratch setup failedBest guess is that this comes from the
pin_map()for the scratch page, which does ani915_gem_object_wait_moving_fence()somewhere. It looks like this now calls intodma_resv_wait_timeout()which can return the remaining timeout, leading to the caller thinking this is an error.Fixes 1d7f5e6c5240 ("drm/i915: drop bo->moving dependency")
Has this one went in bypassing i915 CI and merged via drm-misc-next? If so I think it's the 2nd large disruption to i915 CI flows recently so the lesson here is try not to bypass i915 CI when merging i915 patches.
In this particular example, unless there were merge conflicts causing the series not to apply against drm-tip, it should have been doable to copy intel-gfx on all patches and so get the CI results. (Even if just with --subject-prefix=CI && --suppress-cc=all before merging.)
The second question is which branch to merge through, on which I think i915 maintainers would have liked to be consulted.
Regards,
Tvrtko
Quoted 28 lines
Signed-off-by Matthew Auld <[email protected]>Cc Christian König <[email protected]>Cc Daniel Vetter <[email protected]>--- drivers/gpu/drm/i915/gem/i915_gem_object.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/gem/i915_gem_object.c +7
-2@@ -772,9 +772,14 @@ int i915_gem_object_get_moving_fence(struct drm_i915_gem_object *obj,int i915_gem_object_wait_moving_fence (struct drm_i915_gem_object *obj,bool intr) { +long ret; +assert_object_held (obj); -return dma_resv_wait_timeout (obj->base. resv,DMA_RESV_USAGE_KERNEL , - intr,MAX_SCHEDULE_TIMEOUT ); + + ret =dma_resv_wait_timeout (obj->base. resv,DMA_RESV_USAGE_KERNEL , + intr,MAX_SCHEDULE_TIMEOUT ); + +return ret <0 ? ret :0 ; }#if IS_ENABLED (CONFIG_DRM_I915_SELFTEST )
Re: [Intel-gfx] [PATCH 2/2] drm/i915: fix i915_gem_object_wait_moving_fence
Am 08.04.22 um 11:08 schrieb Tvrtko Ursulin:
Quoted 12 lines · Matthew Auld
Quoted 10 lines
All of CI is just failing with the following, which prevents loading of the module:
i915 0000:03:00.0: [drm] *ERROR* Scratch setup failed
Best guess is that this comes from the
pin_map()for the scratch page, which does ani915_gem_object_wait_moving_fence()somewhere. It looks like this now calls intodma_resv_wait_timeout()which can return the remaining timeout, leading to the caller thinking this is an error.
Quoted 5 lines
Quoted 1 line
Fixes 1d7f5e6c5240 ("drm/i915: drop bo->moving dependency")Has this one went in bypassing i915 CI and merged via drm-misc-next? If so I think it's the 2nd large disruption to i915 CI flows recently so the lesson here is try not to bypass i915 CI when merging i915 patches.
In this particular example, unless there were merge conflicts causing the series not to apply against drm-tip, it should have been doable to copy intel-gfx on all patches and so get the CI results. (Even if just with --subject-prefix=CI && --suppress-cc=all before merging.)
Exactly that was the problem. I didn't got any usable CI results for this set because it always caused merge conflicts between i915 and drm-misc-next in drm-tip.
Regards,
Christian.
Quoted 36 lines
The second question is which branch to merge through, on which I think i915 maintainers would have liked to be consulted.
Regards,
Tvrtko
Quoted 29 lines
Signed-off-by Matthew Auld <[email protected]>Cc Christian König <[email protected]>Cc Daniel Vetter <[email protected]>---
drivers/gpu/drm/i915/gem/i915_gem_object.c| 9 +++++++--1 file changed, 7 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/gem/i915_gem_object.c +7
-2@@ -772,9 +772,14 @@ int i915_gem_object_get_moving_fence(structdrm_i915_gem_object *obj, int i915_gem_object_wait_moving_fence(struct drm_i915_gem_object *obj, bool intr) { + long ret; + assert_object_held(obj); - return dma_resv_wait_timeout(obj->base. resv,DMA_RESV_USAGE_KERNEL , - intr, MAX_SCHEDULE_TIMEOUT); + + ret = dma_resv_wait_timeout(obj->base. resv, DMA_RESV_USAGE_KERNEL, + intr, MAX_SCHEDULE_TIMEOUT); + + return ret < 0 ? ret : 0; }#if
IS_ENABLED(CONFIG_DRM_I915_SELFTEST)
Re: [Intel-gfx] [PATCH 2/2] drm/i915: fix i915_gem_object_wait_moving_fence
Quoted 13 lines · Christian König
Am 08.04.22 um 11:08 schrieb Tvrtko Ursulin:
Quoted 12 lines · Matthew Auld
Quoted 10 lines
All of CI is just failing with the following, which prevents loading of the module:
i915 0000:03:00.0: [drm] *ERROR* Scratch setup failed
Best guess is that this comes from the
pin_map()for the scratch page, which does ani915_gem_object_wait_moving_fence()somewhere. It looks like this now calls intodma_resv_wait_timeout()which can return the remaining timeout, leading to the caller thinking this is an error.
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Fixes 1d7f5e6c5240 ("drm/i915: drop bo->moving dependency")Has this one went in bypassing i915 CI and merged via drm-misc-next? If so I think it's the 2nd large disruption to i915 CI flows recently so the lesson here is try not to bypass i915 CI when merging i915 patches.
In this particular example, unless there were merge conflicts causing the series not to apply against drm-tip, it should have been doable to copy intel-gfx on all patches and so get the CI results. (Even if just with --subject-prefix=CI && --suppress-cc=all before merging.)
Exactly that was the problem. I didn't got any usable CI results for this set because it always caused merge conflicts between i915 and drm-misc-next in drm-tip.
Then a staged approach should be used. First merge the core stuff and when we backmerge to drm-intel(-gt)-next send the i915 parts out.
Because knock on effect of such large of a CI fire too many many people on our side is very significant.
Regards,
Tvrtko
Quoted 41 lines
Regards,
Christian.Quoted 36 lines
The second question is which branch to merge through, on which I think i915 maintainers would have liked to be consulted.
Regards,
Tvrtko
Quoted 29 lines
Signed-off-by Matthew Auld <[email protected]>Cc Christian König <[email protected]>Cc Daniel Vetter <[email protected]>---
drivers/gpu/drm/i915/gem/i915_gem_object.c| 9 +++++++--1 file changed, 7 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/gem/i915_gem_object.c +7
-2@@ -772,9 +772,14 @@ int i915_gem_object_get_moving_fence(structdrm_i915_gem_object *obj, int i915_gem_object_wait_moving_fence(struct drm_i915_gem_object *obj, bool intr) { + long ret; + assert_object_held(obj); - return dma_resv_wait_timeout(obj->base. resv,DMA_RESV_USAGE_KERNEL , - intr, MAX_SCHEDULE_TIMEOUT); + + ret = dma_resv_wait_timeout(obj->base. resv, DMA_RESV_USAGE_KERNEL, + intr, MAX_SCHEDULE_TIMEOUT); + + return ret < 0 ? ret : 0; }#if
IS_ENABLED(CONFIG_DRM_I915_SELFTEST)
Re: [Intel-gfx] [PATCH 2/2] drm/i915: fix i915_gem_object_wait_moving_fence
Am 08.04.22 um 11:23 schrieb Tvrtko Ursulin:
Quoted 19 lines · Christian König
Quoted 17 lines
Am 08.04.22 um 11:08 schrieb Tvrtko Ursulin:
Quoted 16 lines · Matthew Auld
Quoted 11 lines
All of CI is just failing with the following, which prevents loading of the module:
i915 0000:03:00.0: [drm] *ERROR* Scratch setup failed
Best guess is that this comes from the
pin_map()for the scratch page, which does ani915_gem_object_wait_moving_fence()somewhere. It looks like this now calls intodma_resv_wait_timeout()which can return the remaining timeout, leading to the caller thinking this is an error.Fixes 1d7f5e6c5240 ("drm/i915: drop bo->moving dependency")Has this one went in bypassing i915 CI and merged via drm-misc-next? If so I think it's the 2nd large disruption to i915 CI flows recently so the lesson here is try not to bypass i915 CI when merging i915 patches.
Quoted 7 lines
Quoted 3 lines
Quoted 1 line
In this particular example, unless there were merge conflicts causing the series not to apply against drm-tip, it should have been doable to copy intel-gfx on all patches and so get the CI results. (Even if just with --subject-prefix=CI && --suppress-cc=all before merging.)
Exactly that was the problem. I didn't got any usable CI results for this set because it always caused merge conflicts between i915 and drm-misc-next in drm-tip.
Then a staged approach should be used. First merge the core stuff and when we backmerge to drm-intel(-gt)-next send the i915 parts out.
Because knock on effect of such large of a CI fire too many many people on our side is very significant.
Sorry for that. I thought we had everything covered in drm-tip, but looks like it still broke.
BTW: Why is the CI system failing?
Regards,
Christian.
Quoted 47 lines
Regards,
Tvrtko
Quoted 42 lines
Regards,
Christian.Quoted 37 lines
The second question is which branch to merge through, on which I think i915 maintainers would have liked to be consulted.
Regards,
Tvrtko
Quoted 30 lines
Signed-off-by Matthew Auld <[email protected]>Cc Christian König <[email protected]>Cc Daniel Vetter <[email protected]>---
drivers/gpu/drm/i915/gem/i915_gem_object.c| 9 +++++++--1 file changed, 7 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/gem/i915_gem_object.c +7
-2@@ -772,9 +772,14 @@ int i915_gem_object_get_moving_fence(structdrm_i915_gem_object *obj, int i915_gem_object_wait_moving_fence(struct drm_i915_gem_object *obj, bool intr) { + long ret; + assert_object_held(obj); - return dma_resv_wait_timeout(obj->base. resv,DMA_RESV_USAGE_KERNEL , - intr, MAX_SCHEDULE_TIMEOUT); + + ret = dma_resv_wait_timeout(obj->base. resv,DMA_RESV_USAGE_KERNEL , + intr, MAX_SCHEDULE_TIMEOUT); + + return ret < 0 ? ret : 0;}
#ifIS_ENABLED(CONFIG_DRM_I915_SELFTEST)
Am 07.04.22 um 18:45 schrieb Matthew Auld:
Quoted 6 lines
I guess this was missed in the conversion or something.
Fixes 7bc80a5462c3 ("dma-buf: add enum dma_resv_usage v4")Signed-off-by Matthew Auld <[email protected]>Cc Christian König <[email protected]>Cc Daniel Vetter <[email protected]>
My best guess is that this is a rebase/merge conflict. I'm 100% sure i915 was compiling fine before I pushed the patch.
Anyway Reviewed-by: Christian König <[email protected]> for the series.
Thanks,
Christian.
Quoted 17 lines
--- drivers/gpu/drm/i915/i915_deps.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/gpu/drm/i915/i915_deps.c +1
-1@@ -226,7 +226,7 @@ int i915_deps_add_resv(struct i915_deps *deps, struct dma_resv *resv,struct dma_fence *fence;dma_resv_assert_held (resv); -dma_resv_for_each_fence (&iter, resv, true, fence) { +dma_resv_for_each_fence (&iter, resv,dma_resv_usage_rw (true), fence) {int ret =i915_deps_add_dependency (deps, fence, ctx);if (ret)
Quoted 9 lines · Christian König
Am 07.04.22 um 18:45 schrieb Matthew Auld:
Quoted 6 lines
I guess this was missed in the conversion or something.
Fixes 7bc80a5462c3 ("dma-buf: add enum dma_resv_usage v4")Signed-off-by Matthew Auld <[email protected]>Cc Christian König <[email protected]>Cc Daniel Vetter <[email protected]>My best guess is that this is a rebase/merge conflict. I'm 100% sure i915 was compiling fine before I pushed the patch.
That was my thinking also, but building drm-misc-next I get the same error:
drivers/gpu/drm/i915/i915_deps.c: In function ‘i915_deps_add_resv’:drivers/gpu/drm/i915/i915_deps.c:229:46: error: implicit conversion from ‘enum <anonymous>’ to ‘enum dma_resv_usage’ [-Werror=enum-conversion]
229 | dma_resv_for_each_fence(&iter, resv, true, fence) {
| ^~~~./include/linux/dma-resv.h:297:47: note: in definition of macro ‘dma_resv_for_each_fence’
297 | for (dma_resv_iter_begin(cursor, obj, usage), \
| ^~~~~
Quoted 2 lines
Anyway Reviewed-by: Christian König <[email protected]> for the series.
Thanks.
Quoted 22 lines
Thanks,
Christian.Quoted 17 lines
---
drivers/gpu/drm/i915/i915_deps.c| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)drivers/gpu/drm/i915/i915_deps.c +1
-1@@ -226,7 +226,7 @@ int i915_deps_add_resv(struct i915_deps *deps, struct dma_resv *resv, struct dma_fence *fence; dma_resv_assert_held(resv); - dma_resv_for_each_fence(&iter, resv, true, fence) { + dma_resv_for_each_fence(&iter, resv, dma_resv_usage_rw(true), fence) { int ret = i915_deps_add_dependency(deps, fence, ctx); if (ret)
Quoted 11 lines · Christian König
Am 07.04.22 um 18:45 schrieb Matthew Auld:
Quoted 6 lines
I guess this was missed in the conversion or something.
Fixes 7bc80a5462c3 ("dma-buf: add enum dma_resv_usage v4")Signed-off-by Matthew Auld <[email protected]>Cc Christian König <[email protected]>Cc Daniel Vetter <[email protected]>My best guess is that this is a rebase/merge conflict. I'm 100% sure i915 was compiling fine before I pushed the patch.
Anyway Reviewed-by: Christian König <[email protected]> for the series.
Christian, could you merge the first patch? I need to re-spin the second patch it seems.
Quoted 22 lines
Thanks,
Christian.Quoted 17 lines
---
drivers/gpu/drm/i915/i915_deps.c| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)drivers/gpu/drm/i915/i915_deps.c +1
-1@@ -226,7 +226,7 @@ int i915_deps_add_resv(struct i915_deps *deps, struct dma_resv *resv, struct dma_fence *fence; dma_resv_assert_held(resv); - dma_resv_for_each_fence(&iter, resv, true, fence) { + dma_resv_for_each_fence(&iter, resv, dma_resv_usage_rw(true), fence) { int ret = i915_deps_add_dependency(deps, fence, ctx); if (ret)
Am 08.04.22 um 10:32 schrieb Matthew Auld:
Quoted 9 lines · Christian König
Quoted 8 lines
Am 07.04.22 um 18:45 schrieb Matthew Auld:
Quoted 6 lines
I guess this was missed in the conversion or something.
Fixes 7bc80a5462c3 ("dma-buf: add enum dma_resv_usage v4")Signed-off-by Matthew Auld <[email protected]>Cc Christian König <[email protected]>Cc Daniel Vetter <[email protected]>
Quoted 5 lines
Quoted 3 lines
My best guess is that this is a rebase/merge conflict. I'm 100% sure i915 was compiling fine before I pushed the patch.
Anyway Reviewed-by: Christian König <[email protected]> for the series.
Christian, could you merge the first patch? I need to re-spin the second patch it seems.
Pushed.
Christian.
Quoted 23 lines
Quoted 23 lines
Thanks,
Christian.Quoted 17 lines
---
drivers/gpu/drm/i915/i915_deps.c| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)drivers/gpu/drm/i915/i915_deps.c +1
-1@@ -226,7 +226,7 @@ int i915_deps_add_resv(struct i915_deps *deps, struct dma_resv *resv, struct dma_fence *fence; dma_resv_assert_held(resv); - dma_resv_for_each_fence(&iter, resv, true, fence) { + dma_resv_for_each_fence(&iter, resv, dma_resv_usage_rw(true), fence) { int ret = i915_deps_add_dependency(deps, fence, ctx); if (ret)
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: fix broken build
In reply to Matthew Auld== Series Details ==
== Series Details ==
Series: series starting with [1/2] drm/i915: fix broken build
URL : https://patchwork.freedesktop.org/series/102354/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11472 -> Patchwork_22820
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/index.html
Participating hosts (49 -> 36)
------------------------------
Additional (2): fi-bwr-2160 fi-pnv-d510
Missing (15): fi-bdw-samus fi-bdw-5557u bat-adls-5 bat-dg1-6 bat-dg1-5 shard-tglu bat-dg2-8 bat-dg2-9 fi-bsw-cyan bat-adlp-6 bat-rpls-1 shard-rkl shard-dg1 bat-jsl-2 bat-jsl-1
Known issues
------------
Here are the changes found in Patchwork_22820 that come from known issues:
### CI changes ###
#### Possible fixes ####
* boot:
- fi-elk-e7500: [FAIL][1] -> [PASS][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-elk-e7500/boot.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-elk-e7500/boot.html
- fi-blb-e6850: [FAIL][3] -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-blb-e6850/boot.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-blb-e6850/boot.html
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@cs-sdma:
- fi-hsw-g3258: NOTRUN -> [SKIP][5] ([fdo#109271] / [fdo#109315]) +17 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-hsw-g3258/igt@amdgpu/[email protected]
* igt@amdgpu/amd_cs_nop@nop-compute0:
- fi-ilk-650: NOTRUN -> [SKIP][6] ([fdo#109271]) +39 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-ilk-650/igt@amdgpu/[email protected]
* igt@amdgpu/amd_prime@amd-to-i915:
- fi-kbl-x1275: NOTRUN -> [SKIP][7] ([fdo#109271]) +19 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-x1275/igt@amdgpu/[email protected]
* igt@amdgpu/amd_prime@i915-to-amd:
- fi-snb-2520m: NOTRUN -> [SKIP][8] ([fdo#109271]) +41 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-snb-2520m/igt@amdgpu/[email protected]
* igt@core_hotunplug@unbind-rebind:
- fi-skl-6700k2: NOTRUN -> [DMESG-WARN][9] ([i915#5437])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-skl-6700k2/igt@[email protected]
- fi-rkl-guc: NOTRUN -> [DMESG-WARN][10] ([i915#5577])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-rkl-guc/igt@[email protected]
- fi-bsw-n3050: NOTRUN -> [DMESG-WARN][11] ([i915#5437])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bsw-n3050/igt@[email protected]
- fi-cfl-guc: NOTRUN -> [DMESG-WARN][12] ([i915#5437])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-guc/igt@[email protected]
- fi-kbl-soraka: NOTRUN -> [DMESG-WARN][13] ([i915#5437])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-soraka/igt@[email protected]
- fi-tgl-1115g4: NOTRUN -> [DMESG-WARN][14] ([i915#5577])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-tgl-1115g4/igt@[email protected]
- fi-bxt-dsi: NOTRUN -> [DMESG-WARN][15] ([i915#5437])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bxt-dsi/igt@[email protected]
- fi-adl-ddr5: NOTRUN -> [DMESG-WARN][16] ([i915#5577])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-adl-ddr5/igt@[email protected]
- fi-cfl-8700k: NOTRUN -> [DMESG-WARN][17] ([i915#5437])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-8700k/igt@[email protected]
- fi-glk-j4005: NOTRUN -> [DMESG-WARN][18] ([i915#5437])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-glk-j4005/igt@[email protected]
- fi-kbl-7500u: NOTRUN -> [DMESG-WARN][19] ([i915#5437])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-7500u/igt@[email protected]
- fi-bsw-nick: NOTRUN -> [DMESG-WARN][20] ([i915#5437])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bsw-nick/igt@[email protected]
- fi-cfl-8109u: NOTRUN -> [DMESG-WARN][21] ([i915#5437])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-8109u/igt@[email protected]
- fi-skl-guc: NOTRUN -> [DMESG-WARN][22] ([i915#5437])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-skl-guc/igt@[email protected]
- fi-kbl-7567u: NOTRUN -> [DMESG-WARN][23] ([i915#5437])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-7567u/igt@[email protected]
- fi-bsw-kefka: NOTRUN -> [DMESG-WARN][24] ([i915#5437])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bsw-kefka/igt@[email protected]
* igt@fbdev@eof:
- fi-kbl-8809g: NOTRUN -> [INCOMPLETE][25] ([i915#5557])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-8809g/igt@[email protected]
* igt@fbdev@nullptr:
- fi-kbl-guc: [PASS][26] -> [SKIP][27] ([fdo#109271]) +4 similar issues
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-kbl-guc/igt@[email protected]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-guc/igt@[email protected]
* igt@gem_exec_fence@basic-busy@bcs0:
- fi-kbl-guc: NOTRUN -> [SKIP][28] ([fdo#109271]) +1 similar issue
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-guc/igt@gem_exec_fence@[email protected]
- fi-kbl-soraka: NOTRUN -> [SKIP][29] ([fdo#109271]) +9 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-soraka/igt@gem_exec_fence@[email protected]
- fi-cfl-8700k: NOTRUN -> [SKIP][30] ([fdo#109271]) +1 similar issue
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-8700k/igt@gem_exec_fence@[email protected]
* igt@gem_exec_fence@basic-wait@bcs0:
- fi-bxt-dsi: NOTRUN -> [SKIP][31] ([fdo#109271]) +1 similar issue
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bxt-dsi/igt@gem_exec_fence@[email protected]
- fi-kbl-7567u: NOTRUN -> [SKIP][32] ([fdo#109271]) +1 similar issue
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-7567u/igt@gem_exec_fence@[email protected]
- fi-cfl-guc: NOTRUN -> [SKIP][33] ([fdo#109271]) +1 similar issue
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-guc/igt@gem_exec_fence@[email protected]
- fi-skl-guc: NOTRUN -> [SKIP][34] ([fdo#109271]) +1 similar issue
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-skl-guc/igt@gem_exec_fence@[email protected]
- fi-glk-j4005: NOTRUN -> [SKIP][35] ([fdo#109271]) +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-glk-j4005/igt@gem_exec_fence@[email protected]
- fi-skl-6700k2: NOTRUN -> [SKIP][36] ([fdo#109271]) +1 similar issue
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-skl-6700k2/igt@gem_exec_fence@[email protected]
- fi-kbl-7500u: NOTRUN -> [SKIP][37] ([fdo#109271]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-7500u/igt@gem_exec_fence@[email protected]
* igt@gem_exec_suspend@basic-s0@smem:
- fi-bdw-gvtdvm: NOTRUN -> [INCOMPLETE][38] ([i915#4831])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bdw-gvtdvm/igt@gem_exec_suspend@[email protected]
* igt@gem_exec_suspend@basic-s3:
- fi-bwr-2160: NOTRUN -> [SKIP][39] ([fdo#109271]) +65 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bwr-2160/igt@[email protected]
* igt@gem_exec_suspend@basic-s3@smem:
- fi-rkl-11600: NOTRUN -> [INCOMPLETE][40] ([i915#5127])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-rkl-11600/igt@gem_exec_suspend@[email protected]
* igt@gem_huc_copy@huc-copy:
- fi-kbl-soraka: NOTRUN -> [SKIP][41] ([fdo#109271] / [i915#2190])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-soraka/igt@[email protected]
- fi-cfl-8109u: NOTRUN -> [SKIP][42] ([fdo#109271] / [i915#2190])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-8109u/igt@[email protected]
* igt@gem_lmem_swapping@basic:
- fi-elk-e7500: NOTRUN -> [SKIP][43] ([fdo#109271]) +53 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-elk-e7500/igt@[email protected]
- fi-kbl-soraka: NOTRUN -> [SKIP][44] ([fdo#109271] / [i915#4613]) +3 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-soraka/igt@[email protected]
* igt@gem_lmem_swapping@parallel-random-engines:
- fi-cfl-8700k: NOTRUN -> [SKIP][45] ([fdo#109271] / [i915#4613]) +2 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-8700k/igt@[email protected]
- fi-cfl-guc: NOTRUN -> [SKIP][46] ([fdo#109271] / [i915#4613]) +2 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-guc/igt@[email protected]
- fi-hsw-4770: NOTRUN -> [SKIP][47] ([fdo#109271]) +2 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-hsw-4770/igt@[email protected]
* igt@gem_lmem_swapping@random-engines:
- fi-kbl-7567u: NOTRUN -> [SKIP][48] ([fdo#109271] / [i915#4613]) +2 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-7567u/igt@[email protected]
- fi-skl-guc: NOTRUN -> [SKIP][49] ([fdo#109271] / [i915#4613]) +2 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-skl-guc/igt@[email protected]
- fi-glk-j4005: NOTRUN -> [SKIP][50] ([fdo#109271] / [i915#4613]) +2 similar issues
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-glk-j4005/igt@[email protected]
- fi-ivb-3770: NOTRUN -> [SKIP][51] ([fdo#109271]) +36 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-ivb-3770/igt@[email protected]
- fi-skl-6700k2: NOTRUN -> [SKIP][52] ([fdo#109271] / [i915#4613]) +2 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-skl-6700k2/igt@[email protected]
- fi-kbl-7500u: NOTRUN -> [SKIP][53] ([fdo#109271] / [i915#4613]) +2 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-7500u/igt@[email protected]
- fi-hsw-g3258: NOTRUN -> [SKIP][54] ([fdo#109271]) +2 similar issues
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-hsw-g3258/igt@[email protected]
- fi-cfl-8109u: NOTRUN -> [SKIP][55] ([fdo#109271] / [i915#4613]) +3 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-8109u/igt@[email protected]
* igt@gem_lmem_swapping@verify-random:
- fi-kbl-x1275: NOTRUN -> [SKIP][56] ([fdo#109271] / [i915#4613]) +2 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-x1275/igt@[email protected]
- fi-bsw-kefka: NOTRUN -> [SKIP][57] ([fdo#109271]) +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bsw-kefka/igt@[email protected]
- fi-bsw-n3050: NOTRUN -> [SKIP][58] ([fdo#109271]) +3 similar issues
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bsw-n3050/igt@[email protected]
- fi-bxt-dsi: NOTRUN -> [SKIP][59] ([fdo#109271] / [i915#4613]) +2 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bxt-dsi/igt@[email protected]
- fi-rkl-guc: NOTRUN -> [SKIP][60] ([i915#4613]) +2 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-rkl-guc/igt@[email protected]
- fi-adl-ddr5: NOTRUN -> [SKIP][61] ([i915#4613]) +2 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-adl-ddr5/igt@[email protected]
- fi-tgl-1115g4: NOTRUN -> [SKIP][62] ([i915#4613]) +2 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-tgl-1115g4/igt@[email protected]
* igt@i915_selftest@live@hangcheck:
- fi-hsw-4770: NOTRUN -> [INCOMPLETE][63] ([i915#4785])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-hsw-4770/igt@i915_selftest@[email protected]
- fi-snb-2600: NOTRUN -> [INCOMPLETE][64] ([i915#3921])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-snb-2600/igt@i915_selftest@[email protected]
* igt@kms_addfb_basic@addfb25-y-tiled-small-legacy:
- fi-snb-2600: NOTRUN -> [SKIP][65] ([fdo#109271]) +22 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-snb-2600/igt@[email protected]
* igt@kms_busy@basic@flip:
- fi-tgl-u2: NOTRUN -> [DMESG-WARN][66] ([i915#402])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-tgl-u2/igt@kms_busy@[email protected]
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-kbl-soraka: NOTRUN -> [SKIP][67] ([fdo#109271] / [fdo#111827]) +8 similar issues
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-soraka/igt@[email protected]
* igt@kms_chamelium@dp-crc-fast:
- fi-bsw-nick: NOTRUN -> [SKIP][68] ([fdo#109271] / [fdo#111827]) +8 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bsw-nick/igt@[email protected]
* igt@kms_chamelium@dp-hpd-fast:
- fi-ilk-650: NOTRUN -> [SKIP][69] ([fdo#109271] / [fdo#111827]) +8 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-ilk-650/igt@[email protected]
- fi-ivb-3770: NOTRUN -> [SKIP][70] ([fdo#109271] / [fdo#111827]) +8 similar issues
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-ivb-3770/igt@[email protected]
* igt@kms_chamelium@hdmi-crc-fast:
- fi-snb-2600: NOTRUN -> [SKIP][71] ([fdo#109271] / [fdo#111827]) +8 similar issues
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-snb-2600/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-snb-2520m: NOTRUN -> [SKIP][72] ([fdo#109271] / [fdo#111827]) +8 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-snb-2520m/igt@[email protected]
- fi-cfl-8109u: NOTRUN -> [SKIP][73] ([fdo#109271] / [fdo#111827]) +8 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-8109u/igt@[email protected]
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c:
- fi-pnv-d510: NOTRUN -> [SKIP][74] ([fdo#109271] / [i915#5341])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-pnv-d510/igt@[email protected]
- fi-snb-2520m: NOTRUN -> [SKIP][75] ([fdo#109271] / [i915#5341])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-snb-2520m/igt@[email protected]
- fi-bsw-nick: NOTRUN -> [SKIP][76] ([fdo#109271] / [i915#5341])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bsw-nick/igt@[email protected]
- fi-bwr-2160: NOTRUN -> [SKIP][77] ([fdo#109271] / [i915#5341])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bwr-2160/igt@[email protected]
- fi-snb-2600: NOTRUN -> [SKIP][78] ([fdo#109271] / [i915#5341])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-snb-2600/igt@[email protected]
- fi-elk-e7500: NOTRUN -> [SKIP][79] ([fdo#109271] / [i915#5341])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-elk-e7500/igt@[email protected]
- fi-blb-e6850: NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#5341])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-blb-e6850/igt@[email protected]
- fi-ilk-650: NOTRUN -> [SKIP][81] ([fdo#109271] / [i915#5341])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-ilk-650/igt@[email protected]
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-blb-e6850: NOTRUN -> [SKIP][82] ([fdo#109271]) +57 similar issues
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-blb-e6850/igt@[email protected]
- fi-kbl-soraka: NOTRUN -> [SKIP][83] ([fdo#109271] / [i915#533])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-soraka/igt@[email protected]
- fi-cfl-8109u: NOTRUN -> [SKIP][84] ([fdo#109271] / [i915#533])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-8109u/igt@[email protected]
* igt@kms_psr@primary_mmap_gtt:
- fi-cfl-8109u: NOTRUN -> [SKIP][85] ([fdo#109271]) +11 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-8109u/igt@kms_psr@primary_mmap_gtt.html
* igt@prime_vgem@basic-fence-flip:
- fi-bsw-nick: NOTRUN -> [SKIP][86] ([fdo#109271]) +49 similar issues
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bsw-nick/igt@[email protected]
* igt@prime_vgem@basic-userptr:
- fi-pnv-d510: NOTRUN -> [SKIP][87] ([fdo#109271]) +57 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-pnv-d510/igt@[email protected]
#### Possible fixes ####
* igt@core_auth@basic-auth:
- fi-rkl-11600: [SKIP][88] -> [PASS][89]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-rkl-11600/igt@[email protected]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-rkl-11600/igt@[email protected]
- fi-apl-guc: [SKIP][90] ([fdo#109271]) -> [PASS][91]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-apl-guc/igt@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-apl-guc/igt@[email protected]
* igt@gem_basic@create-fd-close:
- fi-hsw-4770: [SKIP][92] ([fdo#109271] / [fdo#109315]) -> [PASS][93] +44 similar issues
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-hsw-4770/igt@[email protected]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-hsw-4770/igt@[email protected]
* igt@gem_close_race@basic-process:
- fi-tgl-u2: [SKIP][94] ([fdo#109315] / [i915#2575]) -> [PASS][95] +49 similar issues
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-tgl-u2/igt@[email protected]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-tgl-u2/igt@[email protected]
- fi-bdw-gvtdvm: [SKIP][96] ([fdo#109271]) -> [PASS][97] +10 similar issues
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-bdw-gvtdvm/igt@[email protected]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bdw-gvtdvm/igt@[email protected]
* igt@gem_close_race@basic-threads:
- fi-hsw-g3258: [SKIP][98] ([fdo#109271] / [fdo#109315]) -> [PASS][99] +44 similar issues
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-hsw-g3258/igt@[email protected]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-hsw-g3258/igt@[email protected]
- fi-rkl-11600: [SKIP][100] ([fdo#109315]) -> [PASS][101] +10 similar issues
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-rkl-11600/igt@[email protected]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-rkl-11600/igt@[email protected]
* igt@gem_exec_store@basic:
- fi-kbl-x1275: [SKIP][102] ([fdo#109271]) -> [PASS][103] +107 similar issues
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-kbl-x1275/igt@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-x1275/igt@[email protected]
- fi-rkl-guc: [SKIP][104] ([fdo#109315]) -> [PASS][105] +43 similar issues
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-rkl-guc/igt@[email protected]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-rkl-guc/igt@[email protected]
* igt@gem_flink_basic@bad-open:
- fi-kbl-7500u: [SKIP][106] ([fdo#109271]) -> [PASS][107] +107 similar issues
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-kbl-7500u/igt@[email protected]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-7500u/igt@[email protected]
* igt@gem_mmap_gtt@basic:
- {fi-ehl-2}: [SKIP][108] ([fdo#109315]) -> [PASS][109] +51 similar issues
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-ehl-2/igt@[email protected]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-ehl-2/igt@[email protected]
* igt@gem_render_linear_blits@basic:
- fi-cfl-8700k: [SKIP][110] ([fdo#109271]) -> [PASS][111] +107 similar issues
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-cfl-8700k/igt@[email protected]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-8700k/igt@[email protected]
* igt@gem_softpin@safe-alignment:
- {fi-jsl-1}: [SKIP][112] ([fdo#109315]) -> [PASS][113] +51 similar issues
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-jsl-1/igt@[email protected]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-jsl-1/igt@[email protected]
* igt@i915_hangman@error-state-basic:
- fi-kbl-guc: [SKIP][114] ([fdo#109271]) -> [PASS][115] +74 similar issues
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-kbl-guc/igt@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-guc/igt@[email protected]
* igt@i915_pm_rpm@basic-rte:
- fi-tgl-1115g4: [SKIP][116] -> [PASS][117] +1 similar issue
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-tgl-1115g4/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-tgl-1115g4/igt@[email protected]
- fi-tgl-u2: [SKIP][118] -> [PASS][119] +1 similar issue
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-tgl-u2/igt@[email protected]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-tgl-u2/igt@[email protected]
* igt@kms_addfb_basic@addfb25-modifier-no-flag:
- fi-cfl-guc: [SKIP][120] ([fdo#109271]) -> [PASS][121] +108 similar issues
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-cfl-guc/igt@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-guc/igt@[email protected]
* igt@kms_addfb_basic@addfb25-yf-tiled-legacy:
- fi-tgl-u2: [SKIP][122] ([fdo#111615] / [i915#2575]) -> [PASS][123]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-tgl-u2/igt@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-tgl-u2/igt@[email protected]
- fi-tgl-1115g4: [SKIP][124] ([fdo#111615] / [i915#2575]) -> [PASS][125]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-tgl-1115g4/igt@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-tgl-1115g4/igt@[email protected]
* igt@kms_addfb_basic@bad-pitch-128:
- fi-rkl-guc: [SKIP][126] -> [PASS][127] +60 similar issues
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-rkl-guc/igt@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-rkl-guc/igt@[email protected]
* igt@kms_addfb_basic@bad-pitch-32:
- fi-adl-ddr5: [SKIP][128] -> [PASS][129] +105 similar issues
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-adl-ddr5/igt@[email protected]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-adl-ddr5/igt@[email protected]
* igt@kms_addfb_basic@bad-pitch-63:
- fi-kbl-7567u: [SKIP][130] ([fdo#109271]) -> [PASS][131] +87 similar issues
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-kbl-7567u/igt@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-7567u/igt@[email protected]
* igt@kms_addfb_basic@bad-pitch-65536:
- fi-hsw-g3258: [SKIP][132] ([fdo#109271]) -> [PASS][133] +62 similar issues
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-hsw-g3258/igt@[email protected]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-hsw-g3258/igt@[email protected]
* igt@kms_addfb_basic@invalid-get-prop:
- fi-bsw-n3050: [SKIP][134] ([fdo#109271]) -> [PASS][135] +95 similar issues
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-bsw-n3050/igt@[email protected]
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-bsw-n3050/igt@[email protected]
* igt@kms_addfb_basic@invalid-set-prop:
- fi-hsw-4770: [SKIP][136] ([fdo#109271]) -> [PASS][137] +62 similar issues
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-hsw-4770/igt@[email protected]
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-hsw-4770/igt@[email protected]
* igt@kms_addfb_basic@too-wide:
- fi-tgl-1115g4: [SKIP][138] ([i915#2575]) -> [PASS][139] +58 similar issues
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-tgl-1115g4/igt@[email protected]
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-tgl-1115g4/igt@[email protected]
* igt@kms_addfb_basic@unused-offsets:
- {fi-ehl-2}: [SKIP][140] -> [PASS][141] +60 similar issues
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-ehl-2/igt@[email protected]
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-ehl-2/igt@[email protected]
* igt@kms_force_connector_basic@prune-stale-modes:
- fi-glk-j4005: [SKIP][142] ([fdo#109271]) -> [PASS][143] +107 similar issues
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-glk-j4005/igt@[email protected]
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-glk-j4005/igt@[email protected]
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c:
- fi-kbl-x1275: [SKIP][144] ([fdo#109271] / [i915#5341]) -> [PASS][145]
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-kbl-x1275/igt@[email protected]
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-kbl-x1275/igt@[email protected]
- fi-cfl-guc: [SKIP][146] ([fdo#109271] / [i915#5341]) -> [PASS][147]
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-cfl-guc/igt@[email protected]
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-guc/igt@[email protected]
- fi-skl-guc: [SKIP][148] ([fdo#109271] / [i915#5341]) -> [PASS][149]
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-skl-guc/igt@[email protected]
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-skl-guc/igt@[email protected]
- fi-cfl-8700k: [SKIP][150] ([fdo#109271] / [i915#5341]) -> [PASS][151]
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/fi-cfl-8700k/igt@[email protected]
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/fi-cfl-8700k/igt@[email protected]
- fi-kbl-7500u: [SKIP][152] ([fdo
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/index.html
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915: fix broken build
In reply to Matthew Auld== Series Details ==
== Series Details ==
Series: series starting with [1/2] drm/i915: fix broken build
URL : https://patchwork.freedesktop.org/series/102354/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11472_full -> Patchwork_22820_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_22820_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_22820_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Participating hosts (12 -> 10)
------------------------------
Missing (2): shard-rkl shard-tglu
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_22820_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_exec_balancer@parallel-bb-first:
- shard-iclb: NOTRUN -> [DMESG-WARN][1] +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb2/igt@[email protected]
* igt@gem_exec_balancer@parallel-contexts:
- shard-tglb: NOTRUN -> [DMESG-WARN][2] +2 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb1/igt@[email protected]
* igt@gem_exec_balancer@parallel-ordering:
- shard-iclb: NOTRUN -> [DMESG-FAIL][3]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb4/igt@[email protected]
#### Warnings ####
* igt@gem_exec_balancer@parallel:
- shard-kbl: [SKIP][4] ([fdo#109271]) -> [DMESG-WARN][5] +3 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/shard-kbl4/igt@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-kbl4/igt@[email protected]
* igt@gem_exec_balancer@parallel-ordering:
- shard-tglb: [SKIP][6] ([fdo#109315] / [i915#2575]) -> [DMESG-FAIL][7]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/shard-tglb6/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb8/igt@[email protected]
- shard-kbl: [SKIP][8] ([fdo#109271]) -> [DMESG-FAIL][9]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/shard-kbl4/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-kbl6/igt@[email protected]
* igt@gem_exec_balancer@parallel-out-fence:
- shard-tglb: [SKIP][10] ([fdo#109315] / [i915#2575]) -> [DMESG-WARN][11] +2 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11472/shard-tglb6/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb2/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_22820_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@feature_discovery@chamelium:
- shard-tglb: NOTRUN -> [SKIP][12] ([fdo#111827])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb6/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][13] ([fdo#111827])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb5/igt@[email protected]
* igt@feature_discovery@display-4x:
- shard-iclb: NOTRUN -> [SKIP][14] ([i915#1839]) +1 similar issue
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb1/igt@[email protected]
* igt@gem_ccs@block-copy-inplace:
- shard-tglb: NOTRUN -> [SKIP][15] ([i915#3555] / [i915#5325]) +2 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb2/igt@[email protected]
* igt@gem_ccs@ctrl-surf-copy-new-ctx:
- shard-tglb: NOTRUN -> [SKIP][16] ([i915#5325])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb1/igt@[email protected]
* igt@gem_ccs@suspend-resume:
- shard-iclb: NOTRUN -> [SKIP][17] ([i915#5327]) +4 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb4/igt@[email protected]
* igt@gem_create@create-massive:
- shard-iclb: NOTRUN -> [DMESG-WARN][18] ([i915#4991]) +1 similar issue
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb2/igt@[email protected]
- shard-snb: NOTRUN -> [DMESG-WARN][19] ([i915#4991]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-snb7/igt@[email protected]
* igt@gem_ctx_param@set-priority-not-supported:
- shard-tglb: NOTRUN -> [SKIP][20] ([fdo#109314])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb6/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][21] ([fdo#109314])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb5/igt@[email protected]
* igt@gem_ctx_persistence@legacy-engines-mixed:
- shard-snb: NOTRUN -> [SKIP][22] ([fdo#109271] / [i915#1099]) +22 similar issues
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-snb6/igt@[email protected]
* igt@gem_ctx_sseu@engines:
- shard-tglb: NOTRUN -> [SKIP][23] ([i915#280]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb1/igt@[email protected]
* igt@gem_eio@unwedge-stress:
- shard-snb: NOTRUN -> [FAIL][24] ([i915#3354])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-snb7/igt@[email protected]
* igt@gem_exec_balancer@parallel-contexts:
- shard-iclb: NOTRUN -> [SKIP][25] ([i915#4525])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb5/igt@[email protected]
* igt@gem_exec_capture@pi@vcs0:
- shard-skl: NOTRUN -> [INCOMPLETE][26] ([i915#4547])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-skl7/igt@gem_exec_capture@[email protected]
* igt@gem_exec_fair@basic-deadline:
- shard-skl: NOTRUN -> [FAIL][27] ([i915#2846])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-skl9/igt@[email protected]
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-kbl: NOTRUN -> [FAIL][28] ([i915#2842]) +1 similar issue
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-kbl1/igt@gem_exec_fair@[email protected]
- shard-glk: NOTRUN -> [FAIL][29] ([i915#2842]) +8 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-glk8/igt@gem_exec_fair@[email protected]
- shard-apl: NOTRUN -> [FAIL][30] ([i915#2842])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-apl3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@vcs0:
- shard-tglb: NOTRUN -> [FAIL][31] ([i915#2842]) +14 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb8/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-iclb: NOTRUN -> [FAIL][32] ([i915#2842]) +10 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb5/igt@gem_exec_fair@[email protected]
* igt@gem_exec_flush@basic-batch-kernel-default-cmd:
- shard-iclb: NOTRUN -> [SKIP][33] ([fdo#109313])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb3/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][34] ([fdo#109313])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb2/igt@[email protected]
* igt@gem_exec_params@no-vebox:
- shard-iclb: NOTRUN -> [SKIP][35] ([fdo#109283])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb1/igt@[email protected]
* igt@gem_exec_params@rsvd2-dirt:
- shard-tglb: NOTRUN -> [SKIP][36] ([fdo#109283])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb7/igt@[email protected]
* igt@gem_exec_params@secure-non-root:
- shard-tglb: NOTRUN -> [SKIP][37] ([fdo#112283]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb7/igt@[email protected]
* igt@gem_lmem_swapping@heavy-random:
- shard-iclb: NOTRUN -> [SKIP][38] ([i915#4613]) +6 similar issues
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb2/igt@[email protected]
* igt@gem_lmem_swapping@parallel-random-engines:
- shard-apl: NOTRUN -> [SKIP][39] ([fdo#109271] / [i915#4613]) +2 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-apl8/igt@[email protected]
- shard-skl: NOTRUN -> [SKIP][40] ([fdo#109271] / [i915#4613]) +1 similar issue
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-skl7/igt@[email protected]
* igt@gem_lmem_swapping@parallel-random-verify:
- shard-tglb: NOTRUN -> [SKIP][41] ([i915#4613]) +4 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb2/igt@[email protected]
* igt@gem_lmem_swapping@smem-oom:
- shard-kbl: NOTRUN -> [SKIP][42] ([fdo#109271] / [i915#4613]) +5 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-kbl6/igt@[email protected]
- shard-glk: NOTRUN -> [SKIP][43] ([fdo#109271] / [i915#4613]) +2 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-glk2/igt@[email protected]
* igt@gem_media_vme:
- shard-tglb: NOTRUN -> [SKIP][44] ([i915#284])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb7/igt@gem_media_vme.html
* igt@gem_mmap_gtt@coherency:
- shard-tglb: NOTRUN -> [SKIP][45] ([fdo#111656]) +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb3/igt@[email protected]
* igt@gem_pread@exhaustion:
- shard-iclb: NOTRUN -> [WARN][46] ([i915#2658])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb5/igt@[email protected]
- shard-snb: NOTRUN -> [WARN][47] ([i915#2658])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-snb6/igt@[email protected]
- shard-tglb: NOTRUN -> [WARN][48] ([i915#2658])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb6/igt@[email protected]
- shard-skl: NOTRUN -> [WARN][49] ([i915#2658])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-skl8/igt@[email protected]
* igt@gem_pxp@create-regular-context-1:
- shard-iclb: NOTRUN -> [SKIP][50] ([i915#4270]) +13 similar issues
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb7/igt@[email protected]
* igt@gem_pxp@regular-baseline-src-copy-readible:
- shard-tglb: NOTRUN -> [SKIP][51] ([i915#4270]) +7 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb1/igt@[email protected]
* igt@gem_render_copy@x-tiled-to-vebox-yf-tiled:
- shard-kbl: NOTRUN -> [SKIP][52] ([fdo#109271]) +429 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-kbl6/igt@[email protected]
* igt@gem_render_copy@yf-tiled-mc-ccs-to-vebox-yf-tiled:
- shard-iclb: NOTRUN -> [SKIP][53] ([i915#768]) +10 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb3/igt@[email protected]
* igt@gem_softpin@evict-snoop:
- shard-iclb: NOTRUN -> [SKIP][54] ([fdo#109312])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb4/igt@[email protected]
* igt@gem_userptr_blits@create-destroy-unsync:
- shard-tglb: NOTRUN -> [SKIP][55] ([i915#3297]) +3 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb2/igt@[email protected]
* igt@gem_userptr_blits@dmabuf-sync:
- shard-kbl: NOTRUN -> [SKIP][56] ([fdo#109271] / [i915#3323])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-kbl7/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][57] ([i915#3323])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb4/igt@[email protected]
* igt@gem_userptr_blits@input-checking:
- shard-skl: NOTRUN -> [DMESG-WARN][58] ([i915#4991])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-skl10/igt@[email protected]
- shard-tglb: NOTRUN -> [DMESG-WARN][59] ([i915#4991]) +1 similar issue
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb1/igt@[email protected]
- shard-apl: NOTRUN -> [DMESG-WARN][60] ([i915#4991])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-apl8/igt@[email protected]
- shard-glk: NOTRUN -> [DMESG-WARN][61] ([i915#4991])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-glk6/igt@[email protected]
- shard-kbl: NOTRUN -> [DMESG-WARN][62] ([i915#4991])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-kbl1/igt@[email protected]
* igt@gem_userptr_blits@unsync-unmap:
- shard-iclb: NOTRUN -> [SKIP][63] ([i915#3297]) +4 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb5/igt@[email protected]
* igt@gem_userptr_blits@vma-merge:
- shard-snb: NOTRUN -> [FAIL][64] ([i915#2724])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-snb5/igt@[email protected]
* igt@gen3_render_linear_blits:
- shard-tglb: NOTRUN -> [SKIP][65] ([fdo#109289]) +12 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb8/igt@gen3_render_linear_blits.html
* igt@gen7_exec_parse@bitmasks:
- shard-iclb: NOTRUN -> [SKIP][66] ([fdo#109289]) +16 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb6/igt@[email protected]
* igt@gen9_exec_parse@unaligned-access:
- shard-iclb: NOTRUN -> [SKIP][67] ([i915#2856]) +14 similar issues
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb8/igt@[email protected]
* igt@gen9_exec_parse@valid-registers:
- shard-tglb: NOTRUN -> [SKIP][68] ([i915#2527] / [i915#2856]) +10 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb8/igt@[email protected]
* igt@i915_hangman@engine-engine-hang:
- shard-snb: NOTRUN -> [SKIP][69] ([fdo#109271]) +1922 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-snb2/igt@[email protected]
* igt@i915_pm_backlight@bad-brightness:
- shard-glk: NOTRUN -> [SKIP][70] ([fdo#109271]) +370 similar issues
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-glk4/igt@[email protected]
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-tglb: NOTRUN -> [SKIP][71] ([i915#1904])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb6/igt@[email protected]
* igt@i915_pm_dc@dc6-dpms:
- shard-skl: NOTRUN -> [FAIL][72] ([i915#454]) +1 similar issue
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-skl6/igt@[email protected]
- shard-iclb: NOTRUN -> [FAIL][73] ([i915#454])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb3/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-tglb: NOTRUN -> [FAIL][74] ([i915#454]) +1 similar issue
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb6/igt@[email protected]
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
- shard-apl: NOTRUN -> [SKIP][75] ([fdo#109271] / [i915#1937])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-apl7/igt@i915_pm_lpsp@[email protected]
- shard-kbl: NOTRUN -> [SKIP][76] ([fdo#109271] / [i915#1937])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-kbl6/igt@i915_pm_lpsp@[email protected]
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-hdmi-a:
- shard-glk: NOTRUN -> [SKIP][77] ([fdo#109271] / [i915#1937])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-glk2/igt@i915_pm_lpsp@[email protected]
* igt@i915_pm_lpsp@screens-disabled:
- shard-iclb: NOTRUN -> [SKIP][78] ([i915#1902])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb5/igt@[email protected]
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: NOTRUN -> [WARN][79] ([i915#1804] / [i915#2684])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb6/igt@[email protected]
- shard-tglb: NOTRUN -> [WARN][80] ([i915#2681] / [i915#2684])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb5/igt@[email protected]
* igt@i915_pm_rpm@dpms-mode-unset-non-lpsp:
- shard-tglb: NOTRUN -> [SKIP][81] ([fdo#111644] / [i915#1397] / [i915#2411]) +3 similar issues
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb5/igt@[email protected]
* igt@i915_pm_rpm@gem-execbuf-stress-pc8:
- shard-iclb: NOTRUN -> [SKIP][82] ([fdo#109293] / [fdo#109506]) +1 similar issue
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb5/igt@[email protected]
* igt@i915_pm_rpm@modeset-non-lpsp-stress-no-wait:
- shard-iclb: NOTRUN -> [SKIP][83] ([fdo#110892]) +3 similar issues
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb8/igt@[email protected]
* igt@i915_pm_rpm@modeset-pc8-residency-stress:
- shard-tglb: NOTRUN -> [SKIP][84] ([fdo#109506] / [i915#2411]) +1 similar issue
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb6/igt@[email protected]
* igt@i915_pm_sseu@full-enable:
- shard-tglb: NOTRUN -> [SKIP][85] ([i915#4387])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb5/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][86] ([i915#4387])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb6/igt@[email protected]
* igt@i915_query@query-topology-known-pci-ids:
- shard-iclb: NOTRUN -> [SKIP][87] ([fdo#109303])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb4/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][88] ([fdo#109303])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb1/igt@[email protected]
* igt@i915_selftest@live@gt_lrc:
- shard-tglb: NOTRUN -> [DMESG-FAIL][89] ([i915#2373])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb1/igt@i915_selftest@live@gt_lrc.html
* igt@i915_selftest@live@gt_pm:
- shard-skl: NOTRUN -> [DMESG-FAIL][90] ([i915#1886])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-skl1/igt@i915_selftest@live@gt_pm.html
- shard-tglb: NOTRUN -> [DMESG-FAIL][91] ([i915#1759])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb1/igt@i915_selftest@live@gt_pm.html
* igt@kms_addfb_basic@invalid-smem-bo-on-discrete:
- shard-tglb: NOTRUN -> [SKIP][92] ([i915#3826])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb8/igt@[email protected]
* igt@kms_atomic@atomic_plane_damage:
- shard-iclb: NOTRUN -> [SKIP][93] ([i915#4765])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb2/igt@kms_atomic@atomic_plane_damage.html
* igt@kms_atomic@plane-primary-overlay-mutable-zpos:
- shard-tglb: NOTRUN -> [SKIP][94] ([i915#404])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb1/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][95] ([i915#404])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb5/igt@[email protected]
* igt@kms_atomic_transition@plane-all-modeset-transition:
- shard-tglb: NOTRUN -> [SKIP][96] ([i915#1769])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb6/igt@[email protected]
* igt@kms_atomic_transition@plane-all-modeset-transition-fencing:
- shard-iclb: NOTRUN -> [SKIP][97] ([i915#1769])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb1/igt@[email protected]
* igt@kms_big_fb@4-tiled-64bpp-rotate-0:
- shard-iclb: NOTRUN -> [SKIP][98] ([i915#5286]) +24 similar issues
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb2/igt@[email protected]
* igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-tglb: NOTRUN -> [SKIP][99] ([i915#5286]) +15 similar issues
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb6/igt@[email protected]
* igt@kms_big_fb@x-tiled-16bpp-rotate-270:
- shard-iclb: NOTRUN -> [SKIP][100] ([fdo#110725] / [fdo#111614]) +10 similar issues
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb5/igt@[email protected]
* igt@kms_big_fb@x-tiled-16bpp-rotate-90:
- shard-tglb: NOTRUN -> [SKIP][101] ([fdo#111614]) +7 similar issues
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb3/igt@[email protected]
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip:
- shard-skl: NOTRUN -> [FAIL][102] ([i915#3743]) +2 similar issues
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-skl7/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip.html
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip:
- shard-skl: NOTRUN -> [SKIP][103] ([fdo#109271] / [i915#3777]) +2 similar issues
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-skl6/igt@[email protected]
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip-async-flip:
- shard-kbl: NOTRUN -> [SKIP][104] ([fdo#109271] / [i915#3777]) +3 similar issues
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-kbl7/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip-async-flip.html
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip:
- shard-apl: NOTRUN -> [SKIP][105] ([fdo#109271] / [i915#3777]) +4 similar issues
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-apl1/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip:
- shard-glk: NOTRUN -> [SKIP][106] ([fdo#109271] / [i915#3777]) +5 similar issues
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-glk7/igt@[email protected]
* igt@kms_big_fb@yf-tiled-addfb-size-overflow:
- shard-tglb: NOTRUN -> [SKIP][107] ([fdo#111615]) +19 similar issues
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb8/igt@[email protected]
* igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0:
- shard-iclb: NOTRUN -> [SKIP][108] ([fdo#110723]) +7 similar issues
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb1/igt@[email protected]
* igt@kms_big_joiner@2x-modeset:
- shard-tglb: NOTRUN -> [SKIP][109] ([i915#2705]) +2 similar issues
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb3/igt@[email protected]
* igt@kms_big_joiner@basic:
- shard-iclb: NOTRUN -> [SKIP][110] ([i915#2705]) +2 similar issues
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb2/igt@[email protected]
* igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][111] ([i915#3689] / [i915#3886]) +14 similar issues
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb2/igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][112] ([i915#3689]) +19 similar issues
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb1/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_ccs.html
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][113] ([fdo#109271] / [i915#3886]) +18 similar issues
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-glk7/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-a-random-ccs-data-yf_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][114] ([fdo#111615] / [i915#3689]) +17 similar issues
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb6/igt@kms_ccs@pipe-a-random-ccs-data-yf_tiled_ccs.html
* igt@kms_ccs@pipe-b-bad-aux-stride-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][115] ([fdo#109271] / [i915#3886]) +13 similar issues
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-skl4/igt@kms_ccs@pipe-b-bad-aux-stride-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs:
- shard-iclb: NOTRUN -> [SKIP][116] ([fdo#109278] / [i915#3886]) +32 similar issues
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb8/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs.html
- shard-kbl: NOTRUN -> [SKIP][117] ([fdo#109271] / [i915#3886]) +18 similar issues
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-kbl6/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][118] ([fdo#109271] / [i915#3886]) +15 similar issues
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-apl6/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs.html
* igt@kms_cdclk@plane-scaling:
- shard-tglb: NOTRUN -> [SKIP][119] ([i915#3742])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-tglb7/igt@[email protected]
* igt@kms_chamelium@dp-hpd-storm:
- shard-iclb: NOTRUN -> [SKIP][120] ([fdo#109284] / [fdo#111827]) +50 similar issues
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-iclb3/igt@[email protected]
* igt@kms_chamelium@hdmi-crc-nonplanar-formats:
- shard-glk: NOTRUN -> [SKIP][121] ([fdo#109271] / [fdo#111827]) +27 similar issues
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-glk5/igt@[email protected]
* igt@kms_chamelium@hdmi-edid-change-during-suspend:
- shard-apl: NOTRUN -> [SKIP][122] ([fdo#109271] / [fdo#111827]) +22 similar issues
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-apl7/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-storm-disable:
- shard-skl: NOTRUN -> [SKIP][123] ([fdo#109271] / [fdo#111827]) +28 similar issues
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-skl7/igt@[email protected]
* igt@kms_chamelium@vga-hpd-without-ddc:
- shard-kbl: NOTRUN -> [SKIP][124] ([fdo#109271] / [fdo#111827]) +33 similar issues
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-kbl7/igt@[email protected]
- shard-snb: NOTRUN -> [SKIP][125] ([fdo#109271] / [fdo#111827]) +85 similar issues
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/shard-snb7/igt@[email protected]
* igt@kms_color@pipe-c-deep-color:
- shard-iclb: NOTRUN -> [SKIP][126] ([fdo#109278] / [i915#35
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22820/index.html