https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_371/fi-tgl-u2/igt@gem_exec_schedule@semaphore-user.html Test requirement not met in function semaphore_userlock, file ../tests/i915/gem_exec_schedule.c:391: Test requirement: gem_scheduler_has_semaphores(i915) Subtest semaphore-user: SKIP (0.000s)
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * TGL: igt@gem_exec_schedule@semaphore-user - skip - Test requirement: gem_scheduler_has_semaphores(i915), SKIP - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_371/fi-tgl-u/igt@gem_exec_schedule@semaphore-user.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_368/fi-tgl-u/igt@gem_exec_schedule@semaphore-user.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_369/fi-tgl-u/igt@gem_exec_schedule@semaphore-user.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_369/fi-tgl-u2/igt@gem_exec_schedule@semaphore-user.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_370/fi-tgl-u/igt@gem_exec_schedule@semaphore-user.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_370/fi-tgl-u2/igt@gem_exec_schedule@semaphore-user.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_371/fi-tgl-u2/igt@gem_exec_schedule@semaphore-user.html
*** This bug has been marked as a duplicate of bug 111715 ***
*** Bug 111711 has been marked as a duplicate of this bug. ***
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * TGL: igt@gem_busy@extended-semaphore-* - skip - Test requirement: has_semaphores(fd), SKIP - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_368/fi-tgl-u/igt@gem_busy@extended-semaphore-vcs0.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_368/fi-tgl-u/igt@gem_busy@extended-semaphore-bcs0.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_368/fi-tgl-u/igt@gem_busy@extended-semaphore-rcs0.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_368/fi-tgl-u/igt@gem_busy@extended-semaphore-vcs1.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_368/fi-tgl-u2/igt@gem_busy@extended-semaphore-bcs0.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_368/fi-tgl-u2/igt@gem_busy@extended-semaphore-rcs0.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_368/fi-tgl-u2/igt@gem_busy@extended-semaphore-vecs0.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_369/fi-tgl-u/igt@gem_busy@extended-semaphore-rcs0.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_369/fi-tgl-u2/igt@gem_busy@extended-semaphore-rcs0.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_370/fi-tgl-u/igt@gem_busy@extended-semaphore-rcs0.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_370/fi-tgl-u2/igt@gem_busy@extended-semaphore-rcs0.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_371/fi-tgl-u/igt@gem_busy@extended-semaphore-rcs0.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_371/fi-tgl-u2/igt@gem_busy@extended-semaphore-rcs0.html
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * TGL: igt@gem_exec_schedule@semaphore-codependency - skip - Test requirement: i == ARRAY_SIZE(task), SKIP - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_369/fi-tgl-u/igt@gem_exec_schedule@semaphore-codependency.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_369/fi-tgl-u2/igt@gem_exec_schedule@semaphore-codependency.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_370/fi-tgl-u/igt@gem_exec_schedule@semaphore-codependency.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_370/fi-tgl-u2/igt@gem_exec_schedule@semaphore-codependency.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_371/fi-tgl-u/igt@gem_exec_schedule@semaphore-codependency.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_371/fi-tgl-u2/igt@gem_exec_schedule@semaphore-codependency.html
This issue was seen at least twice every two runs, now not seen for 9 runs. Closing!
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.