112336 – [CI][DRMTIP]igt@gem_eio@reset-stress - fail - Failed assertion: sync_fence_status(hang->out_fence) == -5

Bug 112336 - [CI][DRMTIP]igt@gem_eio@reset-stress - fail - Failed assertion: sync_fence_status(hang->out_fence) == -5

Summary: [CI][DRMTIP]igt@gem_eio@reset-stress - fail - Failed assertion: sync_fence_st...

Status:	RESOLVED FIXED

Alias:	None

Product:	DRI
Classification:	Unclassified
Component:	DRM/Intel (show other bugs)
Version:	DRI git
Hardware:	Other All

Importance:	not set not set
Assignee:	Intel GFX Bugs mailing list
QA Contact:	Intel GFX Bugs mailing list

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2019-11-19 07:53 UTC by Lakshmi
Modified:	2019-11-19 10:02 UTC (History)
CC List:	1 user (show)

See Also:
i915 platform:	BDW, BSW/CHT
i915 features:	GEM/Other

Attachments

Description Lakshmi 2019-11-19 07:53:17 UTC

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bdw-5557u/igt@gem_eio@reset-stress.html
Starting subtest: reset-stress
(gem_eio:1099) CRITICAL: Test assertion failure function reset_stress, file ../tests/i915/gem_eio.c:792:
(gem_eio:1099) CRITICAL: Failed assertion: sync_fence_status(hang->out_fence) == -5
(gem_eio:1099) CRITICAL: error: 1 != -5
Subtest reset-stress failed.

Comment 1 CI Bug Log 2019-11-19 07:54:08 UTC

The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* BSW BDW: igt@gem_eio@reset-stress - fail - Failed assertion: sync_fence_status(hang-&gt;out_fence) == -5
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bdw-5557u/igt@gem_eio@reset-stress.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bsw-kefka/igt@gem_eio@reset-stress.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bsw-n3050/igt@gem_eio@reset-stress.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bsw-nick/igt@gem_eio@reset-stress.html

Comment 2 Chris Wilson 2019-11-19 10:02:07 UTC

Broken igt.

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.