All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Enable atomic for VLV/CHV
Date: Fri, 3 Mar 2017 21:17:10 +0200	[thread overview]
Message-ID: <20170303191710.GS31595@intel.com> (raw)
In-Reply-To: <20170303164728.30583.98776@emeril.freedesktop.org>

On Fri, Mar 03, 2017 at 04:47:28PM -0000, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/i915: Enable atomic for VLV/CHV
> URL   : https://patchwork.freedesktop.org/series/20634/
> State : failure
> 
> == Summary ==
> 
> Series 20634v1 drm/i915: Enable atomic for VLV/CHV
> https://patchwork.freedesktop.org/api/1.0/series/20634/revisions/1/mbox/
> 
> Test drv_module_reload:
>         Subgroup basic-reload-final:
>                 pass       -> DMESG-WARN (fi-skl-6770hq)
> Test kms_cursor_legacy:
>         Subgroup basic-busy-flip-before-cursor-atomic:
>                 skip       -> PASS       (fi-bsw-n3050)
>                 skip       -> FAIL       (fi-byt-n2820)
>                 skip       -> PASS       (fi-byt-j1900)
>         Subgroup basic-busy-flip-before-cursor-legacy:
>                 pass       -> FAIL       (fi-byt-n2820)
>         Subgroup basic-flip-after-cursor-atomic:
>                 skip       -> PASS       (fi-bsw-n3050)
>                 skip       -> FAIL       (fi-byt-n2820)
>                 skip       -> PASS       (fi-byt-j1900)
>         Subgroup basic-flip-after-cursor-legacy:
>                 pass       -> FAIL       (fi-byt-n2820)
>         Subgroup basic-flip-after-cursor-varying-size:
>                 pass       -> FAIL       (fi-byt-n2820)
>         Subgroup basic-flip-before-cursor-atomic:
>                 skip       -> PASS       (fi-bsw-n3050)
>                 skip       -> FAIL       (fi-byt-n2820)
>                 skip       -> PASS       (fi-byt-j1900)
>         Subgroup basic-flip-before-cursor-legacy:
>                 pass       -> FAIL       (fi-byt-n2820)
>         Subgroup basic-flip-before-cursor-varying-size:
>                 pass       -> FAIL       (fi-byt-n2820)

Hmm. I wonder what's bogging that guy down. This seems to pass on my
n2820 just fine.

> 
> fi-bdw-5557u     total:278  pass:267  dwarn:0   dfail:0   fail:0   skip:11 
> fi-bsw-n3050     total:278  pass:242  dwarn:0   dfail:0   fail:0   skip:36 
> fi-bxt-j4205     total:278  pass:259  dwarn:0   dfail:0   fail:0   skip:19 
> fi-bxt-t5700     total:278  pass:258  dwarn:0   dfail:0   fail:0   skip:20 
> fi-byt-j1900     total:278  pass:254  dwarn:0   dfail:0   fail:0   skip:24 
> fi-byt-n2820     total:278  pass:242  dwarn:0   dfail:0   fail:8   skip:28 
> fi-hsw-4770      total:278  pass:262  dwarn:0   dfail:0   fail:0   skip:16 
> fi-hsw-4770r     total:278  pass:262  dwarn:0   dfail:0   fail:0   skip:16 
> fi-ilk-650       total:278  pass:228  dwarn:0   dfail:0   fail:0   skip:50 
> fi-ivb-3520m     total:278  pass:260  dwarn:0   dfail:0   fail:0   skip:18 
> fi-ivb-3770      total:278  pass:260  dwarn:0   dfail:0   fail:0   skip:18 
> fi-kbl-7500u     total:278  pass:259  dwarn:1   dfail:0   fail:0   skip:18 
> fi-skl-6260u     total:278  pass:268  dwarn:0   dfail:0   fail:0   skip:10 
> fi-skl-6700hq    total:278  pass:261  dwarn:0   dfail:0   fail:0   skip:17 
> fi-skl-6700k     total:278  pass:256  dwarn:4   dfail:0   fail:0   skip:18 
> fi-skl-6770hq    total:278  pass:267  dwarn:1   dfail:0   fail:0   skip:10 
> fi-snb-2520m     total:278  pass:250  dwarn:0   dfail:0   fail:0   skip:28 
> fi-snb-2600      total:278  pass:249  dwarn:0   dfail:0   fail:0   skip:29 
> 
> 1d7915e7823628a0d548c6ecc5ad5b9a4ae4a6ff drm-tip: 2017y-03m-03d-15h-54m-06s UTC integration manifest
> e288b5f drm/i915: Enable atomic on VLV/CHV
> f58f60d drm/i915: Use intel_wm_plane_visible() on VLV/CHV as well
> 26ed515 drm/i915: Check for id==PLANE_CURSOR instead of type==DRM_PLANE_TYPE_CURSOR
> a6d3070 drm/i915: Extract intel_wm_plane_visible()
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_4056/

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-03-03 19:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 15:19 [PATCH 0/4] drm/i915: Enable atomic for VLV/CHV ville.syrjala
2017-03-03 15:19 ` [PATCH 1/4] drm/i915: Extract intel_wm_plane_visible() ville.syrjala
2017-03-17 19:52   ` Chris Wilson
2017-03-03 15:19 ` [PATCH 2/4] drm/i915: Check for id==PLANE_CURSOR instead of type==DRM_PLANE_TYPE_CURSOR ville.syrjala
2017-03-17 19:54   ` Chris Wilson
2017-03-17 20:01     ` Ville Syrjälä
2017-03-17 19:56   ` Chris Wilson
2017-03-03 15:19 ` [PATCH 3/4] drm/i915: Use intel_wm_plane_visible() on VLV/CHV as well ville.syrjala
2017-03-17 19:55   ` Chris Wilson
2017-03-03 15:19 ` [PATCH 4/4] drm/i915: Enable atomic on VLV/CHV ville.syrjala
2017-03-06  7:05   ` Maarten Lankhorst
2017-03-03 16:47 ` ✗ Fi.CI.BAT: failure for drm/i915: Enable atomic for VLV/CHV Patchwork
2017-03-03 19:17   ` Ville Syrjälä [this message]
2017-03-06 15:48 ` Patchwork
2017-03-15 17:29 ` Patchwork
2017-03-20 19:00 ` Patchwork
2017-03-21 14:31 ` Patchwork
2017-04-04 17:34 ` ✓ Fi.CI.BAT: success " Patchwork
2017-04-05 10:30   ` 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=20170303191710.GS31595@intel.com \
    --to=ville.syrjala@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 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.