From: "Michal Wajdeczko" <michal.wajdeczko@intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/huc: Fix error reported by I915_PARAM_HUC_STATUS
Date: Thu, 23 Jan 2020 15:57:27 +0100 [thread overview]
Message-ID: <op.0euo51l6xaggs7@mwajdecz-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <157974738496.1145.18249446585697033889@emeril.freedesktop.org>
On Thu, 23 Jan 2020 03:43:04 +0100, Patchwork
<patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: drm/i915/huc: Fix error reported by I915_PARAM_HUC_STATUS
> URL : https://patchwork.freedesktop.org/series/72419/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_7799 -> Patchwork_16219
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_16219 absolutely need to
> be
> verified manually.
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_16219, please notify your bug team to allow
> them
> to document this new failure mode, which will reduce false positives
> in CI.
>
> External URL:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16219/index.html
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in
> Patchwork_16219:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@gem_exec_parallel@contexts:
> - fi-byt-j1900: NOTRUN -> [FAIL][1]
> [1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16219/fi-byt-j1900/igt@gem_exec_parallel@contexts.html
no HuC here, unrelated
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-23 14:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 19:48 [Intel-gfx] [PATCH] drm/i915/huc: Fix error reported by I915_PARAM_HUC_STATUS Michal Wajdeczko
2020-01-22 23:52 ` Daniele Ceraolo Spurio
2020-01-23 15:02 ` Chris Wilson
2020-01-23 15:38 ` Michal Wajdeczko
2020-01-23 15:51 ` Chris Wilson
2020-01-26 17:41 ` Michal Wajdeczko
2020-02-05 0:43 ` Ye, Tony
2020-02-11 17:53 ` Fosha, Robert M
2020-02-11 19:57 ` Michal Wajdeczko
2020-02-11 21:54 ` Fosha, Robert M
2020-02-21 3:56 ` Ye, Tony
2020-02-28 11:33 ` Joonas Lahtinen
2020-02-28 13:44 ` Michal Wajdeczko
2020-01-23 18:26 ` Ye, Tony
2020-01-23 18:43 ` Michal Wajdeczko
2020-01-23 19:50 ` Ye, Tony
2020-01-23 2:43 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2020-01-23 14:57 ` Michal Wajdeczko [this message]
2020-01-23 18:12 ` [Intel-gfx] [PATCH] " Ye, Tony
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=op.0euo51l6xaggs7@mwajdecz-mobl1.ger.corp.intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.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 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.