Starting subtest: pipe-C-overlay-size-256 (kms_plane_cursor:1216) igt_kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file ../lib/igt_kms.c:3514: (kms_plane_cursor:1216) igt_kms-CRITICAL: Failed assertion: ret == 0 (kms_plane_cursor:1216) igt_kms-CRITICAL: Last errno: 22, Invalid argument (kms_plane_cursor:1216) igt_kms-CRITICAL: error: -22 != 0 Subtest pipe-C-overlay-size-256 failed.
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * HSW BSW : igt@kms_plane_cursor@pipe-c-* - fail - Failed assertion: ret == 0 - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_256/fi-bsw-n3050/igt@kms_plane_cursor@pipe-c-overlay-size-256.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_256/fi-bsw-n3050/igt@kms_plane_cursor@pipe-c-viewport-size-256.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_256/fi-bsw-n3050/igt@kms_plane_cursor@pipe-c-primary-size-64.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_256/fi-bsw-n3050/igt@kms_plane_cursor@pipe-c-overlay-size-128.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_256/fi-bsw-n3050/igt@kms_plane_cursor@pipe-c-primary-size-128.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_256/fi-bsw-n3050/igt@kms_plane_cursor@pipe-c-primary-size-256.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_256/fi-bsw-n3050/igt@kms_plane_cursor@pipe-c-viewport-size-128.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_256/fi-bsw-n3050/igt@kms_plane_cursor@pipe-c-overlay-size-64.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_256/fi-bsw-n3050/igt@kms_plane_cursor@pipe-c-viewport-size-64.html
-- 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/270.
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.