Summary: | [CI]: igt@kms_plane_scaling@pipe-[ac]-scaler-* - incomplete | ||
---|---|---|---|
Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
Component: | DRM/Intel | Assignee: | Petri Latvala <petri.latvala> |
Status: | RESOLVED MOVED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | ICL | i915 features: | CI Infra |
Description
Lakshmi
2019-03-13 16:15:46 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@kms_plane_scaling@pipe-[ac]-scaler-* - incomplete (No new failures associated) Latest failure is here https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5742/shard-iclb8/igt@kms_plane_scaling@pipe-a-scaler-with-rotation.html (In reply to Lakshmi from comment #2) > Latest failure is here https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_242/fi-icl-u3/igt@kms_plane_scaling@pipe-a-scaler-with-clipping-clamping.html A CI Bug Log filter associated to this bug has been updated: {- ICL: igt@kms_plane_scaling@pipe-[ac]-scaler-* - incomplete -} {+ ICL: igt@kms_plane_scaling@pipe-[ac]-scaler-* - incomplete +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_243/fi-icl-y/igt@kms_plane_scaling@pipe-b-scaler-with-clipping-clamping.html * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_245/fi-icl-y/igt@kms_plane_scaling@pipe-b-scaler-with-clipping-clamping.html * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_246/fi-icl-y/igt@kms_plane_scaling@pipe-b-scaler-with-clipping-clamping.html A CI Bug Log filter associated to this bug has been updated: {- ICL: igt@kms_plane_scaling@pipe-[ac]-scaler-* - incomplete -} {+ ICL: igt@kms_plane_scaling@pipe-[ac]-scaler-* - incomplete +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_244/fi-icl-y/igt@kms_plane_scaling@pipe-c-scaler-with-clipping-clamping.html Seems issue still happening and similar like on 110040 but BIOS update did not help here. Change priority. Mika: I merged a patch to fix the test issues with planar YUV formats https://patchwork.freedesktop.org/series/58233/ Let's wait and see if the patch has any relevance on bug probability. From customer point of view, the worst case scenario here is that we are not able to scale the plane correctly. This is bad for user experience. Further comments from Mika: Clip & clamp tests also crashes on my ICL-Y. The test itself takes quite a bit of time and the debug information shows progress on the test until it seems to freeze and a signal is sent to kill the test. This is how, I can replicate this crash. The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@runner@aborted - fail - Previous test: kms_plane_scaling (pipe-a-scaler-with-clipping-clamping) - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_271/fi-icl-y/igt@runner@aborted.html From J-P: It start to look like this bug is not a bug in kernel nor the test but features in combination with IGT and CI which cause this "bug". On IGT there has been added more supported framebuffer formats which this test will try all of, this with added multiple monitors mostly being 4k will increase the load causing this test to execute quite a while. ICL on my desk with icl-u where I have two 4k displays (edp&hdmi) this test will run almost steady time from 100-200 seconds which increases the likeliness of this test to hit 'test set overall ~960 seconds timeout in CI' This test should be rewritten for many different reasons, one of them being excessive use of time. Moving to CI infra. Lowering priority. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/249. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.