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 series starting with [v6,1/1] drm/i915/pxp: Promote pxp subsystem to top-level of i915
Date: Thu, 1 Dec 2022 19:25:32 +0000 [thread overview]
Message-ID: <c7461261fd0be882f7db295137cf79fbdb435c8c.camel@intel.com> (raw)
In-Reply-To: <166980724791.2880.15961323416952448626@emeril.freedesktop.org>
On Wed, 2022-11-30 at 11:20 +0000, Patchwork wrote:
> Patch Details
> Series: series starting with [v6,1/1] drm/i915/pxp: Promote pxp subsystem to top-level of i915 URL:
> https://patchwork.freedesktop.org/series/111463/ State: failure Details:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111463v1/index.html
> CI Bug Log - changes from CI_DRM_12449_full -> Patchwork_111463v1_fullSummaryFAILURE
> Serious unknown changes coming with Patchwork_111463v1_full absolutely need to be
> verified manually.
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_111463v1_full, please notify your bug team to allow them
> to document this new failure mode, which will reduce false positives in CI.
> Participating hosts (10 -> 10)No changes in participating hosts
> Possible new issuesHere are the unknown changes that may have been introduced in Patchwork_111463v1_full:
> IGT changesPossible regressions * igt@perf_pmu@enable-race@bcs0:shard-tglb: PASS -> INCOMPLETE
>
I am pretty sure this is unrelated because PXP is not enabled on SKL. The change on the dynamic allocation of pxp
structure cannot be related else we would get much more severe CI failures on all non-PXP platforms.
> Known issuesHere are the changes found in Patchwork_111463v1_full that come from known issues:
> IGT changesIssues hit * igt@gem_exec_balancer@parallel-bb-first:shard-iclb: PASS -> SKIP (i915#4525) +1 similar issue
Alan: [snip]
next prev parent reply other threads:[~2022-12-01 19:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 2:02 [Intel-gfx] [PATCH v6 1/1] drm/i915/pxp: Promote pxp subsystem to top-level of i915 Alan Previn
2022-11-30 2:28 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for series starting with [v6,1/1] " Patchwork
2022-11-30 2:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-30 11:20 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-12-01 19:25 ` Teres Alexis, Alan Previn [this message]
2022-11-30 17:32 ` [Intel-gfx] [PATCH v6 1/1] " Matt Roper
2022-11-30 17:42 ` Vivi, Rodrigo
2022-12-01 19:20 ` Teres Alexis, Alan Previn
2022-12-01 23:55 ` Teres Alexis, Alan Previn
2022-12-02 0:11 ` 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=c7461261fd0be882f7db295137cf79fbdb435c8c.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