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/selftest/gsc: Ensure GSC Proxy init completes before selftests
Date: Wed, 24 May 2023 17:15:48 +0000	[thread overview]
Message-ID: <7cdc4111c1a258b54952677339592dab41dee728.camel@intel.com> (raw)
In-Reply-To: <168395370244.18763.18231456137293123019@emeril.freedesktop.org>

The error below seems unrelated to the change in this patch. In fact test below fails on APL which wont excersize the patch code change.
However, from internal testing we did see cases where CI's selftest timeout is lower than the GSC Proxy requires to complete
(i.e. the selftest would bail with timeout because it was waiting for the GSC proxy to complete but the completion came in after the timeout).

So might need to re-rev this anyway with a longer timeout. (which typically takes longer for first time boot, not at driver-reload or suspend-resume)

...alan

On Sat, 2023-05-13 at 04:55 +0000, Patchwork wrote:
> Patch Details
> Series: drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests
> URL:    https://patchwork.freedesktop.org/series/117713/
> State:  failure
> Details:        https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_117713v1/index.html
> CI Bug Log - changes from CI_DRM_13143_full -> Patchwork_117713v1_full
> Summary
> 
> FAILURE
> 
> Serious unknown changes coming with Patchwork_117713v1_full absolutely need to be
> verified manually.
> 
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_117713v1_full, please notify your bug team to allow them
> to document this new failure mode, which will reduce false positives in CI.
> 
> Participating hosts (7 -> 7)
> 
> No changes in participating hosts
> 
> Possible new issues
> 
> Here are the unknown changes that may have been introduced in Patchwork_117713v1_full:
> 
> IGT changes
> Possible regressions
> 
>   *   igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes:
>      *   shard-apl: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13143/shard-apl7/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes.html> -> ABORT<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_117713v1/shard-apl2/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes.html>
> 
alan:snip

      reply	other threads:[~2023-05-24 17:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 23:58 [Intel-gfx] [PATCH] drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests Alan Previn
2023-05-13  1:14 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-05-13  1:29 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-13  4:55 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-05-24 17:15   ` 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=7cdc4111c1a258b54952677339592dab41dee728.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