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 (rev7)
Date: Wed, 06 Feb 2019 09:25:38 -0000 [thread overview]
Message-ID: <20190206092538.9303.56503@emeril.freedesktop.org> (raw)
In-Reply-To: <20190206091850.2078-1-andi.shyti@intel.com>
== Series Details ==
Series: new engine discovery interface (rev7)
URL : https://patchwork.freedesktop.org/series/52699/
State : failure
== Summary ==
IGT patchset build failed on latest successful build
592b854fead32c2b0dac7198edfb9a6bffd66932 tools/intel_watermark: Clean up the platform checks in the ilk+ code
The output from the failed tests:
138/266 testcase check: gem_ctx_isolation FAIL 0.36 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
--- stderr ---
Received signal SIGSEGV.
Stack trace:
#0 [fatal_sig_handler+0xd5]
#1 [killpg+0x40]
#2 [__real_main687+0x810]
#3 [main+0x44]
#4 [__libc_start_main+0xe7]
#5 [_start+0x2a]
-------
248/266 testcase check: perf_pmu FAIL 0.21 s
--- command ---
/home/cidrm/igt-gpu-tools/tests/igt_command_line.sh perf_pmu
--- stdout ---
tests/perf_pmu:
Checking invalid option handling...
Checking valid option handling...
Checking subtest enumeration...
FAIL: tests/perf_pmu
--- stderr ---
Received signal SIGSEGV.
Stack trace:
#0 [fatal_sig_handler+0xd5]
#1 [killpg+0x40]
#2 [__real_main1671+0xf1f]
#3 [main+0x44]
#4 [__libc_start_main+0xe7]
#5 [_start+0x2a]
-------
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
next prev parent reply other threads:[~2019-02-06 9:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 9:18 [igt-dev] [RFC PATCH v6 0/4] new engine discovery interface Andi Shyti
2019-02-06 9:18 ` [igt-dev] [RFC PATCH v6 1/4] include/drm-uapi: import i915_drm.h header file Andi Shyti
2019-02-06 9:18 ` [igt-dev] [RFC PATCH v6 2/4] lib: implement new engine discovery interface Andi Shyti
2019-02-06 9:31 ` Chris Wilson
2019-02-08 12:55 ` Andi Shyti
2019-02-08 13:03 ` Chris Wilson
2019-02-06 18:11 ` Antonio Argenziano
2019-02-08 11:03 ` Andi Shyti
2019-02-08 11:06 ` Chris Wilson
2019-02-06 9:18 ` [igt-dev] [RFC PATCH v6 3/4] lib: ioctl_wrappers: reach engines by index as well Andi Shyti
2019-02-06 9:33 ` Chris Wilson
2019-02-06 9:18 ` [igt-dev] [RFC PATCH v6 4/4] tests: gem_exec_basic: add "exec-ctx" buffer execution demo test Andi Shyti
2019-02-06 9:25 ` Patchwork [this message]
2019-02-07 8:58 ` [igt-dev] ✗ Fi.CI.BAT: failure for new engine discovery interface (rev7) Petri Latvala
2019-02-08 10:56 ` Andi Shyti
2019-02-12 8:43 ` Tvrtko Ursulin via igt-dev
2019-02-12 11:39 ` Arkadiusz Hiler via igt-dev
2019-02-12 11:56 ` Tvrtko Ursulin via igt-dev
2019-02-15 9:50 ` Petri Latvala via igt-dev
2019-02-25 13:22 ` Tvrtko Ursulin
2019-02-26 9:32 ` Petri Latvala
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=20190206092538.9303.56503@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