https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_379/fi-icl-dsi/igt@gem_exec_balancer@bonded-slice.html Starting subtest: bonded-slice (gem_exec_balancer:1156) igt_aux-CRITICAL: Test assertion failure function sig_abort, file ../lib/igt_aux.c:502: (gem_exec_balancer:1156) igt_aux-CRITICAL: Failed assertion: !"GPU hung" Subtest bonded-slice failed. https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_380/fi-bdw-gvtdvm/igt@gem_exec_balancer@bonded-slice.html Starting subtest: bonded-slice (gem_exec_balancer:1075) igt_aux-CRITICAL: Test assertion failure function sig_abort, file ../lib/igt_aux.c:502: (gem_exec_balancer:1075) igt_aux-CRITICAL: Failed assertion: !"GPU hung" Subtest bonded-slice failed.
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BDW ICL: igt@gem_exec_balancer@bonded-slice - fail - Failed assertion: !"GPU hung" - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14515/shard-iclb1/igt@gem_exec_balancer@bonded-slice.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_379/fi-bdw-gvtdvm/igt@gem_exec_balancer@bonded-slice.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_379/fi-icl-dsi/igt@gem_exec_balancer@bonded-slice.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_380/fi-bdw-gvtdvm/igt@gem_exec_balancer@bonded-slice.html
The test looks in order, the fix makes sense, so this failure is unexpected. Not yet observed in the shards, so play it slow and wait for the pattern in the idle runs to develop.
Setting to medium for now, let's keep monitoring.
Last seen three days ago: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7083/shard-iclb4/igt@gem_exec_balancer@bonded-slice.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/464.
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.