intel-gfx.lists.freedesktop.org archive mirror
 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:  success for drm/i915: Fake HDMI live status (rev3)
Date: Fri, 22 Apr 2016 20:23:38 +0300	[thread overview]
Message-ID: <20160422172338.GU4329@intel.com> (raw)
In-Reply-To: <20160421165428.29238.47731@emeril.freedesktop.org>

On Thu, Apr 21, 2016 at 04:54:28PM -0000, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/i915: Fake HDMI live status (rev3)
> URL   : https://patchwork.freedesktop.org/series/6038/
> State : success
> 
> == Summary ==
> 
> Series 6038v3 drm/i915: Fake HDMI live status
> http://patchwork.freedesktop.org/api/1.0/series/6038/revisions/3/mbox/
> 
> Test gem_busy:
>         Subgroup basic-blt:
>                 skip       -> PASS       (bsw-nuc-2)
> Test gem_sync:
>         Subgroup basic-render:
>                 pass       -> INCOMPLETE (bdw-nuci7) UNSTABLE

Hmm. Random machine death? Looking at the long term history this seems
to be semi-frequent on this machine.

> Test kms_pipe_crc_basic:
>         Subgroup hang-read-crc-pipe-c:
>                 incomplete -> PASS       (bdw-nuci7)
> 
> bdw-nuci7        total:176  pass:164  dwarn:0   dfail:0   fail:0   skip:11 
> bdw-ultra        total:194  pass:170  dwarn:0   dfail:0   fail:1   skip:23 
> bsw-nuc-2        total:193  pass:154  dwarn:0   dfail:0   fail:0   skip:39 
> byt-nuc          total:193  pass:155  dwarn:0   dfail:0   fail:0   skip:38 
> hsw-brixbox      total:194  pass:170  dwarn:0   dfail:0   fail:0   skip:24 
> hsw-gt2          total:194  pass:175  dwarn:0   dfail:0   fail:0   skip:19 
> ilk-hp8440p      total:194  pass:137  dwarn:0   dfail:0   fail:0   skip:57 
> ivb-t430s        total:194  pass:166  dwarn:0   dfail:0   fail:0   skip:28 
> skl-i7k-2        total:194  pass:168  dwarn:0   dfail:0   fail:1   skip:25 
> skl-nuci5        total:194  pass:183  dwarn:0   dfail:0   fail:0   skip:11 
> snb-dellxps      total:193  pass:155  dwarn:0   dfail:0   fail:0   skip:38 
> snb-x220t        total:193  pass:155  dwarn:0   dfail:0   fail:1   skip:37 
> 
> Results at /archive/results/CI_IGT_test/Patchwork_1977/
> 
> 9dabb0053b63bc32ab6ad5d13209d1e43395313f drm-intel-nightly: 2016y-04m-21d-09h-27m-12s UTC integration manifest
> 4bd2e76 drm/i915: Fake HDMI live status
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
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:[~2016-04-22 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 11:18 [PATCH v3] drm/i915: Fake HDMI live status Shashank Sharma
2016-04-21 12:14 ` Ville Syrjälä
2016-04-21 16:54 ` ✓ Fi.CI.BAT: success for drm/i915: Fake HDMI live status (rev3) Patchwork
2016-04-22 17:23   ` Ville Syrjälä [this message]
2016-04-22 17:34 ` [PATCH v3] drm/i915: Fake HDMI live status 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=20160422172338.GU4329@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).