From: "Souza, Jose" <jose.souza@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Kasireddy, Vivek" <vivek.kasireddy@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dsi: Dont forget to clean up the connector on error (rev3)
Date: Tue, 2 Jun 2020 15:35:12 +0000 [thread overview]
Message-ID: <daf59c43f1a1b8c11bb53e2fd4a3583cd52b6cfc.camel@intel.com> (raw)
In-Reply-To: <159109693008.21427.10089451260181328056@emeril.freedesktop.org>
On Tue, 2020-06-02 at 11:22 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/dsi: Dont forget to clean up the connector on error (rev3)
> URL : https://patchwork.freedesktop.org/series/77011/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_8568_full -> Patchwork_17838_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_17838_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_17838_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_17838_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@gem_exec_reloc@basic-cpu-read:
> - shard-skl: [PASS][1] -> [TIMEOUT][2] +2 similar issues
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-skl5/igt@gem_exec_reloc@basic-cpu-read.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-skl9/igt@gem_exec_reloc@basic-cpu-read.html
>
> * igt@kms_plane_multiple@atomic-pipe-b-tiling-none:
> - shard-iclb: [PASS][3] -> [FAIL][4]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-iclb6/igt@kms_plane_multiple@atomic-pipe-b-tiling-none.html
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-iclb1/igt@kms_plane_multiple@atomic-pipe-b-tiling-none.html
>
>
Not related to this changes.
Pushed to dinq, thanks for the patch.
>
> Known issues
> ------------
>
> Here are the changes found in Patchwork_17838_full that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes:
> - shard-apl: [PASS][5] -> [DMESG-WARN][6] ([i915#180]) +3 similar issues
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-apl7/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes.html
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-apl4/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes.html
> - shard-skl: [PASS][7] -> [INCOMPLETE][8] ([i915#648] / [i915#69])
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-skl9/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes.html
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-skl6/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes.html
>
> * igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
> - shard-skl: [PASS][9] -> [FAIL][10] ([fdo#108145] / [i915#265]) +1 similar issue
> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-skl5/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-skl4/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
>
> * igt@kms_psr@psr2_cursor_render:
> - shard-iclb: [PASS][11] -> [SKIP][12] ([fdo#109441]) +1 similar issue
> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-iclb2/igt@kms_psr@psr2_cursor_render.html
> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-iclb5/igt@kms_psr@psr2_cursor_render.html
>
> * igt@kms_vblank@pipe-c-wait-idle-hang:
> - shard-apl: [PASS][13] -> [TIMEOUT][14] ([i915#1635]) +2 similar issues
> [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-apl8/igt@kms_vblank@pipe-c-wait-idle-hang.html
> [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-apl6/igt@kms_vblank@pipe-c-wait-idle-hang.html
>
>
> #### Possible fixes ####
>
> * {igt@gem_exec_schedule@implicit-write-read@rcs0}:
> - shard-snb: [INCOMPLETE][15] ([i915#82]) -> [PASS][16]
> [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-snb6/igt@gem_exec_schedule@implicit-write-read@rcs0.html
> [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-snb5/igt@gem_exec_schedule@implicit-write-read@rcs0.html
>
> * igt@gem_workarounds@suspend-resume-fd:
> - shard-apl: [INCOMPLETE][17] -> [PASS][18]
> [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-apl8/igt@gem_workarounds@suspend-resume-fd.html
> [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-apl6/igt@gem_workarounds@suspend-resume-fd.html
>
> * {igt@kms_flip@flip-vs-suspend@a-dp1}:
> - shard-apl: [DMESG-WARN][19] ([i915#180]) -> [PASS][20] +3 similar issues
> [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-apl1/igt@kms_flip@flip-vs-suspend@a-dp1.html
> [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-apl7/igt@kms_flip@flip-vs-suspend@a-dp1.html
>
> * {igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1}:
> - shard-skl: [FAIL][21] ([i915#1928]) -> [PASS][22]
> [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-skl5/igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1.html
> [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-skl9/igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1.html
>
> * igt@kms_hdr@bpc-switch-dpms:
> - shard-skl: [FAIL][23] ([i915#1188]) -> [PASS][24] +1 similar issue
> [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-skl7/igt@kms_hdr@bpc-switch-dpms.html
> [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-skl2/igt@kms_hdr@bpc-switch-dpms.html
>
> * igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
> - shard-skl: [FAIL][25] ([fdo#108145] / [i915#265]) -> [PASS][26]
> [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-skl3/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html
> [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-skl3/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html
>
> * igt@kms_psr@no_drrs:
> - shard-iclb: [FAIL][27] ([i915#173]) -> [PASS][28]
> [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-iclb1/igt@kms_psr@no_drrs.html
> [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-iclb8/igt@kms_psr@no_drrs.html
>
> * igt@kms_psr@psr2_primary_mmap_cpu:
> - shard-iclb: [SKIP][29] ([fdo#109441]) -> [PASS][30] +2 similar issues
> [29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-iclb6/igt@kms_psr@psr2_primary_mmap_cpu.html
> [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
>
> * igt@kms_vblank@pipe-a-ts-continuation-suspend:
> - shard-kbl: [DMESG-WARN][31] ([i915#180]) -> [PASS][32] +1 similar issue
> [31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-kbl1/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
> [32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
> - shard-skl: [INCOMPLETE][33] ([i915#69]) -> [PASS][34] +1 similar issue
> [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-skl3/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
> [34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-skl10/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
>
>
> #### Warnings ####
>
> * igt@i915_pm_dc@dc6-psr:
> - shard-tglb: [SKIP][35] ([i915#468]) -> [FAIL][36] ([i915#1899])
> [35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-tglb2/igt@i915_pm_dc@dc6-psr.html
> [36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-tglb3/igt@i915_pm_dc@dc6-psr.html
>
> * igt@kms_content_protection@atomic-dpms:
> - shard-apl: [TIMEOUT][37] ([i915#1319] / [i915#1635]) -> [TIMEOUT][38] ([i915#1319])
> [37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-apl8/igt@kms_content_protection@atomic-dpms.html
> [38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-apl6/igt@kms_content_protection@atomic-dpms.html
>
> * igt@kms_content_protection@srm:
> - shard-apl: [FAIL][39] ([fdo#110321]) -> [TIMEOUT][40] ([i915#1319] / [i915#1635])
> [39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-apl4/igt@kms_content_protection@srm.html
> [40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-apl1/igt@kms_content_protection@srm.html
>
> * igt@kms_cursor_legacy@cursora-vs-flipb-toggle:
> - shard-glk: [DMESG-WARN][41] ([i915#1926]) -> [DMESG-FAIL][42] ([i915#1925] / [i915#1926])
> [41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-glk4/igt@kms_cursor_legacy@cursora-vs-flipb-toggle.html
> [42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-glk4/igt@kms_cursor_legacy@cursora-vs-flipb-toggle.html
>
> * igt@kms_cursor_legacy@cursorb-vs-flipa-toggle:
> - shard-glk: [DMESG-WARN][43] ([i915#1926]) -> [DMESG-WARN][44] ([i915#1927])
> [43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-glk9/igt@kms_cursor_legacy@cursorb-vs-flipa-toggle.html
> [44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-glk9/igt@kms_cursor_legacy@cursorb-vs-flipa-toggle.html
>
> * igt@kms_fbcon_fbt@fbc:
> - shard-apl: [FAIL][45] ([i915#1525] / [i915#95]) -> [FAIL][46] ([i915#1525])
> [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8568/shard-apl6/igt@kms_fbcon_fbt@fbc.html
> [46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/shard-apl8/igt@kms_fbcon_fbt@fbc.html
>
>
> {name}: This element is suppressed. This means it is ignored when computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
> [fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
> [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
> [fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
> [i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
> [i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
> [i915#1525]: https://gitlab.freedesktop.org/drm/intel/issues/1525
> [i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
> [i915#173]: https://gitlab.freedesktop.org/drm/intel/issues/173
> [i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
> [i915#1899]: https://gitlab.freedesktop.org/drm/intel/issues/1899
> [i915#1925]: https://gitlab.freedesktop.org/drm/intel/issues/1925
> [i915#1926]: https://gitlab.freedesktop.org/drm/intel/issues/1926
> [i915#1927]: https://gitlab.freedesktop.org/drm/intel/issues/1927
> [i915#1928]: https://gitlab.freedesktop.org/drm/intel/issues/1928
> [i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
> [i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
> [i915#468]: https://gitlab.freedesktop.org/drm/intel/issues/468
> [i915#648]: https://gitlab.freedesktop.org/drm/intel/issues/648
> [i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69
> [i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
> [i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
>
>
> Participating hosts (11 -> 11)
> ------------------------------
>
> No changes in participating hosts
>
>
> Build changes
> -------------
>
> * Linux: CI_DRM_8568 -> Patchwork_17838
>
> CI-20190529: 20190529
> CI_DRM_8568: 124bafc80c3ce62fc61b8eabb2657c87424b999b @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_5690: bea881189520a9cccbb1c1cb454ac5b6fdaea40e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_17838: a30b3a0e479eb9f2f48cf8a737656c9bbb64c15a @ git://anongit.freedesktop.org/gfx-ci/linux
> piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17838/index.html
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-06-02 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 1:01 [Intel-gfx] [PATCH] drm/i915/dsi: Dont forget to clean up the connector on error Vivek Kasireddy
2020-05-07 1:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-05-07 4:30 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-05-22 20:26 ` [Intel-gfx] [PATCH] drm/i915/dsi: Dont forget to clean up the connector on error (v2) Vivek Kasireddy
2020-06-02 15:33 ` Souza, Jose
2020-05-22 21:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dsi: Dont forget to clean up the connector on error (rev2) Patchwork
2020-05-23 8:42 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-06-02 3:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dsi: Dont forget to clean up the connector on error (rev3) Patchwork
2020-06-02 11:22 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-06-02 15:35 ` Souza, Jose [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=daf59c43f1a1b8c11bb53e2fd4a3583cd52b6cfc.camel@intel.com \
--to=jose.souza@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vivek.kasireddy@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).