From: "Kumar, Abhay" <abhay.kumar@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Daniel Vetter" <daniel@ffwll.ch>
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: edp resume/On time optimization. (rev10)
Date: Tue, 26 Jan 2016 16:21:13 -0800 [thread overview]
Message-ID: <56A80D79.6020209@intel.com> (raw)
In-Reply-To: <20160126113621.GX23290@intel.com>
On 1/26/2016 3:36 AM, Ville Syrjälä wrote:
> On Sat, Jan 23, 2016 at 08:43:33AM -0000, Patchwork wrote:
>> == Summary ==
>>
>> Built on 8fe9e785ae04fa7c37f7935cff12d62e38054b60 drm-intel-nightly: 2016y-01m-21d-11h-02m-42s UTC integration manifest
>>
>> Test gem_ctx_basic:
>> pass -> FAIL (bdw-ultra)
> This is another 'returncode -15'. I think that's just some piglit
> fail or something. I think it would indicate someone sent a SIGTERM to
> the test. Not sure why that would happen. Some timeout perhaps?
This might be a false alarm as changes between v4 and v5 is just a
static keyword removal and that shouldn't cause timeout to happen.
V4 results seems to be fine. Shall we ignore this? Is there any way to
rerun the tests apart from pushing patch again or debug this in case?
>
>> Test kms_flip:
>> Subgroup basic-flip-vs-dpms:
>> pass -> DMESG-WARN (ilk-hp8440p)
> And that's the ilk underrrun thing:
> https://bugs.freedesktop.org/show_bug.cgi?id=93787
>
>> bdw-nuci7 total:140 pass:131 dwarn:0 dfail:0 fail:0 skip:9
>> bdw-ultra total:143 pass:136 dwarn:0 dfail:0 fail:1 skip:6
>> bsw-nuc-2 total:143 pass:119 dwarn:0 dfail:0 fail:0 skip:24
>> byt-nuc total:143 pass:128 dwarn:0 dfail:0 fail:0 skip:15
>> 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:103 dwarn:2 dfail:0 fail:0 skip:38
>> ivb-t430s total:143 pass:137 dwarn:0 dfail:0 fail:0 skip:6
>> skl-i5k-2 total:143 pass:134 dwarn:1 dfail:0 fail:0 skip:8
>> snb-dellxps total:143 pass:129 dwarn:0 dfail:0 fail:0 skip:14
>> snb-x220t total:143 pass:129 dwarn:0 dfail:0 fail:1 skip:13
>>
>> Results at /archive/results/CI_IGT_test/Patchwork_1256/
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
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-27 0:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 1:57 [PATCH v4] drm/i915: edp resume/On time optimization abhay.kumar
2016-01-13 8:02 ` Kumar, Shobhit
2016-01-13 10:20 ` ✗ warning: Fi.CI.BAT Patchwork
2016-01-14 23:53 ` [PATCH v4] drm/i915: edp resume/On time optimization Kumar, Abhay
2016-01-19 22:37 ` Kumar, Abhay
2016-01-20 9:00 ` Daniel Vetter
2016-01-20 9:59 ` Kumar, Shobhit
2016-01-20 13:06 ` Ville Syrjälä
2016-01-21 12:17 ` Kumar, Abhay
2016-01-22 5:48 ` Kumar, Shobhit
2016-01-31 7:20 ` Kumar, Abhay
2016-01-23 1:39 ` [PATCH V5] " abhay.kumar
2016-02-12 1:58 ` Kumar, Abhay
2016-02-12 16:07 ` Daniel Vetter
2016-01-23 8:43 ` ✗ Fi.CI.BAT: failure for drm/i915: edp resume/On time optimization. (rev10) Patchwork
2016-01-26 11:36 ` Ville Syrjälä
2016-01-27 0:21 ` Kumar, Abhay [this message]
2016-01-28 12:32 ` ✗ Fi.CI.BAT: warning " 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=56A80D79.6020209@intel.com \
--to=abhay.kumar@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.com \
/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.