Bug 109497 - [CI][DRMTIP] igt@gem_exec_schedule@in-order-render - skip - Test requirement: gem_scheduler_enabled(fd), SKIP
Summary: [CI][DRMTIP] igt@gem_exec_schedule@in-order-render - skip - Test requirement:...
Status: RESOLVED NOTABUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-29 15:31 UTC by Martin Peres
Modified: 2019-01-29 15:36 UTC (History)
1 user (show)

See Also:
i915 platform: ICL
i915 features: GEM/Other


Attachments

Description Martin Peres 2019-01-29 15:31:57 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-icl-u3/igt@gem_exec_schedule@in-order-render.html

Using Execlists submission
Found wedged device, trying to reset and continue
Test requirement not met in function __real_main1194, file ../tests/i915/gem_exec_schedule.c:1235:
Test requirement: gem_scheduler_enabled(fd)
Subtest in-order-render: SKIP
Test requirement not met in function __real_main1194, file ../tests/i915/gem_exec_schedule.c:1331:
Test requirement: gem_scheduler_enabled(fd)
Comment 1 CI Bug Log 2019-01-29 15:32:26 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL: igt@gem_exec_schedule@in-order-render - skip - Test requirement: gem_scheduler_enabled(fd), SKIP
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-icl-u3/igt@gem_exec_schedule@in-order-render.html
Comment 2 Chris Wilson 2019-01-29 15:35:29 UTC
GPU died earlier in the shard, test was skipped as it could not be run.
Comment 3 Martin Peres 2019-01-29 15:36:45 UTC
(In reply to Chris Wilson from comment #2)
> GPU died earlier in the shard, test was skipped as it could not be run.

But shouldn't igt_runner stop executing then?


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.