Attachment 128524 Details for Bug 99130 – basic-wait-all log

basic-wait-all log

file_99130.txt (text/plain), 1.50 KB, created by Dorota Czaplejewicz on 2016-12-17 16:48:01 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Dorota Czaplejewicz

Created: 2016-12-17 16:48:01 UTC

Size: 1.50 KB

patch

obsolete

>IGT-Version: 1.17-g68c59ce (x86_64) (Linux: 4.9.0-CI-CI_DRM_1968_vanilla+ x86_64)
>(gem_wait:20933) igt-core-DEBUG: Test requirement passed: !igt_run_in_simulation()
>(gem_wait:20933) drmtest-DEBUG: Test requirement passed: !(fd<0)
>(gem_wait:20933) drmtest-DEBUG: Test requirement passed: drmSetMaster(fd) == 0
>(gem_wait:20933) igt-core-DEBUG: Starting subtest: basic-wait-all
>(gem_wait:20933) igt-dummyload-DEBUG: Test requirement passed: nengine
>(gem_wait:20933) CRITICAL: Test assertion failure function basic, file gem_wait.c:91:
>(gem_wait:20933) CRITICAL: Failed assertion: __gem_wait(fd, &wait) == -62
>(gem_wait:20933) CRITICAL: Last errno: 4, Interrupted system call
>(gem_wait:20933) CRITICAL: error: 0 != -62
>Stack trace:
>  #0 [__igt_fail_assert+0xf1]
>  #1 [basic+0x289]
>  #2 [_start+0x0]
>  #3 [<unknown>+0x0]
>  #4 [<unknown>+0x0]
>Subtest basic-wait-all failed.
>**** DEBUG ****
>(gem_wait:20933) igt-dummyload-DEBUG: Test requirement passed: nengine
>(gem_wait:20933) CRITICAL: Test assertion failure function basic, file gem_wait.c:91:
>(gem_wait:20933) CRITICAL: Failed assertion: __gem_wait(fd, &wait) == -62
>(gem_wait:20933) CRITICAL: Last errno: 4, Interrupted system call
>(gem_wait:20933) CRITICAL: error: 0 != -62
>****  END  ****
>Subtest basic-wait-all: FAIL (1.180s)
>(gem_wait:20933) ioctl-wrappers-DEBUG: Test requirement passed: has_ban_period || has_bannable
>(gem_wait:20933) igt-gt-DEBUG: Test requirement passed: has_gpu_reset(fd)
>(gem_wait:20933) igt-core-DEBUG: Exiting with status code 99

Actions: View

Attachments on bug 99130: 128524 | 128525 | 128544 | 128545 | 128546 | 128547 | 128548 | 128606

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.