https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_305/fi-byt-j1900/igt@gem_vm_create@isolation.html Starting subtest: isolation (gem_vm_create:1133) CRITICAL: Test assertion failure function isolation, file ../tests/i915/gem_vm_create.c:329: (gem_vm_create:1133) CRITICAL: Failed assertion: result == 1 (gem_vm_create:1133) CRITICAL: error: 0 != 1 Subtest isolation failed. **** DEBUG **** (gem_vm_create:1133) CRITICAL: Test assertion failure function isolation, file ../tests/i915/gem_vm_create.c:329: (gem_vm_create:1133) CRITICAL: Failed assertion: result == 1 (gem_vm_create:1133) CRITICAL: error: 0 != 1 (gem_vm_create:1133) igt_core-INFO: Stack trace: (gem_vm_create:1133) igt_core-INFO: #0 ../lib/igt_core.c:1514 __igt_fail_assert() (gem_vm_create:1133) igt_core-INFO: #1 ../tests/i915/gem_vm_create.c:166 __real_main375() (gem_vm_create:1133) igt_core-INFO: #2 [<unknown>+0x0] **** END **** Subtest isolation: FAIL (0.024s)
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BYT: igt@gem_vm_create@isolation - fail - Failed assertion: result == 1, error: 0 != 1 - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_305/fi-byt-j1900/igt@gem_vm_create@isolation.html
Another case where I shouldn't have used gem_read() because we are lying to the kernel about write hazards, I think.
> Another case where I shouldn't have used gem_read() because we are lying to > the kernel about write hazards, I think. Was there a fix? It hasn't happened again, although there have only been a few runs.
Nope, I haven't sent a patch for this yet. It will just take a perfect storm to detect.
A CI Bug Log filter associated to this bug has been updated: {- BYT: igt@gem_vm_create@isolation - fail - Failed assertion: result == 1, error: 0 != 1 -} {+ APL BYT: igt@gem_vm_create@isolation - fail - Failed assertion: result == 1, error: 0 != 1 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7373/shard-apl4/igt@gem_vm_create@isolation.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/314.
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.