All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: ✗ Fi.CI.BAT: failure for series starting with [1/6] drm/i915: Use drm_connector_list_iter in debugfs
Date: Thu, 09 Mar 2017 12:48:56 +0200	[thread overview]
Message-ID: <87fuimhgiv.fsf@intel.com> (raw)
In-Reply-To: <20170308224226.6tdo7jz7nxsqhkgo@phenom.ffwll.local>

On Thu, 09 Mar 2017, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Mar 01, 2017 at 10:52:35AM -0000, Patchwork wrote:
>> == Series Details ==
>> 
>> Series: series starting with [1/6] drm/i915: Use drm_connector_list_iter in debugfs
>> URL   : https://patchwork.freedesktop.org/series/20441/
>> State : failure
>> 
>> == Summary ==
>> 
>> Series 20441v1 Series without cover letter
>> https://patchwork.freedesktop.org/api/1.0/series/20441/revisions/1/mbox/
>> 
>> Test gem_ctx_create:
>>         Subgroup basic-files:
>>                 pass       -> INCOMPLETE (fi-bdw-5557u)
>> Test kms_busy:
>>         Subgroup basic-flip-default-a:
>>                 fail       -> PASS       (fi-byt-n2820)
>> Test kms_pipe_crc_basic:
>>         Subgroup nonblocking-crc-pipe-a:
>>                 pass       -> DMESG-WARN (fi-byt-n2820)
>
> Thrown at trybot to confirm these are unrelated flukes and merged with
> Maarten's irc-r-b for the remaining patches.

You should be able to request a re-run from the patchwork
interface. It's well hidden, but it's there somewhere...

BR,
Jani.


> -Daniel
>
>> 
>> fi-bdw-5557u     total:17   pass:16   dwarn:0   dfail:0   fail:0   skip:0  
>> fi-bsw-n3050     total:278  pass:239  dwarn:0   dfail:0   fail:0   skip:39 
>> fi-bxt-j4205     total:278  pass:259  dwarn:0   dfail:0   fail:0   skip:19 
>> fi-bxt-t5700     total:108  pass:95   dwarn:0   dfail:0   fail:0   skip:12 
>> fi-byt-j1900     total:278  pass:251  dwarn:0   dfail:0   fail:0   skip:27 
>> fi-byt-n2820     total:278  pass:246  dwarn:1   dfail:0   fail:0   skip:31 
>> 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:268  dwarn:0   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 
>> 
>> 5e40124690ed25976cb436f1a3f83ba657b8fafb drm-tip: 2017y-03m-01d-09h-46m-54s UTC integration manifest
>> eb43dd1 drm/i915: Fix up verify_encoder_state
>> ea8bbb3 drm/i915: use for_each_intel_connector_iter in intel_display.c
>> 87b27ca drm/i915: Make intel_get_pipe_from_connector atomic
>> d5d4e9b drm/i915: use drm_connector_list_iter in intel_opregion.c
>> ae16a12 drm/i915: use drm_connector_list_iter in intel_hotplug.c
>> 47814de drm/i915: Use drm_connector_list_iter in debugfs
>> 
>> == Logs ==
>> 
>> For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_4013/

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-03-09 10:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01  9:52 [PATCH 1/6] drm/i915: Use drm_connector_list_iter in debugfs Daniel Vetter
2017-03-01  9:52 ` [PATCH 2/6] drm/i915: use drm_connector_list_iter in intel_hotplug.c Daniel Vetter
2017-03-01  9:52 ` [PATCH 3/6] drm/i915: use drm_connector_list_iter in intel_opregion.c Daniel Vetter
2017-03-01  9:52 ` [PATCH 4/6] drm/i915: Make intel_get_pipe_from_connector atomic Daniel Vetter
2017-03-01  9:52 ` [PATCH 5/6] drm/i915: use for_each_intel_connector_iter in intel_display.c Daniel Vetter
2017-03-01  9:52 ` [PATCH 6/6] drm/i915: Fix up verify_encoder_state Daniel Vetter
2017-03-08  9:37   ` Maarten Lankhorst
2017-03-01 10:52 ` ✗ Fi.CI.BAT: failure for series starting with [1/6] drm/i915: Use drm_connector_list_iter in debugfs Patchwork
2017-03-08 22:42   ` Daniel Vetter
2017-03-09 10:48     ` Jani Nikula [this message]
2017-03-13  8:37       ` Daniel Vetter
2017-03-13  8:54         ` Jani Nikula

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=87fuimhgiv.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --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.