From: Matt Roper <matthew.d.roper@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/skl+: Use plane size for relative data rate calculation
Date: Wed, 6 Apr 2016 11:03:43 -0700 [thread overview]
Message-ID: <20160406180343.GK20385@intel.com> (raw)
In-Reply-To: <20160406160636.18876.85597@emeril.freedesktop.org>
On Wed, Apr 06, 2016 at 04:06:36PM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/skl+: Use plane size for relative data rate calculation
> URL : https://patchwork.freedesktop.org/series/5376/
> State : failure
>
> == Summary ==
>
> Series 5376v1 drm/i915/skl+: Use plane size for relative data rate calculation
> http://patchwork.freedesktop.org/api/1.0/series/5376/revisions/1/mbox/
>
> Test drv_module_reload_basic:
> dmesg-warn -> PASS (bsw-nuc-2)
> Test gem_ctx_param_basic:
> Subgroup invalid-ctx-set:
> dmesg-warn -> PASS (bsw-nuc-2)
> Subgroup invalid-size-get:
> pass -> DMESG-WARN (bsw-nuc-2)
> Test gem_ctx_switch:
> Subgroup basic-default:
> pass -> DMESG-FAIL (bsw-nuc-2)
Both are
https://bugs.freedesktop.org/show_bug.cgi?id=94584
> Test gem_storedw_loop:
> Subgroup basic-blt:
> dmesg-fail -> PASS (bsw-nuc-2)
> Subgroup basic-bsd:
> skip -> PASS (bsw-nuc-2)
> Test kms_addfb_basic:
> Subgroup bad-pitch-128:
> dmesg-warn -> PASS (bsw-nuc-2)
> Test kms_flip:
> Subgroup basic-flip-vs-dpms:
> dmesg-warn -> PASS (bsw-nuc-2)
> pass -> DMESG-WARN (ilk-hp8440p) UNSTABLE
https://bugs.freedesktop.org/show_bug.cgi?id=93787
> Subgroup basic-flip-vs-modeset:
> dmesg-warn -> PASS (ilk-hp8440p) UNSTABLE
> Test kms_force_connector_basic:
> Subgroup force-edid:
> pass -> SKIP (ivb-t430s)
> Test kms_pipe_crc_basic:
> Subgroup suspend-read-crc-pipe-b:
> incomplete -> PASS (hsw-gt2)
>
> bdw-nuci7 total:196 pass:184 dwarn:0 dfail:0 fail:0 skip:12
> bdw-ultra total:196 pass:175 dwarn:0 dfail:0 fail:0 skip:21
> bsw-nuc-2 total:196 pass:157 dwarn:1 dfail:1 fail:0 skip:37
> byt-nuc total:196 pass:161 dwarn:0 dfail:0 fail:0 skip:35
> hsw-brixbox total:196 pass:174 dwarn:0 dfail:0 fail:0 skip:22
> hsw-gt2 total:196 pass:179 dwarn:0 dfail:0 fail:0 skip:17
> ilk-hp8440p total:196 pass:131 dwarn:1 dfail:0 fail:0 skip:64
> ivb-t430s total:196 pass:170 dwarn:0 dfail:0 fail:0 skip:26
> skl-i7k-2 total:196 pass:173 dwarn:0 dfail:0 fail:0 skip:23
> skl-nuci5 total:196 pass:185 dwarn:0 dfail:0 fail:0 skip:11
> snb-dellxps total:196 pass:162 dwarn:0 dfail:0 fail:0 skip:34
> snb-x220t total:196 pass:162 dwarn:0 dfail:0 fail:1 skip:33
>
> Results at /archive/results/CI_IGT_test/Patchwork_1818/
>
> ab13a48af1102b84bdb8dcdfbef1b5b44fab8d3d drm-intel-nightly: 2016y-04m-06d-11h-23m-30s UTC integration manifest
> 278a2dfb05bef0627573d0eb98e89f0cbef7d3b5 drm/i915/skl+: Use plane size for relative data rate calculation
>
--
Matt Roper
Graphics Software Engineer
IoTG Platform Enabling & Development
Intel Corporation
(916) 356-2795
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-04-06 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 15:26 [PATCH RESEND FOR CI] drm/i915/skl+: Use plane size for relative data rate calculation Matt Roper
2016-04-06 16:06 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-04-06 18:03 ` Matt Roper [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=20160406180343.GK20385@intel.com \
--to=matthew.d.roper@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