public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
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/2] drm/i915: Split execlists hardware status page initialisation from setup
Date: Wed, 13 Apr 2016 10:50:50 +0100	[thread overview]
Message-ID: <570E167A.4050506@linux.intel.com> (raw)
In-Reply-To: <20160412165401.10589.35232@emeril.freedesktop.org>


On 12/04/16 17:54, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [1/2] drm/i915: Split execlists hardware status page initialisation from setup
> URL   : https://patchwork.freedesktop.org/series/5596/
> State : failure
>
> == Summary ==
>
> Series 5596v1 Series without cover letter
> http://patchwork.freedesktop.org/api/1.0/series/5596/revisions/1/mbox/
>
> Test drv_module_reload_basic:
>                  pass       -> FAIL       (snb-dellxps)

This hasn't been filed so far and it failed once already in CI_DRM_1194​.

Failure are assertions in gem_exec_store after driver reload.

Filed a new BZ: https://bugs.freedesktop.org/show_bug.cgi?id=94914

> Test kms_flip:
>          Subgroup basic-flip-vs-wf_vblank:
>                  pass       -> FAIL       (ivb-t430s)

Old friend https://bugs.freedesktop.org/show_bug.cgi?id=94294

>
> bdw-nuci7        total:203  pass:191  dwarn:0   dfail:0   fail:0   skip:12
> bdw-ultra        total:203  pass:180  dwarn:0   dfail:0   fail:0   skip:23
> bsw-nuc-2        total:202  pass:163  dwarn:0   dfail:0   fail:0   skip:39
> byt-nuc          total:202  pass:164  dwarn:0   dfail:0   fail:0   skip:38
> hsw-brixbox      total:203  pass:179  dwarn:0   dfail:0   fail:0   skip:24
> hsw-gt2          total:203  pass:184  dwarn:0   dfail:0   fail:0   skip:19
> ivb-t430s        total:203  pass:174  dwarn:0   dfail:0   fail:1   skip:28
> skl-i7k-2        total:203  pass:178  dwarn:0   dfail:0   fail:0   skip:25
> skl-nuci5        total:203  pass:192  dwarn:0   dfail:0   fail:0   skip:11
> snb-dellxps      total:203  pass:164  dwarn:0   dfail:0   fail:1   skip:38
> snb-x220t        total:203  pass:165  dwarn:0   dfail:0   fail:1   skip:37
>
> Results at /archive/results/CI_IGT_test/Patchwork_1875/
>
> 42189a46296988a9e16b57dca9e25c227458888b drm-intel-nightly: 2016y-04m-12d-14h-35m-43s UTC integration manifest
> 6d8f2e9 drm/i915: Use new i915_gem_object_pin_map for LRC
> f1b4a09 drm/i915: Split execlists hardware status page initialisation from setup

Merged - thanks for the review.

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-04-13  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 14:40 [PATCH 1/2] drm/i915: Split execlists hardware status page initialisation from setup Tvrtko Ursulin
2016-04-12 14:40 ` [PATCH 2/2] drm/i915: Use new i915_gem_object_pin_map for LRC Tvrtko Ursulin
2016-04-12 15:09   ` Chris Wilson
2016-04-12 16:54 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: Split execlists hardware status page initialisation from setup Patchwork
2016-04-13  9:50   ` Tvrtko Ursulin [this message]

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=570E167A.4050506@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox