From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for series starting with [1/5] drm/i915: Add wait_for_us
Date: Thu, 3 Mar 2016 17:01:15 +0000 [thread overview]
Message-ID: <56D86DDB.4080104@linux.intel.com> (raw)
In-Reply-To: <20160303150324.32567.6459@emeril.freedesktop.org>
On 03/03/16 15:03, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [1/5] drm/i915: Add wait_for_us
> URL : https://patchwork.freedesktop.org/series/4059/
> State : failure
>
> == Summary ==
>
> Series 4059v1 Series without cover letter
> http://patchwork.freedesktop.org/api/1.0/series/4059/revisions/1/mbox/
>
> Test gem_sync:
> Subgroup basic-bsd:
> dmesg-fail -> PASS (ilk-hp8440p)
> Test kms_flip:
> Subgroup basic-flip-vs-wf_vblank:
> pass -> DMESG-WARN (hsw-gt2)
Known unrelated: https://bugs.freedesktop.org/show_bug.cgi?id=94349
> Subgroup basic-plain-flip:
> pass -> DMESG-WARN (snb-dellxps)
Same as above.
> dmesg-warn -> PASS (hsw-brixbox)
> Test kms_force_connector_basic:
> Subgroup force-edid:
> skip -> PASS (ilk-hp8440p)
> Test kms_psr_sink_crc:
> Subgroup psr_basic:
> dmesg-warn -> PASS (bdw-ultra)
> Test pm_rpm:
> Subgroup basic-pci-d3-state:
> dmesg-warn -> PASS (snb-dellxps)
> Subgroup basic-rte:
> pass -> DMESG-WARN (bsw-nuc-2)
Known unrelated: https://bugs.freedesktop.org/show_bug.cgi?id=94164
>
> bdw-nuci7 total:183 pass:172 dwarn:0 dfail:0 fail:0 skip:11
> bdw-ultra total:183 pass:165 dwarn:0 dfail:0 fail:0 skip:18
> bsw-nuc-2 total:183 pass:147 dwarn:1 dfail:0 fail:1 skip:34
> byt-nuc total:183 pass:152 dwarn:0 dfail:0 fail:0 skip:31
> hsw-brixbox total:183 pass:163 dwarn:1 dfail:0 fail:0 skip:19
> hsw-gt2 total:183 pass:168 dwarn:1 dfail:0 fail:0 skip:14
> ilk-hp8440p total:183 pass:125 dwarn:0 dfail:0 fail:0 skip:58
> ivb-t430s total:183 pass:162 dwarn:0 dfail:0 fail:0 skip:21
> skl-i5k-2 total:183 pass:163 dwarn:0 dfail:0 fail:0 skip:20
> skl-i7k-2 total:183 pass:163 dwarn:0 dfail:0 fail:0 skip:20
> snb-dellxps total:183 pass:153 dwarn:1 dfail:0 fail:0 skip:29
>
> Results at /archive/results/CI_IGT_test/Patchwork_1524/
>
> 1b34b1cf252bb734775331c435b0e3a3de484db6 drm-intel-nightly: 2016y-03m-03d-13h-06m-21s UTC integration manifest
> f69fa33fd56c8d11757c3f12b918b3a5b1ede935 drm/i915: Do not wait atomically for display clocks
> dae20b8161fd1e3b460f176064689f28aa852210 drm/i915: Do not lie about atomic wait granularity
> 328f1cc8e235f05948e43c71cf4c3457185a236f drm/i915: Kconfig for extra driver debugging
> 0324e4ed18bbc27f6620c29bf266eaa4debee3fb drm/i915/lrc: Do not wait atomically when stopping engines
> 822b3c5647a918dd7f1b7a81318c82f99697a0d3 drm/i915: Add wait_for_us
Just need some r-b's and this is merge-able then. :)
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-03-03 17:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 14:36 [PATCH 1/5] drm/i915: Add wait_for_us Tvrtko Ursulin
2016-03-03 14:36 ` [PATCH 2/5] drm/i915/lrc: Do not wait atomically when stopping engines Tvrtko Ursulin
2016-03-03 14:36 ` [PATCH 3/5] drm/i915: Kconfig for extra driver debugging Tvrtko Ursulin
2016-03-03 14:36 ` [PATCH 4/5] drm/i915: Do not lie about atomic wait granularity Tvrtko Ursulin
2016-03-03 15:11 ` Chris Wilson
2016-03-03 15:43 ` Tvrtko Ursulin
2016-03-03 16:10 ` Chris Wilson
2016-03-03 16:21 ` [PATCH v5 4/5] drm/i915: Do not lie about atomic timeout granularity Tvrtko Ursulin
2016-03-03 14:36 ` [PATCH 5/5] drm/i915: Do not wait atomically for display clocks Tvrtko Ursulin
2016-03-03 15:03 ` ✗ Fi.CI.BAT: failure for series starting with [1/5] drm/i915: Add wait_for_us Patchwork
2016-03-03 17:01 ` Tvrtko Ursulin [this message]
2016-03-03 17:20 ` Chris Wilson
2016-03-03 17:35 ` Tvrtko Ursulin
2016-03-03 17:01 ` ✗ Fi.CI.BAT: warning for series starting with [1/5] drm/i915: Add wait_for_us (rev2) Patchwork
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=56D86DDB.4080104@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 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.