Attachment 134263 Details for Bug 102799 – test log

test log

testlog.txt (text/plain), 9.59 KB, created by Armando Antonio on 2017-09-15 18:22:36 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Armando Antonio

Created: 2017-09-15 18:22:36 UTC

Size: 9.59 KB

patch

obsolete

>(08:18 AM) [gfx@BXT-3] [tests]$ : sudo -E ./gem_exec_nop --r headless --d
>IGT-Version: 1.19-gb6ea8b2 (x86_64) (Linux: 4.13.0-drm-tip-ww37-commit-29603d0+ x86_64)
>(gem_exec_nop:2085) drmtest-DEBUG: Test requirement passed: !(fd<0)
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) drmtest-DEBUG: Test requirement passed: is_i915_device(fd) && has_known_intel_chipset(fd)
>(gem_exec_nop:2085) ioctl-wrappers-DEBUG: Test requirement passed: err == 0
>Using GuC submission
>(gem_exec_nop:2085) igt-core-DEBUG: Starting subtest: headless
>(gem_exec_nop:2085) DEBUG: Test requirement passed: nr_connected > 0
>(gem_exec_nop:2085) igt-kms-DEBUG: VT: graphics mode set (mode was 0x0)
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>With one display connected: 9.10us
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>Without a display connected (headless): 42.53us
>(gem_exec_nop:2085) CRITICAL: Test assertion failure function headless, file gem_exec_nop.c:185:
>(gem_exec_nop:2085) CRITICAL: Failed assertion: (n_headless) <= (1.0 + 0.1f) * n_display && (n_headless) >= (1.0 - 0.1f) * n_display
>(gem_exec_nop:2085) CRITICAL: 'n_headless' != 'n_display' (0.000043 not within 10.000000% tolerance of 0.000009)
>Stack trace:
>  #0 [__igt_fail_assert+0x101]
>  #1 [__real_main614+0x78d]
>  #2 [__libc_csu_init+0x0]
>Subtest headless failed.
>**** DEBUG ****
>(gem_exec_nop:2085) DEBUG: Test requirement passed: nr_connected > 0
>(gem_exec_nop:2085) igt-kms-DEBUG: VT: graphics mode set (mode was 0x0)
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) INFO: With one display connected: 9.10us
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(gem_exec_nop:2085) INFO: Without a display connected (headless): 42.53us
>(gem_exec_nop:2085) CRITICAL: Test assertion failure function headless, file gem_exec_nop.c:185:
>(gem_exec_nop:2085) CRITICAL: Failed assertion: (n_headless) <= (1.0 + 0.1f) * n_display && (n_headless) >= (1.0 - 0.1f) * n_display
>(gem_exec_nop:2085) CRITICAL: 'n_headless' != 'n_display' (0.000043 not within 10.000000% tolerance of 0.000009)
>(gem_exec_nop:2085) igt-core-INFO: Stack trace:
>(gem_exec_nop:2085) igt-core-INFO:   #0 [__igt_fail_assert+0x101]
>(gem_exec_nop:2085) igt-core-INFO:   #1 [__real_main614+0x78d]
>(gem_exec_nop:2085) igt-core-INFO:   #2 [__libc_csu_init+0x0]
>****  END  ****
>Subtest headless: FAIL (10.673s)
>(gem_exec_nop:2085) igt-core-DEBUG: Exiting with status code 99
>(gem_exec_nop:2085) igt-kms-DEBUG: VT: original mode 0x0 restored
>(gem_exec_nop:2085) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'

Actions: View

Attachments on bug 102799: 134262 | 134263

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.