https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-tglb1/igt@gem_sync@basic-all.html Starting subtest: basic-all Subtest basic-all failed. **** DEBUG **** (gem_sync:2434) DEBUG: Test requirement passed: num_engines (gem_sync:2434) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0' (gem_sync:2434) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0' (gem_sync:2434) igt_core-INFO: Timed out waiting for children **** END **** Subtest basic-all: FAIL (15.015s) https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-tglb4/igt@gem_sync@basic-store-all.html Starting subtest: basic-store-all Subtest basic-store-all failed. **** DEBUG **** (gem_sync:1115) DEBUG: Test requirement passed: num_engines (gem_sync:1115) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0' (gem_sync:1115) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0' (gem_sync:1115) igt_core-INFO: Timed out waiting for children **** END **** Subtest basic-store-all: FAIL (15.015s)
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * TGL: igt@gem_sync@basic-(store-)?all - fail -Timed out waiting for children - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5101/fi-tgl-u2/igt@gem_sync@basic-store-all.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14595/fi-tgl-u2/igt@gem_sync@basic-store-all.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-tglb1/igt@gem_sync@basic-all.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-tglb4/igt@gem_sync@basic-store-all.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14598/fi-tgl-u2/igt@gem_sync@basic-all.html
Nothing to see here, just playing with TGL hax.
Setting to medium/normal for now.
Experiment removed. fi-tgl-u came back from the grave.
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.