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.BAT: failure for series starting with [1/1] drm/i915/pxp: Separate PXP FW interface structures for both v42 and 43
Date: Wed, 26 Oct 2022 20:56:43 +0000	[thread overview]
Message-ID: <0401915cabdfc12a2d27fa3c8d4730c51059dc03.camel@intel.com> (raw)
In-Reply-To: <166665731405.15482.12991155255759957077@emeril.freedesktop.org>

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

The issues reported below are unrelated to the patch because:
1. SKL and ICL do not even support PXP and none of the code path of this series will get executed.
2. RKL supports PXP but the code paths only get executed when PXP is enabled by the component binding and activated (via IGT PXP) whereas the failure was on "[IGT] i915_selftest: starting dynamic subtest hugepages" and no PXP code paths executed.

Thus these failures are unrelated.


On Tue, 2022-10-25 at 00:21 +0000, Patchwork wrote:
Patch Details
Series: series starting with [1/1] drm/i915/pxp: Separate PXP FW interface structures for both v42 and 43
URL:    https://patchwork.freedesktop.org/series/110084/
State:  failure
Details:        https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110084v1/index.html
CI Bug Log - changes from CI_DRM_12288 -> Patchwork_110084v1
Summary

FAILURE

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

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_110084v1, 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_110084v1/index.html

Participating hosts (41 -> 41)

Additional (1): bat-atsm-1
Missing (1): fi-ctg-p8600

Possible new issues

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

IGT changes
Possible regressions

  *   igt@i915_selftest@live@hugepages:

     *   fi-rkl-guc: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12288/fi-rkl-guc/igt@i915_selftest@live@hugepages.html> -> DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110084v1/fi-rkl-guc/igt@i915_selftest@live@hugepages.html>

     *   fi-skl-guc: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12288/fi-skl-guc/igt@i915_selftest@live@hugepages.html> -> DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110084v1/fi-skl-guc/igt@i915_selftest@live@hugepages.html>

     *   fi-icl-u2: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12288/fi-icl-u2/igt@i915_selftest@live@hugepages.html> -> DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110084v1/fi-icl-u2/igt@i915_selftest@live@hugepages.html>

Suppressed

The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.

  *   igt@i915_selftest@live@hugepages:
     *   {fi-tgl-dsi}: NOTRUN -> DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110084v1/fi-tgl-dsi/igt@i915_selftest@live@hugepages.html>

Known issues

Here are the changes found in Patchwork_110084v1 that come from known issues:

I

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

  reply	other threads:[~2022-10-26 20:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 18:40 [Intel-gfx] [PATCH 1/1] drm/i915/pxp: Separate PXP FW interface structures for both v42 and 43 Alan Previn
2022-10-24 23:58 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/1] " Patchwork
2022-10-24 23:59 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-25  0:21 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-10-26 20:56   ` Teres Alexis, Alan Previn [this message]
2022-11-01 23:17 ` [Intel-gfx] [PATCH 1/1] " Ceraolo Spurio, Daniele
2022-11-02  9:35   ` Jani Nikula
2022-11-08  3:48     ` Teres Alexis, Alan Previn

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=0401915cabdfc12a2d27fa3c8d4730c51059dc03.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