Bug 111938

Summary: [CI][SHARDS] igt@kms_flip@.*-wf_vblank - fail - Failed assertion: fabs((elapsed - expected) / expected) <= 0.005
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED MOVED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: CFL, ICL, TGL i915 features: display/Other

Description Lakshmi 2019-10-09 14:28:24 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5218/shard-tglb2/igt@kms_flip@flip-vs-absolute-wf_vblank.html
	
Starting subtest: flip-vs-absolute-wf_vblank
(kms_flip:1228) CRITICAL: Test assertion failure function check_state, file ../tests/kms_flip.c:531:
(kms_flip:1228) CRITICAL: Failed assertion: fabs((elapsed - expected) / expected) <= 0.005
(kms_flip:1228) CRITICAL: inconsistent vblank ts/seq: last 186.503342/4818, current 186.616776/4828: elapsed=113433.0us expected=110935.0us
Subtest flip-vs-absolute-wf_vblank failed.
Comment 1 CI Bug Log 2019-10-09 14:28:59 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@kms_flip@.*-wf_vblank - fail - Failed assertion: fabs((elapsed - expected) / expected) &lt;= 0.005
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3552/shard-tglb7/igt@kms_flip@flip-vs-blocking-wf-vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5217/shard-tglb1/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14703/shard-tglb1/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5218/shard-tglb2/igt@kms_flip@flip-vs-absolute-wf_vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7034/shard-tglb5/igt@kms_flip@flip-vs-absolute-wf_vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7034/shard-tglb6/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3553/shard-tglb6/igt@kms_flip@flip-vs-blocking-wf-vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7035/shard-tglb1/igt@kms_flip@flip-vs-absolute-wf_vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7032/re-tgl-u/igt@kms_flip@flip-vs-absolute-wf_vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7032/re-tgl-u/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7032/re-tgl-u/igt@kms_flip@flip-vs-blocking-wf-vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14706/shard-tglb1/igt@kms_flip@flip-vs-absolute-wf_vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5132/shard-tglb6/igt@kms_flip@flip-vs-blocking-wf-vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14711/shard-tglb4/igt@kms_flip@flip-vs-absolute-wf_vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7037/shard-tglb1/igt@kms_flip@flip-vs-absolute-wf_vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7037/shard-tglb6/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14712/shard-tglb3/igt@kms_flip@flip-vs-blocking-wf-vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14716/shard-tglb5/igt@kms_flip@flip-vs-blocking-wf-vblank.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7039/shard-tglb3/igt@kms_flip@flip-vs-absolute-wf_vblank.html
Comment 2 Caz.Yokoyama 2019-10-10 16:25:02 UTC
Expectation maybe too strict from the facts
- On TGL
- 14 / 25 runs (56.0%) of failure rate
- elapsed=113433.0us expected=110935.0us
Comment 3 CI Bug Log 2019-11-04 12:18:44 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: igt@kms_flip@.*-wf_vblank - fail - Failed assertion: fabs((elapsed - expected) / expected) &lt;= 0.005 -}
{+ ICL TGL: igt@kms_flip@.*-wf_vblank - fail - Failed assertion: fabs((elapsed - expected) / expected) &lt;= 0.005 +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_396/fi-icl-y/igt@kms_flip@wf_vblank-ts-check.html
Comment 4 CI Bug Log 2019-11-04 12:20:55 UTC
A CI Bug Log filter associated to this bug has been updated:

{- ICL TGL: igt@kms_flip@.*-wf_vblank - fail - Failed assertion: fabs((elapsed - expected) / expected) &lt;= 0.005 -}
{+ ICL TGL: igt@kms_flip@.*-wf_vblank - fail - Failed assertion: fabs((elapsed - expected) / expected) &lt;= 0.005 +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_396/fi-icl-y/igt@kms_flip@blocking-wf_vblank.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_396/fi-icl-y/igt@kms_flip@wf_vblank-ts-check-interruptible.html
Comment 5 CI Bug Log 2019-11-06 09:06:16 UTC
A CI Bug Log filter associated to this bug has been updated:

{- ICL TGL: igt@kms_flip@.*-wf_vblank - fail - Failed assertion: fabs((elapsed - expected) / expected) &lt;= 0.005 -}
{+ WHL ICL TGL: igt@kms_flip@.* - fail - Failed assertion: fabs((elapsed - expected) / expected) &lt;= 0.005 +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_397/fi-whl-u/igt@kms_flip@plain-flip-fb-recreate-interruptible.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_397/fi-whl-u/igt@kms_flip@basic-flip-vs-wf_vblank.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_397/fi-whl-u/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_397/fi-whl-u/igt@kms_flip@flip-vs-absolute-wf_vblank.html
Comment 6 Martin Peres 2019-11-29 19:38:34 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/488.

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.