[igt-dev] ✗ Fi.CI.BAT: failure for new engine discovery interface (rev7)
Petri Latvala
petri.latvala at intel.com
Thu Feb 7 08:58:40 UTC 2019
On Wed, Feb 06, 2019 at 09:25:38AM +0000, Patchwork wrote:
> == 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]
> -------
>
These tests are constructing subtests for each known engine. Your
engine loop changes make it not possible to enumerate any names
statically, without accessing the driver.
--
Petri Latvala
More information about the igt-dev
mailing list