From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Execlists small cleanups and micro-optimisations (rev2)
Date: Mon, 29 Feb 2016 10:16:39 +0000 [thread overview]
Message-ID: <56D41A87.8090207@linux.intel.com> (raw)
In-Reply-To: <20160226172747.30359.52182@emeril.freedesktop.org>
On 26/02/16 17:27, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Execlists small cleanups and micro-optimisations (rev2)
> URL : https://patchwork.freedesktop.org/series/3853/
> State : failure
>
> == Summary ==
>
> Series 3853v2 drm/i915: Execlists small cleanups and micro-optimisations
> http://patchwork.freedesktop.org/api/1.0/series/3853/revisions/2/mbox/
>
> Test drv_hangman:
> Subgroup error-state-basic:
> pass -> FAIL (ilk-hp8440p)
Known unrelated: https://bugs.freedesktop.org/show_bug.cgi?id=94305
> Test kms_flip:
> Subgroup basic-flip-vs-dpms:
> dmesg-warn -> PASS (ilk-hp8440p) UNSTABLE
> Subgroup basic-flip-vs-modeset:
> incomplete -> PASS (ilk-hp8440p) UNSTABLE
> Test kms_pipe_crc_basic:
> Subgroup suspend-read-crc-pipe-a:
> pass -> DMESG-WARN (skl-i7k-2) UNSTABLE
Known unrelated: https://bugs.freedesktop.org/show_bug.cgi?id=93294
> Subgroup suspend-read-crc-pipe-b:
> incomplete -> PASS (hsw-gt2)
> Subgroup suspend-read-crc-pipe-c:
> dmesg-warn -> PASS (skl-i7k-2) UNSTABLE
>
> bdw-nuci7 total:166 pass:155 dwarn:0 dfail:0 fail:0 skip:11
> bdw-ultra total:169 pass:155 dwarn:0 dfail:0 fail:0 skip:14
> byt-nuc total:169 pass:144 dwarn:0 dfail:0 fail:0 skip:25
> hsw-brixbox total:169 pass:155 dwarn:0 dfail:0 fail:0 skip:14
> hsw-gt2 total:169 pass:158 dwarn:0 dfail:1 fail:0 skip:10
> ilk-hp8440p total:169 pass:118 dwarn:0 dfail:1 fail:1 skip:49
> ivb-t430s total:169 pass:154 dwarn:0 dfail:0 fail:1 skip:14
> skl-i7k-2 total:169 pass:152 dwarn:1 dfail:0 fail:0 skip:16
> snb-dellxps total:169 pass:146 dwarn:0 dfail:0 fail:1 skip:22
> snb-x220t total:169 pass:146 dwarn:0 dfail:0 fail:2 skip:21
>
> Results at /archive/results/CI_IGT_test/Patchwork_1487/
>
> e511a05b4b3bb4d1dbca99b00af6d0dc0a65d295 drm-intel-nightly: 2016y-02m-26d-13h-42m-46s UTC integration manifest
> b5bf538d5948d2f82c61c92bd452decab535d880 drm/i915: Execlists small cleanups and micro-optimisations
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-02-29 10:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 15:37 [PATCH] drm/i915: Execlists small cleanups and micro-optimisations Tvrtko Ursulin
2016-02-26 16:03 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-02-26 16:36 ` [PATCH] " Chris Wilson
2016-02-26 16:58 ` [PATCH v4] " Tvrtko Ursulin
2016-02-26 20:24 ` Chris Wilson
2016-02-29 10:45 ` Tvrtko Ursulin
2016-02-29 10:53 ` Chris Wilson
2016-02-29 11:01 ` Tvrtko Ursulin
2016-02-29 11:13 ` Chris Wilson
2016-02-29 11:40 ` Tvrtko Ursulin
2016-02-29 11:48 ` Chris Wilson
2016-02-29 11:59 ` Tvrtko Ursulin
2016-03-01 10:21 ` Tvrtko Ursulin
2016-03-01 10:32 ` Chris Wilson
2016-03-01 10:41 ` Tvrtko Ursulin
2016-03-01 10:57 ` Chris Wilson
2016-03-01 10:32 ` Chris Wilson
2016-02-26 17:27 ` ✗ Fi.CI.BAT: failure for drm/i915: Execlists small cleanups and micro-optimisations (rev2) Patchwork
2016-02-29 10:16 ` Tvrtko Ursulin [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=56D41A87.8090207@linux.intel.com \
--to=tvrtko.ursulin@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