Bug 110569

Summary:	[CI][DRMTIP] igt@kms_ccs@pipe-c-crc-sprite-planes-basic - skip - Test requirement: valid_tests
Product:	DRI	Reporter:	Martin Peres <martin.peres>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	medium	CC:	intel-gfx-bugs
Version:	XOrg git
Hardware:	Other
OS:	All
Whiteboard:	ReadyForDev
i915 platform:	CFL	i915 features:	display/Other

Description Martin Peres 2019-04-30 12:30:13 UTC

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_267/fi-cml-u/igt@kms_ccs@pipe-c-crc-sprite-planes-basic.html

Starting subtest: pipe-C-crc-sprite-planes-basic
Test requirement not met in function __real_main327, file ../tests/kms_ccs.c:374:
Test requirement: valid_tests
Subtest pipe-C-crc-sprite-planes-basic: SKIP (0.291s)

Comment 1 CI Bug Log 2019-04-30 12:31:28 UTC

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

### New filters associated

* fi-cml-u re-cml-u: igt@kms_ccs@pipe-c-crc-sprite-planes-basic - skip - Test requirement: valid_tests
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_267/fi-cml-u/igt@kms_ccs@pipe-c-crc-sprite-planes-basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_268/fi-cml-u/igt@kms_ccs@pipe-c-crc-sprite-planes-basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_269/fi-cml-u/igt@kms_ccs@pipe-c-crc-sprite-planes-basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-cml-u/igt@kms_ccs@pipe-c-crc-sprite-planes-basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6010/re-cml-u/igt@kms_ccs@pipe-c-crc-sprite-planes-basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6012/re-cml-u/igt@kms_ccs@pipe-c-crc-sprite-planes-basic.html

Comment 2 Arek Hiler 2019-08-06 10:11:09 UTC

Same as the other bug that was skipping on on test_output(), unified in a single bug now.

*** This bug has been marked as a duplicate of bug 111304 ***

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.