[igt-dev] ✗ Fi.CI.BAT: failure for new engine discovery interface (rev7)

[Andi Shyti]

Hi Petri,

> > 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.

dammit! I didn't see it. This means that I have to leave the
intel_execution_engines2[] as it is. But this has to be a
temporary solution.

Thanks, Petri,
Andi