Bug 100339 - [many][EXT] igt@kms_flip tests incomplete in CI
Summary: [many][EXT] igt@kms_flip tests incomplete in CI
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 100318
  Show dependency treegraph
 
Reported: 2017-03-22 17:17 UTC by Jani Saarinen
Modified: 2017-05-16 15:38 UTC (History)
1 user (show)

See Also:
i915 platform: BDW, BXT, BYT
i915 features: display/Other


Attachments

Description Jani Saarinen 2017-03-22 17:17:53 UTC
On Extended:
igt@kms_flip@vblank-vs-dpms-suspend-interruptible
igt@kms_flip@2x-wf_vblank-interruptible
igt@kms_flip@vblank-vs-dpms-suspend
igt@kms_flip@flip-vs-rmfb
igt@kms_flip@2x-render-flip-vs-dpms
igt@kms_flip@2x-render-flip-vs-modeset
igt@kms_flip@2x-render-flip-vs-modeset-interruptible
igt@kms_flip@2x-vblank-vs-suspend-interruptible
igt@kms_flip@2x-wf_vblank-ts-check-interruptible
igt@kms_flip@busy-flip-interruptible
igt@kms_flip@render-flip-vs-modeset
igt@kms_flip@render-flip-vs-modeset-interruptible
igt@kms_flip@render-flip-vs-panning
igt@kms_flip@vblank-vs-dpms-rpm-interruptible
igt@kms_flip@vblank-vs-modeset-rpm-interruptible
igt@kms_flip@vblank-vs-modeset-suspend
igt@kms_flip@vblank-vs-modeset-suspend-interruptible
igt@kms_flip@vblank-vs-suspend
igt@kms_flip@wf_vblank-ts-check-interruptible
igt@kms_flip_tiling@flip-to-x-tiled

incomplete

Eg: http://intel-gfx-ci.fi.intel.com/archive/results/CI_IGT_test/igt@kms_flip@vblank-vs-dpms-suspend-interruptible.html
Comment 1 Mika Kahola 2017-03-23 08:51:39 UTC
For bug on igt@kms_flip_tiling@flip-to-x-tiled there seems to be a duplicate bug defined

https://bugs.freedesktop.org/show_bug.cgi?id=92474
Comment 2 Chris Wilson 2017-05-03 13:33:13 UTC
Assuming that these incompletes were the irq bugs fixed about the same time as these were filed.


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.