From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx-trybot@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, "Vudum,
Lakshminarayana" <lakshminarayana.vudum@intel.com>
Subject: Re: [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915/fbc: Don't nuke manually around flips (rev3)
Date: Fri, 30 Apr 2021 15:39:46 +0300 [thread overview]
Message-ID: <YIv6kpNjEusaeDyp@intel.com> (raw)
In-Reply-To: <161976430944.17882.10814391960381972941@emeril.freedesktop.org>
On Fri, Apr 30, 2021 at 06:31:49AM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [1/2] drm/i915/fbc: Don't nuke manually around flips (rev3)
> URL : https://patchwork.freedesktop.org/series/89517/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_10031_full -> Trybot_7704_full
> ====================================================
>
> Summary
> -------
>
> **SUCCESS**
>
> No regressions found.
...
> * igt@kms_draw_crc@draw-method-xrgb8888-render-untiled:
> - shard-iclb: [PASS][33] -> [FAIL][34] ([i915#52] / [i915#54]) +1 similar issue
> [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10031/shard-iclb4/igt@kms_draw_crc@draw-method-xrgb8888-render-untiled.html
> [34]: https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_7704/shard-iclb8/igt@kms_draw_crc@draw-method-xrgb8888-render-untiled.html
We have some seriously overzealous failure filtering going on here.
A lot of new failures on iclb with this run that all just got ignored.
We need to get this filtering reduced significantly or we'll end
up merging regressions. Not sure if it's possibly to clean it up
in any gradual way. Might just have to throw out everything related
to crc mismatches and start again from scratch. I suspect FIFO
underruns are in a similar situation.
And in the future really need to start tracking these types of
failures more or less by platform. I think currently we have just
several of these ancient meta-bugs where everything gets clumped
together, and thus no one can ever know what has been fixed and
what is still a problem on each platform.
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
parent reply other threads:[~2021-04-30 12:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <161976430944.17882.10814391960381972941@emeril.freedesktop.org>]
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=YIv6kpNjEusaeDyp@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx-trybot@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lakshminarayana.vudum@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox