Happened on fi-bsw-n3050 Detail Value Returncode 99 Time 0:01:03.911723 Stdout IGT-Version: 1.15-gf749a2d (x86_64) (Linux: 4.7.0-rc7-CI-Nightly_684+ x86_64) Stack trace: #0 [__igt_fail_assert+0x101] #1 [busy+0x38b] #2 [run_poll+0x21f] #3 [__real_main227+0xfd] #4 [main+0x23] #5 [__libc_start_main+0xf0] #6 [_start+0x29] Subtest basic-wait-before-default: FAIL (0.004s) Test requirement not met in function gem_require_ring, file ioctl_wrappers.c:1450: Test requirement: gem_has_ring(fd, ring) Test requirement not met in function gem_require_ring, file ioctl_wrappers.c:1450: Test requirement: gem_has_ring(fd, ring) Test requirement not met in function gem_require_ring, file ioctl_wrappers.c:1450: Test requirement: gem_has_ring(fd, ring) Test requirement not met in function gem_require_ring, file ioctl_wrappers.c:1450: Test requirement: gem_has_ring(fd, ring) Test requirement not met in function gem_require_ring, file ioctl_wrappers.c:1450: Test requirement: gem_has_ring(fd, ring) Test requirement not met in function gem_require_ring, file ioctl_wrappers.c:1450: Test requirement: gem_has_ring(fd, ring) Stderr (prime_busy:10977) CRITICAL: Test assertion failure function busy, file prime_busy.c:138: (prime_busy:10977) CRITICAL: Failed assertion: prime_busy(&pfd[SCRATCH], false) Subtest basic-wait-before-default failed. **** DEBUG **** (prime_busy:10977) DEBUG: Test requirement passed: __gem_execbuf(fd, &execbuf) == 0 (prime_busy:10977) CRITICAL: Test assertion failure function busy, file prime_busy.c:138: (prime_busy:10977) CRITICAL: Failed assertion: prime_busy(&pfd[SCRATCH], false) **** END **** Environment PIGLIT_PLATFORM="mixed_glx_egl" PIGLIT_SOURCE_DIR="/opt/igt/piglit" Command /opt/igt/tests/prime_busy --run-subtest basic-wait-before-default dmesg
4.7.0-rc7-CI-Nightly is not the right marker for an uptodate build. Seems odd.
fi-bsw-n3050 had to be recovered; it was stuck on a corrupt fs.
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.