From: "Souza, Jose" <jose.souza@intel.com>
To: "natechancellor@gmail.com" <natechancellor@gmail.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/display: Ensure that ret is always initialized in icl_combo_phy_verify_state
Date: Tue, 28 Jul 2020 01:47:56 +0000 [thread overview]
Message-ID: <74694924dbd548db634148b9ee8eaed2fc738f3f.camel@intel.com> (raw)
In-Reply-To: <159487600890.25374.16029833195632024587@emeril.freedesktop.org>
Hi Nathan
Are you planning to check this regressions and send another version with the fix?Or can I do it on top of your patch?
On Thu, 2020-07-16 at 05:06 +0000, Patchwork wrote:
> Patch Details
> Series: drm/i915/display: Ensure that ret is always initialized in icl_combo_phy_verify_state
> URL: https://patchwork.freedesktop.org/series/79536/
> State: failure
> Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18185/index.html
> CI Bug Log - changes from CI_DRM_8753 -> Patchwork_18185
> Summary
> FAILURE
>
> Serious unknown changes coming with Patchwork_18185 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_18185, 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_18185/index.html
>
> Possible new issues
> Here are the unknown changes that may have been introduced in Patchwork_18185:
>
> IGT changes
> Possible regressions
> igt@i915_pm_rpm@module-reload:
> fi-tgl-y: PASS -> DMESG-WARN +4 similar issues
> Suppressed
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> igt@i915_pm_rpm@basic-pci-d3-state:
>
> {fi-tgl-dsi}: DMESG-WARN (i915#1982) -> DMESG-WARN
> igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
>
> {fi-tgl-dsi}: PASS -> DMESG-WARN +4 similar issues
> Known issues
> Here are the changes found in Patchwork_18185 that come from known issues:
>
> IGT changes
> Issues hit
> igt@gem_exec_suspend@basic-s0:
>
> fi-tgl-u2: PASS -> FAIL (i915#1888)
> igt@kms_addfb_basic@bo-too-small:
>
> fi-tgl-y: PASS -> DMESG-WARN (i915#402) +1 similar issue
> Possible fixes
> igt@debugfs_test@read_all_entries:
>
> fi-bsw-nick: INCOMPLETE (i915#1250 / i915#1436) -> PASS
> igt@gem_exec_store@basic:
>
> fi-tgl-y: DMESG-WARN (i915#402) -> PASS +2 similar issues
> igt@i915_module_load@reload:
>
> fi-byt-j1900: DMESG-WARN (i915#1982) -> PASS
>
> fi-kbl-x1275: DMESG-WARN (i915#62 / i915#92) -> PASS
>
> igt@i915_pm_rpm@basic-pci-d3-state:
>
> fi-bsw-kefka: DMESG-WARN (i915#1982) -> PASS
> igt@i915_selftest@live@execlists:
>
> fi-kbl-r: INCOMPLETE (i915#794) -> PASS
> igt@i915_selftest@live@gt_lrc:
>
> fi-tgl-u2: DMESG-FAIL (i915#1233) -> PASS
> igt@kms_flip@basic-flip-vs-modeset@a-dsi1:
>
> {fi-tgl-dsi}: DMESG-WARN (i915#1982) -> PASS
> igt@kms_pipe_crc_basic@read-crc-pipe-a-frame-sequence:
>
> fi-tgl-u2: DMESG-WARN (i915#402) -> PASS
> Warnings
> igt@gem_exec_suspend@basic-s0:
>
> fi-kbl-x1275: DMESG-WARN (i915#62 / i915#92) -> DMESG-WARN (i915#1982 / i915#62 / i915#92 / i915#95)
> igt@kms_flip@basic-flip-vs-dpms@a-dp1:
>
> fi-kbl-x1275: DMESG-WARN (i915#62 / i915#92 / i915#95) -> DMESG-WARN (i915#62 / i915#92)
> igt@kms_force_connector_basic@force-edid:
>
> fi-kbl-x1275: DMESG-WARN (i915#62 / i915#92) -> DMESG-WARN (i915#62 / i915#92 / i915#95) +4 similar issues
> {name}: This element is suppressed. This means it is ignored when computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
> Participating hosts (46 -> 40)
> Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
>
> Build changes
> Linux: CI_DRM_8753 -> Patchwork_18185
> CI-20190529: 20190529
> CI_DRM_8753: 62f01b776240c4586b3cbbdbe6065d4473d45429 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_5737: c18a9c1083ce9344ff71ae405b9f2deaa82b6702 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_18185: b0efac00fd8cdd3d7a3cc3140ba0df8bda56ebf3 @ git://anongit.freedesktop.org/gfx-ci/linux
>
> == Linux commits ==
>
> b0efac00fd8c drm/i915/display: Ensure that ret is always initialized in icl_combo_phy_verify_state
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2020-07-28 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 4:27 [PATCH] drm/i915/display: Ensure that ret is always initialized in icl_combo_phy_verify_state Nathan Chancellor
2020-07-16 4:27 ` [Intel-gfx] " Nathan Chancellor
2020-07-16 4:27 ` Nathan Chancellor
2020-07-16 4:44 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-07-16 5:06 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-07-28 1:47 ` Souza, Jose [this message]
2020-07-28 4:08 ` Nathan Chancellor
2020-07-16 5:31 ` [PATCH] " Matt Roper
2020-07-16 5:31 ` [Intel-gfx] " Matt Roper
2020-07-16 5:31 ` Matt Roper
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=74694924dbd548db634148b9ee8eaed2fc738f3f.camel@intel.com \
--to=jose.souza@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=natechancellor@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.