https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_218/fi-icl-u2/igt@gem_exec_schedule@wide-render.html Starting subtest: wide-render (gem_exec_schedule:1522) igt_vgem-CRITICAL: Test assertion failure function vgem_fence_signal, file ../lib/igt_vgem.c:193: (gem_exec_schedule:1522) igt_vgem-CRITICAL: Failed assertion: __vgem_fence_signal(fd, fence) == 0 (gem_exec_schedule:1522) igt_vgem-CRITICAL: error: -110 != 0 Subtest wide-render failed. **** DEBUG **** (gem_exec_schedule:1522) drmtest-DEBUG: Test requirement passed: !(fd<0) (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: vgem_has_fences(cork->vgem.device) (gem_exec_schedule:1522) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0' (gem_exec_schedule:1522) drmtest-DEBUG: Test requirement passed: !(fd<0) (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: vgem_has_fences(cork->vgem.device) (gem_exec_schedule:1522) INFO: Submitted 7 requests over 1024 contexts in 10858.9ms (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_dummyload-DEBUG: Test requirement passed: nengine (gem_exec_schedule:1522) igt_vgem-CRITICAL: Test assertion failure function vgem_fence_signal, file ../lib/igt_vgem.c:193: (gem_exec_schedule:1522) igt_vgem-CRITICAL: Failed assertion: __vgem_fence_signal(fd, fence) == 0 (gem_exec_schedule:1522) igt_vgem-CRITICAL: error: -110 != 0 (gem_exec_schedule:1522) igt_core-INFO: Stack trace: (gem_exec_schedule:1522) igt_core-INFO: #0 ../lib/igt_core.c:1474 __igt_fail_assert() (gem_exec_schedule:1522) igt_core-INFO: #1 ../lib/igt_vgem.c:194 vgem_fence_signal() (gem_exec_schedule:1522) igt_core-INFO: #2 ../lib/igt_dummyload.c:457 unplug_vgem_handle() (gem_exec_schedule:1522) igt_core-INFO: #3 ../lib/igt_dummyload.c:541 igt_cork_unplug() (gem_exec_schedule:1522) igt_core-INFO: #4 ../tests/i915/gem_exec_schedule.c:144 unplug_show_queue() (gem_exec_schedule:1522) igt_core-INFO: #5 ../tests/i915/gem_exec_schedule.c:950 wide() (gem_exec_schedule:1522) igt_core-INFO: #6 ../tests/i915/gem_exec_schedule.c:1332 __real_main1209() (gem_exec_schedule:1522) igt_core-INFO: #7 ../tests/i915/gem_exec_schedule.c:1209 main() (gem_exec_schedule:1522) igt_core-INFO: #8 ../csu/libc-start.c:344 __libc_start_main() (gem_exec_schedule:1522) igt_core-INFO: #9 [_start+0x2a] **** END **** Subtest wide-render: FAIL (11.242s)
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@gem_exec_schedule@wide-render - Fail - Failed assertion: __vgem_fence_signal(fd, fence) == 0 - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_218/fi-icl-u2/igt@gem_exec_schedule@wide-render.html
No tell-tales at all to explain the delay; which is itself quite odd.
So far this is an isolated failure, let's keep watching...
A CI Bug Log filter associated to this bug has been updated: {- ICL: igt@gem_exec_schedule@wide-render - Fail - Failed assertion: __vgem_fence_signal(fd, fence) == 0 -} {+ ICL: igt@gem_exec_schedule@wide-* - Fail - Failed assertion: __vgem_fence_signal(fd, fence) == 0 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_231/fi-icl-u3/igt@gem_exec_schedule@wide-blt.html
A CI Bug Log filter associated to this bug has been updated: {- ICL: igt@gem_exec_schedule@wide-* - Fail - Failed assertion: __vgem_fence_signal(fd, fence) == 0 -} {+ ICL: igt@gem_exec_schedule@* - Fail - Failed assertion: __vgem_fence_signal(fd, fence) == 0 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_244/fi-icl-y/igt@gem_exec_schedule@deep-vebox.html
(In reply to Francesco Balestrieri from comment #3) > So far this is an isolated failure, let's keep watching... Seen once every 3.7 in average on drmtip.
Not seen for 3 months / 729 runs, was occurring every week / ~10 runs. Closing.
(In reply to Francesco Balestrieri from comment #7) > Not seen for 3 months / 729 runs, was occurring every week / ~10 runs. > Closing. No new occurrences on drmtip, reproduction rate is once in every 5 drmtip runs. Not seen for the last 90 drmtip runs. Closing and archiving this issue.
The CI Bug Log issue associated to this bug has been archived. New failures matching the above filters will not be associated to this bug anymore.
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.