On 16/03/16 15:56, Daniel Vetter wrote:
On Wed, Mar 16, 2016 at 4:45 PM, Tvrtko Ursulin
<tvrtko.ursulin@xxxxxxxxxxxxxxx> wrote:
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.
Someone is asking for a really nasty maintainer to provide motivation?
More seriously&honestly I'm not entirely sure how we can get out of
this "CI seems constantly broken" place :(
I've noticed people are working on some of those constant naggers so
perhaps there is light at the end of the tunnel.
Key is having the right hardware, and IMHO, assigning people to critical
BAT tagged Bugzilla's. There is plenty of those, with more or less links
to CI failure example, so it looks to me there is certainly enough
material already.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
