[Bug 101916] [IGT] kms_* fail in some subtest Failed assertion: ret == 0...

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=101916

Hector Velazquez <hector.franciscox.velazquez.suriano at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      i915 platform|BXT, CFL, CNL, GLK          |

--- Comment #15 from Hector Velazquez <hector.franciscox.velazquez.suriano at intel.com> ---
This tests continue failing on IVB QA 

Tests List:
igt at kms_panel_fitting@legacy

output sample:
(kms_panel_fitting:19195) igt-kms-CRITICAL: Test assertion failure function
igt_drm_plane_commit, file igt_kms.c:2355:
(kms_panel_fitting:19195) igt-kms-CRITICAL: Failed assertion: ret == 0
(kms_panel_fitting:19195) igt-kms-CRITICAL: Last errno: 22, Invalid argument
(kms_panel_fitting:19195) igt-kms-CRITICAL: error: -22 != 0
Subtest legacy failed.

This tests has skipped on IVB QA 
Tests List:
igt at kms_plane_scaling@(all subtests)


This tests has skipped on GLK/CFL QA 
Tests List:
igt at kms_ccs@pipe-C-crc-primary-basic 
igt at kms_ccs@pipe-C-crc-primary-rotation-180
igt at kms_atomic_transition@plane-all-modeset-transition-internal-panels

This tests has pass successfully on GLK/CFL QA 
Tests List:
igt at kms_vblank@query-busy
igt at kms_plane@plane-position-covered-pipe-B-planes
igt at kms_pipe_crc_basic@nonblocking-crc-pipe-B-frame-sequence
igt at kms_mmap_write_crc
igt at kms_atomic_transition@plane-all-modeset-transition

software:
IGT-Version: 1.21-g1fb30f1 (x86_64) (Linux:
4.16.0-rc2-drm-intel-qa-ww8-commit-562dc33+ x86_64)

(removing BXT/CNL/CFL/GLK from the platform list, verified as fixed in last
executions on BXT/CNL/CFL/GLK)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180228/50584572/attachment.html>