From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for series starting with [1/5] drm/i915: Rename local struct intel_engine_cs variables
Date: Wed, 16 Mar 2016 15:45:08 +0000 [thread overview]
Message-ID: <56E97F84.6040501@linux.intel.com> (raw)
In-Reply-To: <20160316154026.GO4329@intel.com>
On 16/03/16 15:40, Ville Syrjälä wrote:
> On Wed, Mar 16, 2016 at 03:35:13PM +0000, Tvrtko Ursulin wrote:
>>
>> On 16/03/16 15:01, Patchwork wrote:
>>> == Series Details ==
>>>
>>> Series: series starting with [1/5] drm/i915: Rename local struct intel_engine_cs variables
>>> URL : https://patchwork.freedesktop.org/series/4508/
>>> State : failure
>>>
>>> == Summary ==
>>>
>>> Series 4508v1 Series without cover letter
>>> http://patchwork.freedesktop.org/api/1.0/series/4508/revisions/1/mbox/
>>>
>>> Test drv_module_reload_basic:
>>> skip -> PASS (bdw-nuci7)
>>> Test kms_flip:
>>> Subgroup basic-flip-vs-wf_vblank:
>>> pass -> FAIL (ivb-t430s)
>>
>> Unrelated https://bugs.freedesktop.org/show_bug.cgi?id=94294
>
> I'd like people to add a bit more information to these analysis mails.
> If there's just the bugzilla link I actually have to open it before
> I can see what the problem was. Makes it harder to keep on top what
> the most common BAT problems are.
Yeah in principle I agree but some of these are the usual suspects which
have been dragging for so long it would take an iron will (or something
nastier) to keep repeating the same analysis over and over again.
Sometimes I remember and add a link to new CI logs to the relevant BZ
instance which is probably more useful for people looking at BAT marked
entries (which are all critical anyway) to gather enough data points
when debugging.
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-16 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 11:00 [PATCH 1/5] drm/i915: Rename local struct intel_engine_cs variables Tvrtko Ursulin
2016-03-16 11:00 ` [PATCH 2/5] drm/i915: Rename intel_engine_cs function parameters Tvrtko Ursulin
2016-03-16 11:00 ` [PATCH 3/5] drm/i915: Rename intel_engine_cs struct members Tvrtko Ursulin
2016-03-16 11:00 ` [PATCH 4/5] drm/i915: More intel_engine_cs renaming Tvrtko Ursulin
2016-03-16 11:00 ` [PATCH 5/5] drm/i915: More renaming of rings to engines Tvrtko Ursulin
2016-03-16 11:15 ` Chris Wilson
2016-03-16 15:01 ` ✗ Fi.CI.BAT: failure for series starting with [1/5] drm/i915: Rename local struct intel_engine_cs variables Patchwork
2016-03-16 15:35 ` Tvrtko Ursulin
2016-03-16 15:40 ` Ville Syrjälä
2016-03-16 15:45 ` Tvrtko Ursulin [this message]
2016-03-16 15:56 ` Daniel Vetter
2016-03-16 16:40 ` Tvrtko Ursulin
2016-03-16 16:14 ` Ville Syrjälä
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=56E97F84.6040501@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox