From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Ausmus, James" <james.ausmus@intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Handle drm-layer errors in intel_dp_add_mst_connector (rev6)
Date: Tue, 17 Oct 2017 13:11:02 +0300 [thread overview]
Message-ID: <20171017101102.GP10981@intel.com> (raw)
In-Reply-To: <CAA1Hj7TOfY3eaJtvvTn4kQWTsW5Dy7LHQJ66rfVMkkCXRYieMQ@mail.gmail.com>
On Mon, Oct 16, 2017 at 04:04:40PM -0700, Ausmus, James wrote:
> On Fri, Oct 13, 2017 at 8:35 PM, Patchwork
> <patchwork@emeril.freedesktop.org> wrote:
> > == Series Details ==
> >
> > Series: drm/i915: Handle drm-layer errors in intel_dp_add_mst_connector (rev6)
> > URL : https://patchwork.freedesktop.org/series/30384/
> > State : failure
> >
> > == Summary ==
> >
> > Test kms_flip:
> > Subgroup basic-flip-vs-wf_vblank:
> > pass -> FAIL (shard-hsw)
> >
> > shard-hsw total:2553 pass:1440 dwarn:1 dfail:0 fail:9 skip:1103 time:9649s
> >
> > == Logs ==
> >
> > For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_6031/shards.html
>
> I'm not seeing how this failure could relate to the patch involved -
> am I missing something, or was this a fluke?
Yeah, we just missed the target by one frame for some reason. Doesn't
look like that particular test has been flaky before though. But then
again the history for shard runs isn't very long so it's hard to say
for sure how frequent this might be.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-10-17 10:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 19:59 [PATCH] drm/i915: Handle drm-layer errors in intel_dp_add_mst_connector James Ausmus
2017-09-14 20:19 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-09-15 5:48 ` ✓ Fi.CI.IGT: " Patchwork
2017-09-15 10:18 ` [PATCH] " Ville Syrjälä
2017-09-15 17:12 ` Ausmus, James
2017-09-15 17:49 ` [PATCH v2] " James Ausmus
2017-09-15 18:09 ` Ville Syrjälä
2017-09-15 19:43 ` Ausmus, James
2017-09-15 18:09 ` ✓ Fi.CI.BAT: success for drm/i915: Handle drm-layer errors in intel_dp_add_mst_connector (rev2) Patchwork
2017-09-15 19:42 ` [PATCH v3] drm/i915: Handle drm-layer errors in intel_dp_add_mst_connector James Ausmus
2017-09-15 19:43 ` ✓ Fi.CI.IGT: success for drm/i915: Handle drm-layer errors in intel_dp_add_mst_connector (rev2) Patchwork
2017-09-15 20:04 ` ✓ Fi.CI.BAT: success for drm/i915: Handle drm-layer errors in intel_dp_add_mst_connector (rev3) Patchwork
2017-09-15 21:26 ` ✓ Fi.CI.IGT: " Patchwork
2017-09-27 18:29 ` [PATCH v4 1/2] drm/i915: Handle drm-layer errors in intel_dp_add_mst_connector James Ausmus
2017-09-27 18:29 ` [PATCH 2/2] drm/i915: Use for_each_pipe in intel_dp_mst.c James Ausmus
2017-10-12 18:59 ` [PATCH v4 1/2] drm/i915: Handle drm-layer errors in intel_dp_add_mst_connector Ausmus, James
2017-10-13 18:01 ` [PATCH v5] " James Ausmus
2017-10-17 15:38 ` Ville Syrjälä
2017-10-17 16:46 ` James Ausmus
2017-10-13 18:26 ` ✓ Fi.CI.BAT: success for drm/i915: Handle drm-layer errors in intel_dp_add_mst_connector (rev6) Patchwork
2017-10-14 3:35 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-10-16 23:04 ` Ausmus, James
2017-10-17 10:11 ` Ville Syrjälä [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=20171017101102.GP10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=james.ausmus@intel.com \
/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