Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ehl: Allow combo PHY A to drive a third external display (rev3)
HI, > -Original Message- > From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of > Matt Roper > Sent: keskiviikko 19. kesäkuuta 2019 21.31 > To: intel-gfx@lists.freedesktop.org > Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ehl: Allow combo > PHY A to > drive a third external display (rev3) > > On Wed, Jun 19, 2019 at 01:28:04PM +, Patchwork wrote: > > == Series Details == > > > > Series: drm/i915/ehl: Allow combo PHY A to drive a third external display > > (rev3) > > URL : https://patchwork.freedesktop.org/series/62131/ > > State : failure > > > > == Summary == > > > > CI Bug Log - changes from CI_DRM_6297_full -> Patchwork_13334_full > > > > > > Summary > > --- > > > > **FAILURE** > > > > Serious unknown changes coming with Patchwork_13334_full absolutely need > to be > > verified manually. > > > > If you think the reported changes have nothing to do with the changes > > introduced in Patchwork_13334_full, please notify your bug team to allow > them > > to document this new failure mode, which will reduce false positives in > > CI. > > > > > > > > Possible new issues > > --- > > > > Here are the unknown changes that may have been introduced in > Patchwork_13334_full: > > > > ### IGT changes ### > > > > Possible regressions > > > > * igt@runner@aborted: > > - shard-kbl: NOTRUN -> ([FAIL][1], [FAIL][2], [FAIL][3], > > [FAIL][4], [FAIL][5], > [FAIL][6], [FAIL][7]) ([fdo#108903] / [fdo#108904] / [fdo#108905] / > [fdo#110938]) > >[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard- > kbl4/igt@run...@aborted.html > >[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard- > kbl4/igt@run...@aborted.html > >[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard- > kbl4/igt@run...@aborted.html > >[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard- > kbl7/igt@run...@aborted.html > >[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard- > kbl4/igt@run...@aborted.html > >[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard- > kbl4/igt@run...@aborted.html > >[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard- > kbl4/igt@run...@aborted.html > > I'm not sure I understand what CI is saying here; link #4 here gives a > 404, and the other six links are all the same, but show empty boot/dmesg > logs. There are some fdo bug numbers reported here for known bugs, so I > guess those are what CI detected, even though the logfiles themselves > appear to be empty? It tries to say that each of these run none of the run was done as eg. https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/run33.log It seems that CI files are not sent. Anyway on this normally dmesg logs should tell that there has been kernel tainted and that is why no tests run on these runs...perhaps, Tomi, Martin? > > Anyway, whatever is going on with this KBL system doesn't appear to be > caused by my patch since I'm updating code that only runs on gen11 > platforms. > > The rest of the CI results look okay, so applied to dinq. Thanks Ville > for the review. > > > Matt > > > > > > > > Known issues > > > > > > Here are the changes found in Patchwork_13334_full that come from known > issues: > > > > ### IGT changes ### > > > > Issues hit > > > > * igt@gem_userptr_blits@map-fixed-invalidate-busy-gup: > > - shard-snb: [PASS][8] -> [DMESG-WARN][9] ([fdo#110913 ]) > >[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard- > snb5/igt@gem_userptr_bl...@map-fixed-invalidate-busy-gup.html > >[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard- > snb6/igt@gem_userptr_bl...@map-fixed-invalidate-busy-gup.html > > > > * igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy: > > - shard-kbl: [PASS][10] -> [DMESG-WARN][11] ([fdo#110913 ]) > >[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard- > kbl4/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html > >[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard- > kbl4/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html > > - shard-apl: [PASS][12] -> [DMESG-WARN][13] ([fdo#110913 ]) +2 > > similar > issues > >[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard- > apl8/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html > >[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard- > apl4/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html > > > > * igt@i915_selftest@live_evict: > > - shard-kbl: [PASS][14] -> [INCOMPLETE][15] ([fdo#103665] / > [fdo#110938]) > >[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard- > kbl6/igt@i915_selftest@live_evict.html > >[15]:
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ehl: Allow combo PHY A to drive a third external display (rev3)
On Wed, Jun 19, 2019 at 01:28:04PM +, Patchwork wrote: > == Series Details == > > Series: drm/i915/ehl: Allow combo PHY A to drive a third external display > (rev3) > URL : https://patchwork.freedesktop.org/series/62131/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_6297_full -> Patchwork_13334_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_13334_full absolutely need to > be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_13334_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_13334_full: > > ### IGT changes ### > > Possible regressions > > * igt@runner@aborted: > - shard-kbl: NOTRUN -> ([FAIL][1], [FAIL][2], [FAIL][3], > [FAIL][4], [FAIL][5], [FAIL][6], [FAIL][7]) ([fdo#108903] / [fdo#108904] / > [fdo#108905] / [fdo#110938]) >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@run...@aborted.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@run...@aborted.html >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@run...@aborted.html >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl7/igt@run...@aborted.html >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@run...@aborted.html >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@run...@aborted.html >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@run...@aborted.html I'm not sure I understand what CI is saying here; link #4 here gives a 404, and the other six links are all the same, but show empty boot/dmesg logs. There are some fdo bug numbers reported here for known bugs, so I guess those are what CI detected, even though the logfiles themselves appear to be empty? Anyway, whatever is going on with this KBL system doesn't appear to be caused by my patch since I'm updating code that only runs on gen11 platforms. The rest of the CI results look okay, so applied to dinq. Thanks Ville for the review. Matt > > > Known issues > > > Here are the changes found in Patchwork_13334_full that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_userptr_blits@map-fixed-invalidate-busy-gup: > - shard-snb: [PASS][8] -> [DMESG-WARN][9] ([fdo#110913 ]) >[8]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-snb5/igt@gem_userptr_bl...@map-fixed-invalidate-busy-gup.html >[9]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-snb6/igt@gem_userptr_bl...@map-fixed-invalidate-busy-gup.html > > * igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy: > - shard-kbl: [PASS][10] -> [DMESG-WARN][11] ([fdo#110913 ]) >[10]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-kbl4/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html >[11]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html > - shard-apl: [PASS][12] -> [DMESG-WARN][13] ([fdo#110913 ]) +2 > similar issues >[12]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-apl8/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html >[13]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-apl4/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html > > * igt@i915_selftest@live_evict: > - shard-kbl: [PASS][14] -> [INCOMPLETE][15] ([fdo#103665] / > [fdo#110938]) >[14]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-kbl6/igt@i915_selftest@live_evict.html >[15]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl7/igt@i915_selftest@live_evict.html > > * igt@i915_suspend@sysfs-reader: > - shard-apl: [PASS][16] -> [DMESG-WARN][17] ([fdo#108566]) >[16]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-apl6/igt@i915_susp...@sysfs-reader.html >[17]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-apl3/igt@i915_susp...@sysfs-reader.html > > * igt@kms_cursor_crc@pipe-b-cursor-64x21-sliding: > - shard-kbl: [PASS][18] -> [FAIL][19] ([fdo#103232]) >[18]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-kbl1/igt@kms_cursor_...@pipe-b-cursor-64x21-sliding.html >[19]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl2/igt@kms_cursor_...@pipe-b-cursor-64x21-sliding.html > > *
[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ehl: Allow combo PHY A to drive a third external display (rev3)
== Series Details == Series: drm/i915/ehl: Allow combo PHY A to drive a third external display (rev3) URL : https://patchwork.freedesktop.org/series/62131/ State : failure == Summary == CI Bug Log - changes from CI_DRM_6297_full -> Patchwork_13334_full Summary --- **FAILURE** Serious unknown changes coming with Patchwork_13334_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_13334_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Possible new issues --- Here are the unknown changes that may have been introduced in Patchwork_13334_full: ### IGT changes ### Possible regressions * igt@runner@aborted: - shard-kbl: NOTRUN -> ([FAIL][1], [FAIL][2], [FAIL][3], [FAIL][4], [FAIL][5], [FAIL][6], [FAIL][7]) ([fdo#108903] / [fdo#108904] / [fdo#108905] / [fdo#110938]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@run...@aborted.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@run...@aborted.html [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@run...@aborted.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl7/igt@run...@aborted.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@run...@aborted.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@run...@aborted.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@run...@aborted.html Known issues Here are the changes found in Patchwork_13334_full that come from known issues: ### IGT changes ### Issues hit * igt@gem_userptr_blits@map-fixed-invalidate-busy-gup: - shard-snb: [PASS][8] -> [DMESG-WARN][9] ([fdo#110913 ]) [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-snb5/igt@gem_userptr_bl...@map-fixed-invalidate-busy-gup.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-snb6/igt@gem_userptr_bl...@map-fixed-invalidate-busy-gup.html * igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy: - shard-kbl: [PASS][10] -> [DMESG-WARN][11] ([fdo#110913 ]) [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-kbl4/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl4/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html - shard-apl: [PASS][12] -> [DMESG-WARN][13] ([fdo#110913 ]) +2 similar issues [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-apl8/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-apl4/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html * igt@i915_selftest@live_evict: - shard-kbl: [PASS][14] -> [INCOMPLETE][15] ([fdo#103665] / [fdo#110938]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-kbl6/igt@i915_selftest@live_evict.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl7/igt@i915_selftest@live_evict.html * igt@i915_suspend@sysfs-reader: - shard-apl: [PASS][16] -> [DMESG-WARN][17] ([fdo#108566]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-apl6/igt@i915_susp...@sysfs-reader.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-apl3/igt@i915_susp...@sysfs-reader.html * igt@kms_cursor_crc@pipe-b-cursor-64x21-sliding: - shard-kbl: [PASS][18] -> [FAIL][19] ([fdo#103232]) [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-kbl1/igt@kms_cursor_...@pipe-b-cursor-64x21-sliding.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-kbl2/igt@kms_cursor_...@pipe-b-cursor-64x21-sliding.html * igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic: - shard-hsw: [PASS][20] -> [FAIL][21] ([fdo#105767]) [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-hsw2/igt@kms_cursor_leg...@2x-long-cursor-vs-flip-atomic.html [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-hsw4/igt@kms_cursor_leg...@2x-long-cursor-vs-flip-atomic.html * igt@kms_draw_crc@draw-method-xrgb2101010-mmap-gtt-ytiled: - shard-skl: [PASS][22] -> [FAIL][23] ([fdo#103184] / [fdo#103232]) [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6297/shard-skl4/igt@kms_draw_...@draw-method-xrgb2101010-mmap-gtt-ytiled.html [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13334/shard-skl4/igt@kms_draw_...@draw-method-xrgb2101010-mmap-gtt-ytiled.html * igt@kms_flip@2x-plain-flip: -
