From: Dave Gordon <david.s.gordon@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Ro.CI.BAT: failure for drm/i915/guc: emit (drm) messages at the most appropriate level
Date: Fri, 22 Jul 2016 11:59:10 +0100 [thread overview]
Message-ID: <5791FC7E.5090808@intel.com> (raw)
In-Reply-To: <20160722062528.28654.66001@emeril.freedesktop.org>
On 22/07/16 07:25, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/guc: emit (drm) messages at the most appropriate level
> URL : https://patchwork.freedesktop.org/series/10150/
> State : failure
>
> == Summary ==
>
> Series 10150v1 drm/i915/guc: emit (drm) messages at the most appropriate level
> http://patchwork.freedesktop.org/api/1.0/series/10150/revisions/1/mbox
>
> Test gem_sync:
> Subgroup basic-store-each:
> pass -> DMESG-FAIL (ro-bdw-i7-5600u)
The now-familiar https://bugs.freedesktop.org/show_bug.cgi?id=96974
Bug 96974 - [BAT BDW] gem_sync / basic-store-each fails sporadically
Though it looks like Chris may have a fix for this :)
.Dave.
> fi-hsw-i7-4770k total:244 pass:216 dwarn:0 dfail:0 fail:8 skip:20
> fi-kbl-qkkr total:244 pass:180 dwarn:27 dfail:1 fail:9 skip:27
> fi-skl-i5-6260u total:244 pass:224 dwarn:0 dfail:0 fail:8 skip:12
> fi-skl-i7-6700k total:244 pass:210 dwarn:0 dfail:0 fail:8 skip:26
> fi-snb-i7-2600 total:244 pass:196 dwarn:0 dfail:0 fail:8 skip:40
> ro-bdw-i5-5250u total:244 pass:219 dwarn:4 dfail:0 fail:8 skip:13
> ro-bdw-i7-5557U total:244 pass:221 dwarn:1 dfail:0 fail:8 skip:14
> ro-bdw-i7-5600u total:244 pass:203 dwarn:0 dfail:1 fail:8 skip:32
> ro-bsw-n3050 total:218 pass:173 dwarn:0 dfail:0 fail:2 skip:42
> ro-byt-n2820 total:244 pass:197 dwarn:0 dfail:0 fail:9 skip:38
> ro-hsw-i3-4010u total:244 pass:212 dwarn:0 dfail:0 fail:8 skip:24
> ro-hsw-i7-4770r total:244 pass:212 dwarn:0 dfail:0 fail:8 skip:24
> ro-ilk-i7-620lm total:244 pass:172 dwarn:0 dfail:0 fail:9 skip:63
> ro-ilk1-i5-650 total:239 pass:172 dwarn:0 dfail:0 fail:9 skip:58
> ro-ivb-i7-3770 total:244 pass:203 dwarn:0 dfail:0 fail:8 skip:33
> ro-skl3-i5-6260u total:244 pass:224 dwarn:0 dfail:0 fail:8 skip:12
> ro-snb-i7-2620M total:244 pass:193 dwarn:0 dfail:0 fail:9 skip:42
>
> Results at /archive/results/CI_IGT_test/RO_Patchwork_1566/
>
> cf82f46 drm-intel-nightly: 2016y-07m-21d-20h-43m-36s UTC integration manifest
> 5c44b9b drm/i915/guc: revisit GuC loader message levels
> 50ffd43 drm/i915/guc: downgrade some DRM_ERROR() messages to DRM_WARN()
> 900ee7b drm: extra printk() wrapper macros
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-07-22 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 18:27 [PATCH v4 0/3] drm/i915/guc: emit (drm) messages at the most appropriate level Dave Gordon
2016-07-21 18:27 ` [PATCH v4 1/3] drm: extra printk() wrapper macros Dave Gordon
2016-07-21 18:27 ` [PATCH v4 2/3] drm/i915/guc: downgrade some DRM_ERROR() messages to DRM_WARN() Dave Gordon
2016-07-21 18:27 ` [PATCH v4 3/3] drm/i915/guc: revisit GuC loader message levels Dave Gordon
2016-07-22 6:25 ` ✗ Ro.CI.BAT: failure for drm/i915/guc: emit (drm) messages at the most appropriate level Patchwork
2016-07-22 10:59 ` Dave Gordon [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=5791FC7E.5090808@intel.com \
--to=david.s.gordon@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 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.