All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx]  ✗ Fi.CI.IGT: failure for drm/i915: Add relocation exceptions for two other platforms
Date: Thu, 29 Apr 2021 19:46:12 +0300	[thread overview]
Message-ID: <YIri1F/6Yu4YWSBZ@intel.com> (raw)
In-Reply-To: <20210429081631.GA3868@zkempczy-mobl2>

On Thu, Apr 29, 2021 at 10:16:31AM +0200, Zbigniew Kempczyński wrote:
> On Wed, Apr 28, 2021 at 07:43:42PM +0000, Patchwork wrote:
> >    Patch Details
> > 
> >    Series:  drm/i915: Add relocation exceptions for two other platforms         
> >    URL:     https://patchwork.freedesktop.org/series/89594/                     
> >    State:   failure                                                             
> >    Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20017/index.html 
> > 
> >       CI Bug Log - changes from CI_DRM_10023_full -> Patchwork_20017_full
> > 
> > Summary
> > 
> >    FAILURE
> > 
> >    Serious unknown changes coming with Patchwork_20017_full absolutely need
> >    to be
> >    verified manually.
> > 
> >    If you think the reported changes have nothing to do with the changes
> >    introduced in Patchwork_20017_full, please notify your bug team to allow
> >    them
> >    to document this new failure mode, which will reduce false positives in
> >    CI.
> > 
> > Possible new issues
> > 
> >    Here are the unknown changes that may have been introduced in
> >    Patchwork_20017_full:
> > 
> >   IGT changes
> > 
> >     Possible regressions
> > 
> >      * igt@kms_flip_tiling@flip-changes-tiling-yf@edp-1-pipe-b:
> >           * shard-skl: PASS -> FAIL
> 
> I don't think enabling relocations on rkl/adl has the influence to skl
> but if anyone knows I'm wrong please share the details. Otherwise
> I would rerun the series to ensure this is incidental failure.

I suspect this is due to a bug in igt kms legacy commits. At least
I see a failing alpha blend test on pipe B in the log before this one,
which is how the bug hits us usually.

I'm trying to fix it atm, but unfortunately the fix is revealing other
harder to solve bugs which need to be fixed first :/

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2021-04-29 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 17:30 [Intel-gfx] [PATCH] drm/i915: Add relocation exceptions for two other platforms Zbigniew Kempczyński
2021-04-28 17:30 ` Zbigniew Kempczyński
2021-04-28 18:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-04-28 19:43 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-04-29  8:16   ` Zbigniew Kempczyński
2021-04-29 16:46     ` Ville Syrjälä [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=YIri1F/6Yu4YWSBZ@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=zbigniew.kempczynski@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.