https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_292/fi-icl-u3/igt@kms_concurrent@pipe-c.html Starting subtest: pipe-C Testing resolution with connector eDP-1 using pipe C with seed 1517155323 Testing resolution with connector DP-1 using pipe C with seed 1517155323 Test requirement not met in function test_init, file ../tests/kms_concurrent.c:86: Test requirement: !(ret != 0) Last errno: 22, Invalid argument Subtest pipe-C: SKIP (1.358s) Test requirement not met in function run_tests_for_pipe, file ../tests/kms_concurrent.c:344: Test requirement: !(pipe >= data->display.n_pipes) Test requirement not met in function run_tests_for_pipe, file ../tests/kms_concurrent.c:344: Test requirement: !(pipe >= data->display.n_pipes) Test requirement not met in function run_tests_for_pipe, file ../tests/kms_concurrent.c:344: Test requirement: !(pipe >= data->display.n_pipes)
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@kms_concurrent@pipe-c|igt@kms_plane@plane-panning-top-left-pipe-b-planes - skip - Test requirement: !(ret != 0), SKIP - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_292/fi-icl-u3/igt@kms_concurrent@pipe-c.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_294/fi-icl-u3/igt@kms_plane@plane-panning-top-left-pipe-b-planes.html
A CI Bug Log filter associated to this bug has been updated: {- ICL: igt@kms_concurrent@pipe-c|igt@kms_plane@plane-panning-top-left-pipe-b-planes - skip - Test requirement: !(ret != 0), SKIP -} {+ ICL: igt@kms_concurrent@pipe-c|igt@kms_plane@plane-panning-top-left-pipe-b-planes - skip - Test requirement: !(ret != 0), SKIP +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6150/re-icl-u/igt@kms_concurrent@pipe-a.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6150/re-icl-u/igt@kms_concurrent@pipe-b.html
Imre, Ville, are these relevant skips or can be ignored?
(In reply to Jani Saarinen from comment #3) > Imre, Ville, are these relevant skips or can be ignored? The dmesg doesn't tell us why the commit failed. I wonder if we're missing a DRM_DEBUG from some relevant path...
kms_concurrent IGT test exercises concurrent atomic commits by swithcing resolution and drawing a plane in different locations on the screen. kms_plane performs plane tests such as position, panning and pixel formats. Failure in these tests could mean that that planes are not drawn at all and we may have corrupted image or flickering.
Tried reproducing locally, however couldn't reproduce the issue. Is it possible it happens only after particular test gets executed before this? Order of test execution?
-- 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/303.
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.