public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Manasi Navare <manasi.d.navare@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/dp: Add HBR3 support in existing DRM DP helpers
Date: Tue, 23 Jan 2018 06:03:38 -0000	[thread overview]
Message-ID: <20180123060338.32070.57120@emeril.freedesktop.org> (raw)
In-Reply-To: <1516660991-20697-1-git-send-email-manasi.d.navare@intel.com>

== Series Details ==

Series: series starting with [1/2] drm/dp: Add HBR3 support in existing DRM DP helpers
URL   : https://patchwork.freedesktop.org/series/36931/
State : failure

== Summary ==

Test kms_cursor_legacy:
        Subgroup short-flip-after-cursor-atomic-transitions:
                pass       -> FAIL       (shard-apl) fdo#103792
        Subgroup cursor-vs-flip-legacy:
                fail       -> PASS       (shard-apl) fdo#103355
Test kms_frontbuffer_tracking:
        Subgroup fbc-tilingchange:
                fail       -> PASS       (shard-apl)
        Subgroup fbc-1p-offscren-pri-shrfb-draw-render:
                fail       -> PASS       (shard-snb) fdo#101623
Test drv_suspend:
        Subgroup fence-restore-tiled2untiled-hibernate:
                fail       -> SKIP       (shard-snb) fdo#103375
Test kms_flip:
        Subgroup flip-vs-panning-vs-hang-interruptible:
                dmesg-warn -> PASS       (shard-snb) fdo#103821
        Subgroup vblank-vs-suspend-interruptible:
                pass       -> FAIL       (shard-apl) fdo#100368
Test pm_rpm:
        Subgroup gem-execbuf-stress:
                pass       -> INCOMPLETE (shard-hsw)

fdo#103792 https://bugs.freedesktop.org/show_bug.cgi?id=103792
fdo#103355 https://bugs.freedesktop.org/show_bug.cgi?id=103355
fdo#101623 https://bugs.freedesktop.org/show_bug.cgi?id=101623
fdo#103375 https://bugs.freedesktop.org/show_bug.cgi?id=103375
fdo#103821 https://bugs.freedesktop.org/show_bug.cgi?id=103821
fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368

shard-apl        total:2753 pass:1713 dwarn:1   dfail:0   fail:26  skip:1013 time:13962s
shard-hsw        total:2728 pass:1712 dwarn:1   dfail:0   fail:11  skip:1002 time:14880s
shard-snb        total:2753 pass:1319 dwarn:1   dfail:0   fail:9   skip:1424 time:7883s
Blacklisted hosts:
shard-kbl        total:2753 pass:1838 dwarn:1   dfail:1   fail:24  skip:889 time:10774s

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7747/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-23  6:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22 22:43 [PATCH 1/2] drm/dp: Add HBR3 support in existing DRM DP helpers Manasi Navare
2018-01-22 22:43 ` [PATCH 2/2] drm/dp: Add definitions for TPS4 bits and macros to check the support Manasi Navare
2018-01-22 23:03 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/dp: Add HBR3 support in existing DRM DP helpers Patchwork
2018-01-23  6:03 ` Patchwork [this message]
2018-01-23 14:47 ` [PATCH 1/2] " Harry Wentland
2018-01-26 11:38   ` 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=20180123060338.32070.57120@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=manasi.d.navare@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