Bug 112263 - [CI][RESUME]igt@kms_setmode@invalid-clone-single-crtc-stealing - fail - Failed assertion: ret == 0, error: -22 != 0
Summary: [CI][RESUME]igt@kms_setmode@invalid-clone-single-crtc-stealing - fail - Faile...
Status: RESOLVED MOVED
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-11-13 11:13 UTC by Lakshmi
Modified: 2019-11-29 19:47 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Lakshmi 2019-11-13 11:13:50 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7303/re-tgl-u/igt@kms_setmode@invalid-clone-single-crtc-stealing.html
Starting subtest: invalid-clone-single-crtc-stealing
(kms_setmode:1215) CRITICAL: Test assertion failure function test_stealing, file ../tests/kms_setmode.c:401:
(kms_setmode:1215) CRITICAL: Failed assertion: ret == 0
(kms_setmode:1215) CRITICAL: Last errno: 22, Invalid argument
(kms_setmode:1215) CRITICAL: error: -22 != 0
Subtest invalid-clone-single-crtc-stealing failed.
Comment 1 CI Bug Log 2019-11-13 11:17:00 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@kms_setmode@invalid-clone-single-crtc-stealing - fail - Failed assertion: ret == 0, error: -22 != 0
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7303/re-tgl-u/igt@kms_setmode@invalid-clone-single-crtc-stealing.html
Comment 2 Martin Peres 2019-11-29 19:47:10 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/594.


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.