All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anshuman Gupta <anshuman.gupta@intel.com>
To: lakshminarayana.vudum@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx]  ✗ Fi.CI.BAT: failure for Tweaked Wa_14010685332 for all PCHs
Date: Tue, 10 Aug 2021 20:52:32 +0530	[thread overview]
Message-ID: <20210810152230.GA814@intel.com> (raw)
In-Reply-To: <162860384942.29683.15649135811749450065@emeril.freedesktop.org>

On 2021-08-10 at 13:57:29 +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: Tweaked Wa_14010685332 for all PCHs
> URL   : https://patchwork.freedesktop.org/series/93548/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_10464 -> Patchwork_20792
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with Patchwork_20792 absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_20792, 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_20792/index.html
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in Patchwork_20792:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@core_hotunplug@unbind-rebind:
>     - fi-rkl-guc:         NOTRUN -> [DMESG-WARN][1]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20792/fi-rkl-guc/igt@core_hotunplug@unbind-rebind.html
	Hi Lakshmi ,
	Above CI BAT failure is a unrealted failure(not realted to display), it seems related to core power.
	could you plese create the issue and re-report the result.
	Thanks,
	Anshuman Gupta.	
> 
>   
> Known issues
> ------------
> 
>   Here are the changes found in Patchwork_20792 that come from known issues:
> 
> ### CI changes ###
> 
> #### Issues hit ####
> 
>   * boot:
>     - fi-kbl-soraka:      [PASS][2] -> [FAIL][3] ([i915#3895])
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10464/fi-kbl-soraka/boot.html
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20792/fi-kbl-soraka/boot.html
> 
>   
> 
> ### IGT changes ###
> 
> #### Issues hit ####
> 
>   * igt@prime_vgem@basic-userptr:
>     - fi-rkl-guc:         NOTRUN -> [SKIP][4] ([i915#3301])
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20792/fi-rkl-guc/igt@prime_vgem@basic-userptr.html
> 
>   * igt@prime_vgem@basic-write:
>     - fi-rkl-guc:         NOTRUN -> [SKIP][5] ([i915#3291]) +2 similar issues
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20792/fi-rkl-guc/igt@prime_vgem@basic-write.html
> 
>   
> #### Possible fixes ####
> 
>   * igt@i915_pm_rps@basic-api:
>     - fi-rkl-guc:         [DMESG-WARN][6] ([i915#3925]) -> [PASS][7]
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10464/fi-rkl-guc/igt@i915_pm_rps@basic-api.html
>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20792/fi-rkl-guc/igt@i915_pm_rps@basic-api.html
> 
>   
> #### Warnings ####
> 
>   * igt@runner@aborted:
>     - fi-rkl-guc:         [FAIL][8] ([i915#3925]) -> [FAIL][9] ([i915#1602])
>    [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10464/fi-rkl-guc/igt@runner@aborted.html
>    [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20792/fi-rkl-guc/igt@runner@aborted.html
> 
>   
>   [i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
>   [i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
>   [i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
>   [i915#3895]: https://gitlab.freedesktop.org/drm/intel/issues/3895
>   [i915#3925]: https://gitlab.freedesktop.org/drm/intel/issues/3925
> 
> 
> Participating hosts (37 -> 34)
> ------------------------------
> 
>   Missing    (3): fi-bdw-samus fi-bsw-cyan bat-jsl-1 
> 
> 
> Build changes
> -------------
> 
>   * Linux: CI_DRM_10464 -> Patchwork_20792
> 
>   CI-20190529: 20190529
>   CI_DRM_10464: 294a55f328023a4e36f46e5eb6c4859076efd850 @ git://anongit.freedesktop.org/gfx-ci/linux
>   IGT_6165: df5d05d742275b049f6f3c852a86c4769966b126 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>   Patchwork_20792: 0af364b9489343e7bf0eb498f34d70f67dd7551c @ git://anongit.freedesktop.org/gfx-ci/linux
> 
> 
> == Linux commits ==
> 
> 0af364b94893 drm/i915: Tweaked Wa_14010685332 for all PCHs
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20792/index.html

  reply	other threads:[~2021-08-10 15:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 11:31 [Intel-gfx] [CI v2 0/1] Tweaked Wa_14010685332 for all PCHs Anshuman Gupta
2021-08-10 11:31 ` [Intel-gfx] [CI v2 1/1] drm/i915: " Anshuman Gupta
2021-08-10 13:26 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-08-10 13:57 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-08-10 15:22   ` Anshuman Gupta [this message]
2021-08-10 20:04     ` Vudum, Lakshminarayana
2021-08-12 16:15     ` Vudum, Lakshminarayana
2021-08-10 16:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-10 22:11 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-08-12 10:12   ` Anshuman Gupta
2021-08-12 16:06 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork

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=20210810152230.GA814@intel.com \
    --to=anshuman.gupta@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lakshminarayana.vudum@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 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.