From: Patchwork <patchwork@emeril.freedesktop.org>
To: Andi Shyti <andi.shyti@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for new engine discovery interface (rev5)
Date: Tue, 15 Jan 2019 12:39:06 -0000 [thread overview]
Message-ID: <20190115123906.8003.29156@emeril.freedesktop.org> (raw)
In-Reply-To: <20190115123511.11474-1-andi.shyti@intel.com>
== Series Details ==
Series: new engine discovery interface (rev5)
URL : https://patchwork.freedesktop.org/series/52699/
State : failure
== Summary ==
IGT patchset build failed on latest successful build
951e2b1a016b750544d0f42459b13b9c70631c68 intel-ci: Drop gem_ctx_switch/heavy from BAT
239/263 testcase check: gen3_render_linear_blits OK 0.16 s
240/263 testcase check: gen3_render_mixed_blits OK 0.13 s
241/263 testcase check: gen3_render_tiledx_blits OK 0.16 s
242/263 testcase check: gen3_render_tiledy_blits OK 0.16 s
243/263 testcase check: gem_eio OK 0.14 s
244/263 testcase check: gem_mocs_settings OK 0.12 s
245/263 testcase check: perf_pmu OK 0.15 s
246/263 testcase check: testdisplay OK 0.17 s
247/263 testcase check: amdgpu/amd_abm OK 0.12 s
248/263 testcase check: amdgpu/amd_basic OK 0.11 s
249/263 testcase check: amdgpu/amd_cs_nop OK 0.12 s
250/263 testcase check: amdgpu/amd_prime OK 0.13 s
251/263 runner OK 1.36 s
252/263 runner_json OK 0.09 s
253/263 assembler: test/mov OK 0.08 s
254/263 assembler: test/frc OK 0.07 s
255/263 assembler: test/regtype OK 0.08 s
256/263 assembler: test/rndd OK 0.09 s
257/263 assembler: test/rndu OK 0.08 s
258/263 assembler: test/rnde OK 0.08 s
259/263 assembler: test/rnde-intsrc OK 0.07 s
260/263 assembler: test/rndz OK 0.06 s
261/263 assembler: test/lzd OK 0.06 s
262/263 assembler: test/not OK 0.03 s
263/263 assembler: test/immediate OK 0.06 s
OK: 262
FAIL: 1
SKIP: 0
TIMEOUT: 0
The output from the failed tests:
137/263 testcase check: gem_ctx_isolation FAIL 0.22 s
--- command ---
/home/cidrm/igt-gpu-tools/tests/igt_command_line.sh gem_ctx_isolation
--- stdout ---
tests/gem_ctx_isolation:
Checking invalid option handling...
Checking valid option handling...
Checking subtest enumeration...
FAIL: tests/gem_ctx_isolation
-------
Full log written to /home/cidrm/igt-gpu-tools/build/meson-logs/testlog.txt
FAILED: meson-test
/usr/bin/python3 -u /usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-01-15 12:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 12:35 [igt-dev] [RFC PATCH v4 0/3] new engine discovery interface Andi Shyti
2019-01-15 12:35 ` [igt-dev] [RFC PATCH v4 1/3] include/drm-uapi: import i915_drm.h header file Andi Shyti
2019-01-15 12:35 ` [igt-dev] [RFC PATCH v4 2/3] lib: implement new engine discovery interface Andi Shyti
2019-01-15 13:00 ` Chris Wilson
2019-01-15 13:14 ` Tvrtko Ursulin
2019-01-15 13:19 ` Chris Wilson
2019-01-15 13:32 ` Tvrtko Ursulin
2019-01-15 13:43 ` Chris Wilson
2019-01-15 13:41 ` Andi Shyti
2019-01-15 13:50 ` Tvrtko Ursulin
2019-01-15 13:55 ` Andi Shyti
2019-01-15 13:32 ` Andi Shyti
2019-01-15 12:35 ` [igt-dev] [RFC PATCH v4 3/3] tests: gem_exec_basic: add "exec-ctx" buffer execution demo test Andi Shyti
2019-01-15 13:04 ` Chris Wilson
2019-01-15 13:43 ` Andi Shyti
2019-01-15 12:39 ` Patchwork [this message]
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=20190115123906.8003.29156@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=andi.shyti@intel.com \
--cc=igt-dev@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