From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: C8 fix
Date: Tue, 28 May 2019 16:03:12 +0300 [thread overview]
Message-ID: <20190528130312.GK5942@intel.com> (raw)
In-Reply-To: <20190513214047.3916.38590@emeril.freedesktop.org>
On Mon, May 13, 2019 at 09:40:47PM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: C8 fix
> URL : https://patchwork.freedesktop.org/series/60583/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_6077_full -> Patchwork_13008_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_13008_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_13008_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_13008_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_available_modes_crc@available_mode_test_crc:
> - shard-apl: [PASS][1] -> [FAIL][2]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6077/shard-apl6/igt@kms_available_modes_crc@available_mode_test_crc.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13008/shard-apl1/igt@kms_available_modes_crc@available_mode_test_crc.html
> - shard-glk: [PASS][3] -> [FAIL][4]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6077/shard-glk7/igt@kms_available_modes_crc@available_mode_test_crc.html
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13008/shard-glk7/igt@kms_available_modes_crc@available_mode_test_crc.html
> - shard-hsw: [PASS][5] -> [FAIL][6]
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6077/shard-hsw6/igt@kms_available_modes_crc@available_mode_test_crc.html
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13008/shard-hsw5/igt@kms_available_modes_crc@available_mode_test_crc.html
> - shard-snb: [PASS][7] -> [FAIL][8]
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6077/shard-snb4/igt@kms_available_modes_crc@available_mode_test_crc.html
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13008/shard-snb6/igt@kms_available_modes_crc@available_mode_test_crc.html
Going to be fixed by removing the semi-busted C8 test:
https://patchwork.freedesktop.org/patch/305298/?series=60729&rev=1
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-05-28 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 13:39 [PATCH 0/2] drm/i915: C8 fix Ville Syrjala
2019-05-13 13:39 ` [PATCH 1/2] drm/i915: Update pipe gamma enable bits when C8 planes are getting enabled/disabled Ville Syrjala
2019-05-13 13:39 ` [PATCH 2/2] drm/i915: Add debugs for the C8 vs. legacy LUT case Ville Syrjala
2019-05-28 10:51 ` Maarten Lankhorst
2019-05-28 17:49 ` Ville Syrjälä
2019-05-13 16:20 ` ✓ Fi.CI.BAT: success for drm/i915: C8 fix Patchwork
2019-05-13 21:40 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-05-28 13:03 ` 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=20190528130312.GK5942@intel.com \
--to=ville.syrjala@linux.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