From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for series starting with [1/6] drm/i915: Use drm_connector_list_iter in debugfs
Date: Mon, 13 Mar 2017 10:54:18 +0200 [thread overview]
Message-ID: <87tw6xftfp.fsf@intel.com> (raw)
In-Reply-To: <20170313083719.5kkaacexogdrhe73@phenom.ffwll.local>
On Mon, 13 Mar 2017, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Thu, Mar 09, 2017 at 12:48:56PM +0200, Jani Nikula wrote:
>> 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...
>
> I quickly looked, didn't find it, trybot was easier (but annoying that the
> priority is lower and the queue almost always full until Europe goes to
> sleep).
The downside with sending to trybot is that if you push the patches that
were actually tested, they'll get a broken Link: tag.
Figured it out. You need to go to the series view, select the series you
want to test, and after that a "Test again" button will show up at the
top. (Yes. Don't get me started.)
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-03-13 8:54 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
2017-03-13 8:37 ` Daniel Vetter
2017-03-13 8:54 ` Jani Nikula [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=87tw6xftfp.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.