Bug 109225 - [CI][DRMTIP] igt@kms_atomic_transition@plane-all-modeset-transition* - fail - Last errno: 28, No space left on device
Summary: [CI][DRMTIP] igt@kms_atomic_transition@plane-all-modeset-transition* - fail -...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-04 14:11 UTC by Martin Peres
Modified: 2019-01-04 14:12 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2019-01-04 14:11:59 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_168/fi-skl-6700k2/igt@kms_atomic_transition@plane-all-modeset-transition.html

Starting subtest: plane-all-modeset-transition
(kms_atomic_transition:1188) igt_kms-CRITICAL: Test assertion failure function do_display_commit, file ../lib/igt_kms.c:3320:
(kms_atomic_transition:1188) igt_kms-CRITICAL: Failed assertion: ret == 0
(kms_atomic_transition:1188) igt_kms-CRITICAL: Last errno: 28, No space left on device
(kms_atomic_transition:1188) igt_kms-CRITICAL: error: -28 != 0
Subtest plane-all-modeset-transition failed.
Comment 1 CI Bug Log 2019-01-04 14:12:59 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL: igt@kms_atomic_transition@plane-all-modeset-transition* - fail - Last errno: 28, No space left on device
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_11112/shard-kbl7/igt@kms_atomic_transition@plane-all-transition-nonblocking.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_174/fi-skl-6700k2/igt@kms_atomic_transition@plane-all-transition-nonblocking.html


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.