From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Patchwork <patchwork@annarchy.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Decouple execbuf uAPI from internal implementation (rev2)
Date: Thu, 21 Jan 2016 11:05:10 +0000 [thread overview]
Message-ID: <56A0BB66.2020106@linux.intel.com> (raw)
In-Reply-To: <20160115172058.32424.50104@annarchy.freedesktop.org>
On 15/01/16 17:20, Patchwork wrote:
> == Summary ==
>
> Built on 615fbad7f4cea73b1a8eccdcc942c8ca1a708dab drm-intel-nightly: 2016y-01m-15d-09h-46m-32s UTC integration manifest
>
> Test gem_storedw_loop:
> Subgroup basic-render:
> pass -> DMESG-WARN (skl-i5k-2) UNSTABLE
> pass -> DMESG-WARN (skl-i7k-2) UNSTABLE
Known unrelated: https://bugs.freedesktop.org/show_bug.cgi?id=93693
> Test kms_flip:
> Subgroup basic-flip-vs-modeset:
> dmesg-warn -> PASS (skl-i5k-2)
> Test kms_pipe_crc_basic:
> Subgroup read-crc-pipe-b-frame-sequence:
> pass -> DMESG-WARN (byt-nuc)
Known unrelated: https://bugs.freedesktop.org/show_bug.cgi?id=93121
>
> bdw-nuci7 total:138 pass:128 dwarn:1 dfail:0 fail:0 skip:9
> bdw-ultra total:138 pass:132 dwarn:0 dfail:0 fail:0 skip:6
> bsw-nuc-2 total:141 pass:115 dwarn:2 dfail:0 fail:0 skip:24
> byt-nuc total:141 pass:122 dwarn:4 dfail:0 fail:0 skip:15
> hsw-brixbox total:141 pass:134 dwarn:0 dfail:0 fail:0 skip:7
> ilk-hp8440p total:141 pass:101 dwarn:3 dfail:0 fail:0 skip:37
> ivb-t430s total:135 pass:122 dwarn:3 dfail:4 fail:0 skip:6
> skl-i5k-2 total:141 pass:131 dwarn:2 dfail:0 fail:0 skip:8
> skl-i7k-2 total:141 pass:131 dwarn:2 dfail:0 fail:0 skip:8
> snb-dellxps total:141 pass:122 dwarn:5 dfail:0 fail:0 skip:14
> snb-x220t total:141 pass:122 dwarn:5 dfail:0 fail:1 skip:13
>
> HANGED hsw-gt2 in igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a
>
> Results at /archive/results/CI_IGT_test/Patchwork_1201/
>
>
Merged.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-01-21 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 15:02 [PATCH] drm/i915: Decouple execbuf uAPI from internal implementation Tvrtko Ursulin
2016-01-14 15:49 ` ✗ failure: Fi.CI.BAT Patchwork
2016-01-14 22:09 ` [PATCH] drm/i915: Decouple execbuf uAPI from internal implementation Chris Wilson
2016-01-15 10:29 ` Tvrtko Ursulin
2016-01-15 11:36 ` Chris Wilson
2016-01-15 15:12 ` [PATCH v2] " Tvrtko Ursulin
2016-01-15 15:53 ` Chris Wilson
2016-01-21 10:22 ` Daniel Vetter
2016-01-27 6:15 ` Gong, Zhipeng
2016-03-25 13:18 ` [PATCH] " Kukanova, Svetlana
2016-04-05 9:17 ` Tvrtko Ursulin
2016-01-15 17:20 ` ✗ Fi.CI.BAT: failure for drm/i915: Decouple execbuf uAPI from internal implementation (rev2) Patchwork
2016-01-21 11:05 ` 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=56A0BB66.2020106@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@annarchy.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.