From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for series starting with [1/3] igt/gem_cpu_reloc: Check HW exists before attempting to use it
Date: Thu, 17 May 2018 09:28:50 -0000 [thread overview]
Message-ID: <20180517092850.2661.54524@emeril.freedesktop.org> (raw)
In-Reply-To: <20180517082330.32760-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/3] igt/gem_cpu_reloc: Check HW exists before attempting to use it
URL : https://patchwork.freedesktop.org/series/43310/
State : failure
== Summary ==
IGT patchset build failed on latest successful build
eccae1360d6d01e73c6af2bd97122cef708207ef igt: Drop Intel from the name in docs and paths
245/257 testcase check: amdgpu/amd_cs_nop OK 0.08 s
246/257 testcase check: amdgpu/amd_prime OK 0.07 s
247/257 assembler: test/mov OK 0.07 s
248/257 assembler: test/frc OK 0.04 s
249/257 assembler: test/regtype OK 0.06 s
250/257 assembler: test/rndd OK 0.04 s
251/257 assembler: test/rndu OK 0.03 s
252/257 assembler: test/rnde OK 0.01 s
253/257 assembler: test/rnde-intsrc OK 0.05 s
254/257 assembler: test/rndz OK 0.04 s
255/257 assembler: test/lzd OK 0.03 s
256/257 assembler: test/not OK 0.03 s
257/257 assembler: test/immediate OK 0.03 s
OK: 256
FAIL: 1
SKIP: 0
TIMEOUT: 0
The output from the failed tests:
183/257 testcase check: kms_frontbuffer_tracking FAIL 0.27 s
--- command ---
/home/cidrm/igt-gpu-tools/tests/igt_command_line.sh kms_frontbuffer_tracking
--- stdout ---
tests/kms_frontbuffer_tracking:
Checking invalid option handling...
Checking valid option handling...
Checking subtest enumeration...
FAIL: tests/kms_frontbuffer_tracking
--- stderr ---
(kms_frontbuffer_tracking:32435) intel_chipset-CRITICAL: Test assertion failure function intel_get_drm_devid, file ../lib/intel_chipset.c:132:
(kms_frontbuffer_tracking:32435) intel_chipset-CRITICAL: Failed assertion: is_i915_device(fd)
(kms_frontbuffer_tracking:32435) intel_chipset-CRITICAL: Last errno: 25, Inappropriate ioctl for device
Test kms_frontbuffer_tracking failed.
**** DEBUG ****
(kms_frontbuffer_tracking:32435) intel_chipset-CRITICAL: Test assertion failure function intel_get_drm_devid, file ../lib/intel_chipset.c:132:
(kms_frontbuffer_tracking:32435) intel_chipset-CRITICAL: Failed assertion: is_i915_device(fd)
(kms_frontbuffer_tracking:32435) intel_chipset-CRITICAL: Last errno: 25, Inappropriate ioctl for device
**** END ****
kms_frontbuffer_tracking: ../lib/igt_core.c:1129: igt_fail: Assertion `igt_can_fail()' failed.
Received signal SIGABRT.
-------
Full log written to /home/cidrm/igt-gpu-tools/build/meson-logs/testlog.txt
FAILED: meson-test
/usr/bin/python3 -u /usr/share/meson/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-05-17 9:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 8:23 [PATCH i-g-t 1/3] igt/gem_cpu_reloc: Check HW exists before attempting to use it Chris Wilson
2018-05-17 8:23 ` [PATCH i-g-t 2/3] igt/gem_blits: Check for blitter support before use Chris Wilson
2018-05-17 17:58 ` Antonio Argenziano
2018-05-17 8:23 ` [PATCH i-g-t 3/3] igt/kms_frontbuffer_tracking: Skip over IGT_DRAW_BLT when there's no BLT Chris Wilson
2018-05-17 9:56 ` [PATCH i-g-t] " Chris Wilson
2018-05-17 23:16 ` Antonio Argenziano
2018-05-17 9:28 ` Patchwork [this message]
2018-05-17 10:38 ` ✓ Fi.CI.BAT: success for series starting with [1/3] igt/gem_cpu_reloc: Check HW exists before attempting to use it (rev2) Patchwork
2018-05-17 13:43 ` ✓ Fi.CI.IGT: " Patchwork
2018-05-17 15:08 ` [PATCH i-g-t 1/3] igt/gem_cpu_reloc: Check HW exists before attempting to use it Antonio Argenziano
2018-05-17 15:37 ` Chris Wilson
2018-05-17 16:29 ` Antonio Argenziano
2018-05-17 16:52 ` Chris Wilson
2018-05-17 17:01 ` Antonio Argenziano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180517092850.2661.54524@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).