From: Chris Wilson <chris@chris-wilson.co.uk>
To: Patchwork <patchwork@emeril.freedesktop.org>,
"Michał Winiarski" <michal.winiarski@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [v3,01/13] drm/i915/guc: Keep GuC interrupts enabled when using GuC
Date: Mon, 19 Mar 2018 12:25:54 +0000 [thread overview]
Message-ID: <152146235498.18954.17648169224292460068@mail.alporthouse.com> (raw)
In-Reply-To: <20180319110845.23411.61576@emeril.freedesktop.org>
Quoting Patchwork (2018-03-19 11:08:45)
> == Series Details ==
>
> Series: series starting with [v3,01/13] drm/i915/guc: Keep GuC interrupts enabled when using GuC
> URL : https://patchwork.freedesktop.org/series/40170/
> State : failure
>
> == Summary ==
>
> ---- Possible new issues:
>
> Test kms_cursor_legacy:
> Subgroup cursor-vs-flip-legacy:
> pass -> FAIL (shard-hsw)
> Test perf:
> Subgroup gen8-unprivileged-single-ctx-counters:
> pass -> FAIL (shard-apl)
> Test pm_rc6_residency:
> Subgroup rc6-accuracy:
> pass -> SKIP (shard-snb)
>
> ---- Known issues:
>
> Test drv_missed_irq:
> pass -> SKIP (shard-apl) fdo#103199
Oh cibuglog, no this is not that bug.
> Test kms_flip:
> Subgroup 2x-plain-flip-ts-check:
> pass -> FAIL (shard-hsw) fdo#100368 +1
> Test kms_rotation_crc:
> Subgroup primary-rotation-180:
> fail -> PASS (shard-hsw) fdo#103925
> Test kms_sysfs_edid_timing:
> pass -> WARN (shard-apl) fdo#100047
>
> fdo#103199 https://bugs.freedesktop.org/show_bug.cgi?id=103199
> fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
> fdo#103925 https://bugs.freedesktop.org/show_bug.cgi?id=103925
> fdo#100047 https://bugs.freedesktop.org/show_bug.cgi?id=100047
Pushed thanks for the patches and review,
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-19 12:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 9:53 [PATCH v3 01/13] drm/i915/guc: Keep GuC interrupts enabled when using GuC Michał Winiarski
2018-03-19 9:53 ` [PATCH v3 02/13] drm/i915/guc: Log runtime should consist of both mapping and relay Michał Winiarski
2018-03-19 9:53 ` [PATCH v3 03/13] drm/i915/guc: Merge log relay file and channel creation Michał Winiarski
2018-03-19 9:53 ` [PATCH v2 04/13] drm/i915/guc: Flush directly in log unregister Michał Winiarski
2018-03-19 9:53 ` [PATCH v3 05/13] drm/i915/guc: Split relay control and GuC log level Michał Winiarski
2018-03-19 9:53 ` [PATCH v2 06/13] drm/i915/guc: Move check for fast memcpy_wc to relay creation Michał Winiarski
2018-03-19 9:53 ` [PATCH v2 07/13] drm/i915/guc: Get rid of GuC log runtime Michał Winiarski
2018-03-19 9:53 ` [PATCH 08/13] drm/i915/guc: Always print log stats in i915_guc_info when using GuC Michał Winiarski
2018-03-19 9:53 ` [PATCH v3 09/13] drm/i915/guc: Don't print out relay statistics when relay is disabled Michał Winiarski
2018-03-19 9:53 ` [PATCH v3 10/13] drm/i915/guc: Allow user to control default GuC logging Michał Winiarski
2018-03-19 11:45 ` Sagar Arun Kamble
2018-03-19 9:53 ` [PATCH v2 11/13] drm/i915/guc: Default to non-verbose " Michał Winiarski
2018-03-19 9:53 ` [PATCH 12/13] drm/i915/guc: Demote GuC error messages Michał Winiarski
2018-03-19 11:49 ` Chris Wilson
2018-03-19 9:53 ` [PATCH 13/13] HAX enable guc for CI Michał Winiarski
2018-03-19 10:04 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v3,01/13] drm/i915/guc: Keep GuC interrupts enabled when using GuC Patchwork
2018-03-19 10:20 ` ✓ Fi.CI.BAT: success " Patchwork
2018-03-19 11:08 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-03-19 12:25 ` Chris Wilson [this message]
2018-03-19 11:17 ` [PATCH v3 01/13] " Sagar Arun Kamble
2018-03-19 12:24 ` Michal Wajdeczko
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=152146235498.18954.17648169224292460068@mail.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.winiarski@intel.com \
--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.