AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Wentland <hwentlan@amd.com>
To: "Zuo, Jerry" <Jerry.Zuo@amd.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Wentland, Harry" <Harry.Wentland@amd.com>,
	"Siqueira, Rodrigo" <Rodrigo.Siqueira@amd.com>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for drm: Add support for DP 1.4 Compliance edid corruption test (rev3)
Date: Fri, 20 Dec 2019 14:52:34 -0500	[thread overview]
Message-ID: <ab9e0ea3-b7cf-97d9-d964-9c9c7ecd1e4d@amd.com> (raw)
In-Reply-To: <DM5PR12MB1705E1910E9D23B47F216B5DE52D0@DM5PR12MB1705.namprd12.prod.outlook.com>

On 2019-12-20 2:40 p.m., Zuo, Jerry wrote:
> Hi All:
> 
>     I got CI check failures. Among those, hdmi-hpd-fast seems related, but I am not sure why. Please take a brief review and help to determine if it is a real false-positive again. 
> 

It looks like the hdmi-hpd-fast failures are listed under "Known
issues." I imagine that means we can ignore them.

But we also see these failures that are list as "Possible regressions"
and I'm not sure why our patch would've broken those:

#### Possible regressions ####

  * igt@gem_ctx_create@basic-files:
    - fi-byt-j1900:       [PASS][1] -> [FAIL][2]
   [1]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-byt-j1900/igt@gem_ctx_create@basic-files.html
   [2]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-byt-j1900/igt@gem_ctx_create@basic-files.html

  * igt@i915_selftest@live_gt_heartbeat:
    - fi-whl-u:           [PASS][3] -> [DMESG-FAIL][4]
   [3]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-whl-u/igt@i915_selftest@live_gt_heartbeat.html
   [4]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-whl-u/igt@i915_selftest@live_gt_heartbeat.html

Would love some input from Intel guys on this as we don't want to break
you with this patch.

Thanks,
Harry

>     Thanks a lot.
> 
> Regards,
> Jerry
> 
> -----Original Message-----
> From: Patchwork <patchwork@emeril.freedesktop.org> 
> Sent: December 9, 2019 4:40 PM
> To: Zuo, Jerry <Jerry.Zuo@amd.com>
> Cc: intel-gfx@lists.freedesktop.org
> Subject: ✗ Fi.CI.BAT: failure for drm: Add support for DP 1.4 Compliance edid corruption test (rev3)
> 
> == Series Details ==
> 
> Series: drm: Add support for DP 1.4 Compliance edid corruption test (rev3)
> URL   : https://patchwork.freedesktop.org/series/70530/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_7522 -> Patchwork_15658 ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with Patchwork_15658 absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_15658, please notify your bug team to allow them
>   to document this new failure mode, which will reduce false positives in CI.
> 
>   External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/index.html
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in Patchwork_15658:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@gem_ctx_create@basic-files:
>     - fi-byt-j1900:       [PASS][1] -> [FAIL][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-byt-j1900/igt@gem_ctx_create@basic-files.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-byt-j1900/igt@gem_ctx_create@basic-files.html
> 
>   * igt@i915_selftest@live_gt_heartbeat:
>     - fi-whl-u:           [PASS][3] -> [DMESG-FAIL][4]
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-whl-u/igt@i915_selftest@live_gt_heartbeat.html
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-whl-u/igt@i915_selftest@live_gt_heartbeat.html
> 
>   
> Known issues
> ------------
> 
>   Here are the changes found in Patchwork_15658 that come from known issues:
> 
> ### IGT changes ###
> 
> #### Issues hit ####
> 
>   * igt@i915_selftest@live_blt:
>     - fi-ivb-3770:        [PASS][5] -> [DMESG-FAIL][6] ([i915#725])
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-ivb-3770/igt@i915_selftest@live_blt.html
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-ivb-3770/igt@i915_selftest@live_blt.html
>     - fi-hsw-4770:        [PASS][7] -> [DMESG-FAIL][8] ([i915#725])
>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-hsw-4770/igt@i915_selftest@live_blt.html
>    [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-hsw-4770/igt@i915_selftest@live_blt.html
> 
>   * igt@kms_chamelium@hdmi-hpd-fast:
>     - fi-kbl-7500u:       [PASS][9] -> [FAIL][10] ([fdo#111096] / [i915#323])
>    [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
>    [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
> 
>   
> #### Possible fixes ####
> 
>   * igt@gem_exec_parallel@basic:
>     - {fi-tgl-u}:         [INCOMPLETE][11] ([i915#476]) -> [PASS][12]
>    [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-tgl-u/igt@gem_exec_parallel@basic.html
>    [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-tgl-u/igt@gem_exec_parallel@basic.html
> 
>   * igt@gem_sync@basic-store-each:
>     - fi-tgl-y:           [INCOMPLETE][13] ([i915#435]) -> [PASS][14]
>    [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-tgl-y/igt@gem_sync@basic-store-each.html
>    [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-tgl-y/igt@gem_sync@basic-store-each.html
> 
>   * igt@i915_selftest@live_gem_contexts:
>     - fi-hsw-peppy:       [INCOMPLETE][15] ([i915#694]) -> [PASS][16]
>    [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-hsw-peppy/igt@i915_selftest@live_gem_contexts.html
>    [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-hsw-peppy/igt@i915_selftest@live_gem_contexts.html
> 
>   
> #### Warnings ####
> 
>   * igt@i915_selftest@live_blt:
>     - fi-hsw-4770r:       [DMESG-FAIL][17] ([i915#553] / [i915#725]) -> [DMESG-FAIL][18] ([i915#725])
>    [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-hsw-4770r/igt@i915_selftest@live_blt.html
>    [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-hsw-4770r/igt@i915_selftest@live_blt.html
> 
>   * igt@i915_selftest@live_gem_contexts:
>     - fi-byt-j1900:       [DMESG-FAIL][19] ([i915#722]) -> [INCOMPLETE][20] ([i915#45])
>    [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-byt-j1900/igt@i915_selftest@live_gem_contexts.html
>    [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-byt-j1900/igt@i915_selftest@live_gem_contexts.html
> 
>   * igt@kms_cursor_legacy@basic-flip-after-cursor-atomic:
>     - fi-kbl-x1275:       [DMESG-WARN][21] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][22] ([i915#62] / [i915#92]) +2 similar issues
>    [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-kbl-x1275/igt@kms_cursor_legacy@basic-flip-after-cursor-atomic.html
>    [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-kbl-x1275/igt@kms_cursor_legacy@basic-flip-after-cursor-atomic.html
> 
>   * igt@kms_flip@basic-flip-vs-modeset:
>     - fi-kbl-x1275:       [DMESG-WARN][23] ([i915#62] / [i915#92]) -> [DMESG-WARN][24] ([i915#62] / [i915#92] / [i915#95]) +4 similar issues
>    [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7522/fi-kbl-x1275/igt@kms_flip@basic-flip-vs-modeset.html
>    [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/fi-kbl-x1275/igt@kms_flip@basic-flip-vs-modeset.html
> 
>   
>   {name}: This element is suppressed. This means it is ignored when computing
>           the status of the difference (SUCCESS, WARNING, or FAILURE).
> 
>   [fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
>   [i915#323]: https://gitlab.freedesktop.org/drm/intel/issues/323
>   [i915#435]: https://gitlab.freedesktop.org/drm/intel/issues/435
>   [i915#45]: https://gitlab.freedesktop.org/drm/intel/issues/45
>   [i915#476]: https://gitlab.freedesktop.org/drm/intel/issues/476
>   [i915#553]: https://gitlab.freedesktop.org/drm/intel/issues/553
>   [i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
>   [i915#694]: https://gitlab.freedesktop.org/drm/intel/issues/694
>   [i915#707]: https://gitlab.freedesktop.org/drm/intel/issues/707
>   [i915#722]: https://gitlab.freedesktop.org/drm/intel/issues/722
>   [i915#725]: https://gitlab.freedesktop.org/drm/intel/issues/725
>   [i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
>   [i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
> 
> 
> Participating hosts (52 -> 47)
> ------------------------------
> 
>   Missing    (5): fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper 
> 
> 
> Build changes
> -------------
> 
>   * CI: CI-20190529 -> None
>   * Linux: CI_DRM_7522 -> Patchwork_15658
> 
>   CI-20190529: 20190529
>   CI_DRM_7522: 75dcdef38ab3cf24b27ccf29d5aeac201d616e76 @ git://anongit.freedesktop.org/gfx-ci/linux
>   IGT_5341: 5fe683cdebde2d77d16ffc42c9fdf29a9f95bb82 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
>   Patchwork_15658: 96a36e9a97da56fdac55dad89998257680b12200 @ git://anongit.freedesktop.org/gfx-ci/linux
> 
> 
> == Linux commits ==
> 
> 96a36e9a97da drm: Add support for DP 1.4 Compliance edid corruption test
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15658/index.html
> 
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      reply	other threads:[~2019-12-20 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09 20:04 [PATCH V4] drm: Add support for DP 1.4 Compliance edid corruption test Jerry (Fangzhi) Zuo
     [not found] ` <157592762919.14781.11113643286290066958@emeril.freedesktop.org>
2019-12-20 19:40   ` ✗ Fi.CI.BAT: failure for drm: Add support for DP 1.4 Compliance edid corruption test (rev3) Zuo, Jerry
2019-12-20 19:52     ` Harry Wentland [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=ab9e0ea3-b7cf-97d9-d964-9c9c7ecd1e4d@amd.com \
    --to=hwentlan@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Harry.Wentland@amd.com \
    --cc=Jerry.Zuo@amd.com \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=ville.syrjala@linux.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