From: Imre Deak <imre.deak@intel.com>
To: Patchwork <patchwork@annarchy.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Move load time stolen memory init earlier
Date: Tue, 19 Jan 2016 18:22:21 +0200 [thread overview]
Message-ID: <1453220541.19100.4.camel@intel.com> (raw)
In-Reply-To: <20160119134953.11857.96112@annarchy.freedesktop.org>
On ti, 2016-01-19 at 13:49 +0000, Patchwork wrote:
> == Summary ==
>
> Built on 00a0c7d1ae09b1259c7af8e5a088b0b225d805df drm-intel-nightly:
> 2016y-01m-18d-16h-50m-37s UTC integration manifest
>
> Test gem_ctx_basic:
> pass -> FAIL (bdw-ultra)
Couldn't reproduce it on the same machine. To me it looks unrelated as
it happened already several times for other patches, always on the same
machine. These BAT results are not shown on the test's "long term"
history btw. I filed a bug:
https://bugs.freedesktop.org/show_bug.cgi?id=93776
> Test kms_flip:
> Subgroup basic-flip-vs-dpms:
> dmesg-warn -> PASS (skl-i5k-2)
> Test pm_rpm:
> Subgroup basic-rte:
> dmesg-warn -> PASS (byt-nuc) UNSTABLE
>
> bdw-
> nuci7 total:140 pass:131 dwarn:0 dfail:0 fail:0 skip:9
>
> bdw-
> ultra total:140 pass:132 dwarn:0 dfail:1 fail:1 skip:6
>
> byt-
> nuc total:143 pass:126 dwarn:2 dfail:0 fail:0 skip:1
> 5
> hsw-
> brixbox total:143 pass:136 dwarn:0 dfail:0 fail:0 skip:7
>
> hsw-
> gt2 total:143 pass:139 dwarn:0 dfail:0 fail:0 skip:4
>
> ilk-
> hp8440p total:143 pass:102 dwarn:3 dfail:0 fail:0 skip:3
> 8
> ivb-
> t430s total:137 pass:124 dwarn:3 dfail:4 fail:0 skip:6
>
> skl-i5k-
> 2 total:143 pass:134 dwarn:1 dfail:0 fail:0 skip:8
> snb-
> dellxps total:143 pass:124 dwarn:5 dfail:0 fail:0 skip:1
> 4
> snb-
> x220t total:143 pass:124 dwarn:5 dfail:0 fail:1 skip:1
> 3
>
> Results at /archive/results/CI_IGT_test/Patchwork_1220/
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-01-19 16:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 13:26 [PATCH 0/7] drm/i915: Move load time stolen memory init earlier Imre Deak
2016-01-19 13:26 ` [PATCH 1/7] drm/i915: Sanitize up DMC/CSR ucode cleanup code Imre Deak
2016-01-22 12:10 ` David Weinehall
2016-01-19 13:26 ` [PATCH 2/7] drm/i915: Sanitize i915_get_bridge_dev() error path Imre Deak
2016-01-22 12:11 ` David Weinehall
2016-01-19 13:26 ` [PATCH 3/7] drm/i915: Sanitize GEM shrinker init and clean-up Imre Deak
2016-01-22 12:15 ` David Weinehall
2016-01-19 13:26 ` [PATCH 4/7] drm/i915: Sanitize i915_gem_load() " Imre Deak
2016-01-22 12:17 ` David Weinehall
2016-01-19 13:26 ` [PATCH 5/7] drm/i915: Move allocation of various workqueues earlier during init Imre Deak
2016-01-22 12:19 ` David Weinehall
2016-01-19 13:26 ` [PATCH 6/7] drm/i915: Move MCHBAR setup " Imre Deak
2016-01-22 12:21 ` David Weinehall
2016-01-19 13:26 ` [PATCH 7/7] drm/i915: Move stolen memory initialization earlier during loading Imre Deak
2016-01-22 12:23 ` David Weinehall
2016-01-27 16:39 ` Imre Deak
2016-01-19 13:49 ` ✗ Fi.CI.BAT: failure for drm/i915: Move load time stolen memory init earlier Patchwork
2016-01-19 16:22 ` Imre Deak [this message]
2016-01-25 16:21 ` Daniel Vetter
2016-01-25 17:34 ` Imre Deak
2016-01-25 17:47 ` Daniel Vetter
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=1453220541.19100.4.camel@intel.com \
--to=imre.deak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).