Started at CI_DRM_3365 SNB-shards, also on CI_DRM_3366, potential regression.
(gem_busy:1645) CRITICAL: Test assertion failure function busy_blt, file gem_busy.c:129:
(gem_busy:1645) CRITICAL: Failed assertion: gem_bo_busy(fd, object.handle)
Subtest close-race failed.
It's just the test making an assertion on a handle in one thread after closing it in another. That test is particularly tricky because we keep trying to use common functions that assert success (when the test is intentionally causing failures).
commit 7e07894d8b0f567cb4241b5bed8a9644874ddd47 (HEAD, upstream/master)
Author: Chris Wilson <email@example.com>
Date: Fri Dec 1 21:53:03 2017 +0000
igt/gem_busy: Replace arbitrary busy batch with indefinite spinbatch
In CI, we were observing situations where the busy blt would complete
before the very next instruction (in userspace) to assert that it was
busy. This is entirely possible if the process was scheduled away and
slept for longer than the arbitrary batch. Instead replace arbitrariness
with a precise infinity.
v2: Be respectful to UP!
v3: Move spinbatch to owning process to avoid serialisation delays.
Signed-off-by: Chris Wilson <firstname.lastname@example.org>
Reviewed-by: Joonas Lahtinen <email@example.com>
Fix included in CI_DRM_3449, I will close