Bug 112059 - [CI][SHARDS] igt@kms_flip@flip-vs-blocking-wf-vblank - fail - Failed assertion: elapsed >= min && elapsed <= max
Summary: [CI][SHARDS] igt@kms_flip@flip-vs-blocking-wf-vblank - fail - Failed assertio...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: high major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-18 12:22 UTC by Lakshmi
Modified: 2019-11-29 19:42 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features: display/Other

Attachments

Description Lakshmi 2019-10-18 12:22:53 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7125/shard-skl9/igt@kms_flip@flip-vs-blocking-wf-vblank.html
Starting subtest: flip-vs-blocking-wf-vblank
(kms_flip:1016) CRITICAL: Test assertion failure function check_final_state, file ../tests/kms_flip.c:1002:
(kms_flip:1016) CRITICAL: Failed assertion: elapsed >= min && elapsed <= max
(kms_flip:1016) CRITICAL: dropped frames, expected 601, counted 600, encoder type 2
Subtest flip-vs-blocking-wf-vblank failed.
Comment 1 CI Bug Log 2019-10-18 12:23:53 UTC 
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL: igt@kms_flip@flip-vs-blocking-wf-vblank - fail - Failed assertion: elapsed &gt;= min &amp;&amp; elapsed &lt;= max
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7125/shard-skl9/igt@kms_flip@flip-vs-blocking-wf-vblank.html
Comment 2 Caz.Yokoyama 2019-10-21 15:24:38 UTC 
set to high/major because of SKL.
Comment 3 Martin Peres 2019-11-29 19:42:01 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/527.

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.