public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: failure for drm/i915: Use enum plane_id for frontbuffer tracking
Date: Wed, 24 Jan 2018 04:04:49 -0000	[thread overview]
Message-ID: <20180124040449.27058.2381@emeril.freedesktop.org> (raw)
In-Reply-To: <20180123183343.9181-1-ville.syrjala@linux.intel.com>

== Series Details ==

Series: drm/i915: Use enum plane_id for frontbuffer tracking
URL   : https://patchwork.freedesktop.org/series/36991/
State : failure

== Summary ==

Test kms_flip:
        Subgroup 2x-wf_vblank-ts-check-interruptible:
                pass       -> FAIL       (shard-hsw)
        Subgroup flip-vs-expired-vblank-interruptible:
                fail       -> PASS       (shard-hsw) fdo#102887
        Subgroup vblank-vs-modeset-suspend:
                pass       -> SKIP       (shard-snb) fdo#102365 +1
        Subgroup vblank-vs-modeset-suspend-interruptible:
                pass       -> DMESG-WARN (shard-snb)
        Subgroup plain-flip-fb-recreate-interruptible:
                pass       -> FAIL       (shard-hsw) fdo#100368
Test kms_sysfs_edid_timing:
                warn       -> PASS       (shard-apl) fdo#100047
Test gem_softpin:
        Subgroup noreloc-s4:
                fail       -> SKIP       (shard-snb) fdo#103375
Test perf:
        Subgroup buffer-fill:
                pass       -> FAIL       (shard-apl) fdo#103755

fdo#102887 https://bugs.freedesktop.org/show_bug.cgi?id=102887
fdo#102365 https://bugs.freedesktop.org/show_bug.cgi?id=102365
fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
fdo#100047 https://bugs.freedesktop.org/show_bug.cgi?id=100047
fdo#103375 https://bugs.freedesktop.org/show_bug.cgi?id=103375
fdo#103755 https://bugs.freedesktop.org/show_bug.cgi?id=103755

shard-apl        total:2753 pass:1716 dwarn:1   dfail:0   fail:23  skip:1013 time:14064s
shard-hsw        total:2753 pass:1723 dwarn:1   dfail:0   fail:13  skip:1015 time:15328s
shard-snb        total:2753 pass:1317 dwarn:2   dfail:0   fail:9   skip:1425 time:7847s
Blacklisted hosts:
shard-kbl        total:2753 pass:1821 dwarn:16  dfail:1   fail:24  skip:891 time:11113s

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7755/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-01-24  4:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 18:33 [PATCH] drm/i915: Use enum plane_id for frontbuffer tracking Ville Syrjala
2018-01-23 19:00 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-01-23 21:11 ` [PATCH] " Chris Wilson
2018-01-24 17:36   ` Ville Syrjälä
2018-01-24 18:19     ` Ville Syrjälä
2018-01-23 21:12 ` Chris Wilson
2018-01-24  4:04 ` Patchwork [this message]
2018-01-24 17:09   ` ✗ Fi.CI.IGT: failure for " Ville Syrjälä
2018-01-24  4:16 ` [PATCH] " Pandiyan, Dhinakaran
2018-01-24 15:16   ` Ville Syrjälä
2018-01-24 19:03     ` Pandiyan, Dhinakaran

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=20180124040449.27058.2381@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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