Bug 112009 - [CI][BAT] igt@kms_cursor_crc@pipe-d-cursor-64x21-sliding - skip - Test requirement: pipe < display->n_pipes, SKIP
Summary: [CI][BAT] igt@kms_cursor_crc@pipe-d-cursor-64x21-sliding - skip - Test requir...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-15 06:42 UTC by Lakshmi
Modified: 2019-10-15 06:44 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-10-15 06:42:47 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3568/shard-iclb3/igt@kms_cursor_crc@pipe-d-cursor-64x21-sliding.html
Test requirement not met in function run_tests_on_pipe, file ../tests/kms_cursor_crc.c:648:
Test requirement: w <= data->cursor_max_w && h <= data->cursor_max_h
Test requirement not met in function run_tests_on_pipe, file ../tests/kms_cursor_crc.c:648:
Test requirement: w <= data->cursor_max_w && h <= data->cursor_max_h
Test requirement not met in function run_tests_on_pipe, file ../tests/kms_cursor_crc.c:648:
Test requirement: w <= data->cursor_max_w && h <= data->cursor_max_h
Test requirement not met in function igt_get_single_output_for_pipe, file ../lib/igt_kms.c:2505:
Test requirement: pipe < display->n_pipes
Subtest pipe-D-cursor-64x21-sliding: SKIP
Test requirement not met in function igt_get_single_output_for_pipe, file ../lib/igt_kms.c:2505:
Test requirement: pipe < display->n_pipes
Test requirement not met in function igt_get_single_output_for_pipe, file ../lib/igt_kms.c:2505:
Test requirement: pipe < display->n_pipes
Comment 1 Lakshmi 2019-10-15 06:44:19 UTC
Update for myself: Create a CI bug log filter.


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.