Bug 109295

Summary:	[CI][SHARDS] igt@prime_vgem@fence-*-hang - skip - Test requirement: vgem_fence_has_flag(vgem, WIP_VGEM_FENCE_NOTIMEOUT), SKIP
Product:	DRI	Reporter:	Martin Peres <martin.peres>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	CLOSED INVALID	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	high	CC:	intel-gfx-bugs
Version:	XOrg git
Hardware:	Other
OS:	All
Whiteboard:	ReadyForDev
i915 platform:	ICL	i915 features:

Description Martin Peres 2019-01-10 16:00:13 UTC

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb5/igt@prime_vgem@fence-flip-hang.html

Test requirement: vgem_fence_has_flag(vgem, WIP_VGEM_FENCE_NOTIMEOUT)
Subtest fence-flip-hang: SKIP

Comment 1 CI Bug Log 2019-01-10 16:00:42 UTC

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

### New filters associated

* ICL: igt@prime_vgem@fence-*-hang - skip - Test requirement: vgem_fence_has_flag(vgem, WIP_VGEM_FENCE_NOTIMEOUT), SKIP
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb5/igt@prime_vgem@fence-flip-hang.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb6/igt@prime_vgem@fence-read-hang.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb6/igt@prime_vgem@fence-write-hang.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_3578/shard-iclb2/igt@prime_vgem@fence-write-hang.html

Comment 2 Chris Wilson 2019-01-10 16:41:35 UTC

Kernel feature required for the test to work only exists as patches.

Comment 3 Martin Peres 2019-01-10 21:04:47 UTC

(In reply to Chris Wilson from comment #2)
> Kernel feature required for the test to work only exists as patches.

Thanks, any pointer to the series you are talking about?

I understand how this bug should be closed (feature requests don't belong here), I am still changing the status to INVALID, so as not to confuse cibuglog's filtering where NOTABUG is used to hide the skips that are expected and not an issue.

For this case, we actually could fix the bug by landing patches, and we might want to keep track of that :)

Comment 4 Chris Wilson 2019-01-10 21:10:42 UTC

It's just a debug feature for the purpose of this test (to disable the fence timeout within vgem itself so that we rely on the fence timeout in i915 instead).

1469043583-14348-1-git-send-email-chris@chris-wilson.co.uk on intel-gfx/dri-devel@

Comment 5 CI Bug Log 2019-04-30 12:25:30 UTC

A CI Bug Log filter associated to this bug has been updated:

{- ICL: igt@prime_vgem@fence-*-hang - skip - Test requirement: vgem_fence_has_flag(vgem, WIP_VGEM_FENCE_NOTIMEOUT), SKIP -}
{+ CML ICL: igt@prime_vgem@fence-*-hang - skip - Test requirement: vgem_fence_has_flag(vgem, WIP_VGEM_FENCE_NOTIMEOUT), SKIP +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-cml-u2/igt@prime_vgem@fence-write-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_267/fi-cml-u/igt@prime_vgem@fence-write-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_267/fi-cml-u/igt@prime_vgem@fence-read-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_268/fi-cml-u/igt@prime_vgem@fence-flip-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_268/fi-cml-u/igt@prime_vgem@fence-write-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_268/fi-cml-u/igt@prime_vgem@fence-read-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_269/fi-cml-u/igt@prime_vgem@fence-flip-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_269/fi-cml-u/igt@prime_vgem@fence-write-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_269/fi-cml-u/igt@prime_vgem@fence-read-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-cml-u/igt@prime_vgem@fence-flip-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-cml-u/igt@prime_vgem@fence-write-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-cml-u/igt@prime_vgem@fence-read-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-cml-u2/igt@prime_vgem@fence-flip-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6010/re-cml-u/igt@prime_vgem@fence-flip-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6010/re-cml-u/igt@prime_vgem@fence-read-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6010/re-cml-u/igt@prime_vgem@fence-write-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6012/re-cml-u/igt@prime_vgem@fence-flip-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6012/re-cml-u/igt@prime_vgem@fence-read-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6012/re-cml-u/igt@prime_vgem@fence-write-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-cml-u2/igt@prime_vgem@fence-read-hang.html

Comment 6 CI Bug Log 2019-09-10 10:36:41 UTC

A CI Bug Log filter associated to this bug has been updated:

{- CML ICL: igt@prime_vgem@fence-*-hang - skip - Test requirement: vgem_fence_has_flag(vgem, WIP_VGEM_FENCE_NOTIMEOUT), SKIP -}
{+ CML ICL TGL: igt@prime_vgem@fence-*-hang - skip - Test requirement: vgem_fence_has_flag(vgem, WIP_VGEM_FENCE_NOTIMEOUT), SKIP +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_365/fi-tgl-u/igt@prime_vgem@fence-write-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_365/fi-tgl-u/igt@prime_vgem@fence-flip-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_365/fi-tgl-u/igt@prime_vgem@fence-read-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_363/fi-tgl-u/igt@prime_vgem@fence-flip-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_363/fi-tgl-u/igt@prime_vgem@fence-read-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@prime_vgem@fence-write-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@prime_vgem@fence-flip-hang.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@prime_vgem@fence-read-hang.html

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.