Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx]  ✗ Fi.CI.IGT: failure for drm/i915/guc: Add GuC-Error-Capture-Init coverage of new engine types (rev3)
Date: Mon, 24 Oct 2022 20:25:29 +0000	[thread overview]
Message-ID: <e8fe008e811e7f324ee7c1b956fcde70f75489a0.camel@intel.com> (raw)
In-Reply-To: <166619489925.29706.10615953710927182059@emeril.freedesktop.org>

[-- Attachment #1: Type: text/plain, Size: 4069 bytes --]

I believe that the issues below are not related to this series because they were running on platforms that do not use guc-submission. Additionally, both patches of this series impact steps very early in the guc initialization phase and never again - and do not impact runtime operation of display. That said, an issue if resulting from this series were to occur, it would be noticed very early in the i915 loading process.

...alan

On Wed, 2022-10-19 at 15:54 +0000, Patchwork wrote:
Patch Details
Series: drm/i915/guc: Add GuC-Error-Capture-Init coverage of new engine types (rev3)
URL:    https://patchwork.freedesktop.org/series/109737/
State:  failure
Details:        https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109737v3/index.html
CI Bug Log - changes from CI_DRM_12259_full -> Patchwork_109737v3_full
Summary

FAILURE

Serious unknown changes coming with Patchwork_109737v3_full absolutely need to be
verified manually.

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_109737v3_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.

Participating hosts (9 -> 11)

Additional (2): shard-rkl shard-dg1

Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_109737v3_full:

IGT changes
Possible regressions

  *   igt@i915_suspend@fence-restore-tiled2untiled:

     *   shard-tglb: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12259/shard-tglb3/igt@i915_suspend@fence-restore-tiled2untiled.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109737v3/shard-tglb3/igt@i915_suspend@fence-restore-tiled2untiled.html>
  *   igt@kms_plane_lowres@tiling-none@pipe-c-hdmi-a-2:

     *   shard-glk: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12259/shard-glk3/igt@kms_plane_lowres@tiling-none@pipe-c-hdmi-a-2.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109737v3/shard-glk5/igt@kms_plane_lowres@tiling-none@pipe-c-hdmi-a-2.html> +1 similar issue

Warnings

  *   igt@gem_pwrite@basic-exhaustion:

     *   shard-glk: WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12259/shard-glk9/igt@gem_pwrite@basic-exhaustion.html> (i915#2658<https://gitlab.freedesktop.org/drm/intel/issues/2658>) ->INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109737v3/shard-glk8/igt@gem_pwrite@basic-exhaustion.html>
  *   igt@runner@aborted:

     *   shard-skl: (FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12259/shard-skl4/igt@runner@aborted.html>,FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12259/shard-skl4/igt@runner@aborted.html>, FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12259/shard-skl7/igt@runner@aborted.html>, FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12259/shard-skl5/igt@runner@aborted.html>, FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12259/shard-skl2/igt@runner@aborted.html>, FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12259/shard-skl9/igt@runner@aborted.html>, FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12259/shard-skl9/igt@runner@aborted.html>, FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12259/shard-skl1/igt@runner@aborted.html>) (i915#3002<https://gitlab.freedesktop.org/drm/intel/issues/3002> /i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312> / i915#6949<https://gitlab.freedesktop.org/drm/intel/issues/6949>) -> (FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109737v3/shard-skl4/igt@runner@aborted.html>,FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109737v3/shard-skl6/igt@runner@aborted.html>, FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109737v3/shard-skl10/igt@runner@aborted.html>, FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109737v3/shard-skl1/igt@runner@aborted.html>, FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109737v3/shard-skl1/igt@runner@aborted.html>) (i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312>)


[-- Attachment #2: Type: text/html, Size: 5482 bytes --]

      reply	other threads:[~2022-10-24 20:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19  7:29 [Intel-gfx] [PATCH v3 0/2] drm/i915/guc: Add GuC-Error-Capture-Init coverage of new engine types Alan Previn
2022-10-19  7:29 ` [Intel-gfx] [PATCH v3 1/2] drm/i915/guc: Add error-capture init warnings when needed Alan Previn
2022-10-21 19:42   ` John Harrison
2022-10-19  7:29 ` [Intel-gfx] [PATCH v3 2/2] drm/i915/guc: Add compute reglist for guc err capture Alan Previn
2022-10-21 18:49   ` John Harrison
2022-10-19  8:53 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/guc: Add GuC-Error-Capture-Init coverage of new engine types (rev3) Patchwork
2022-10-19 15:54 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-24 20:25   ` Teres Alexis, Alan Previn [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=e8fe008e811e7f324ee7c1b956fcde70f75489a0.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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