From: Patchwork <patchwork@emeril.freedesktop.org>
To: Yaodong Li <yaodong.li@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: failure for drm/i915: Use correct reST syntax for WOPCM and GuC kernel-doc diagrams (rev2)
Date: Thu, 15 Mar 2018 01:27:23 -0000 [thread overview]
Message-ID: <20180315012723.32602.56981@emeril.freedesktop.org> (raw)
In-Reply-To: <1521053083-2693-1-git-send-email-yaodong.li@intel.com>
== Series Details ==
Series: drm/i915: Use correct reST syntax for WOPCM and GuC kernel-doc diagrams (rev2)
URL : https://patchwork.freedesktop.org/series/39979/
State : failure
== Summary ==
---- Possible new issues:
Test gem_exec_capture:
Subgroup capture-vebox:
pass -> FAIL (shard-apl)
Test kms_frontbuffer_tracking:
Subgroup fbc-1p-primscrn-pri-indfb-draw-mmap-wc:
pass -> FAIL (shard-apl)
Subgroup fbc-1p-primscrn-spr-indfb-draw-pwrite:
pass -> FAIL (shard-apl)
Test kms_vblank:
Subgroup pipe-a-ts-continuation-suspend:
skip -> PASS (shard-snb)
---- Known issues:
Test gem_eio:
Subgroup in-flight-contexts:
pass -> INCOMPLETE (shard-apl) fdo#105341
Test kms_flip:
Subgroup plain-flip-fb-recreate-interruptible:
fail -> PASS (shard-hsw) fdo#100368 +1
Test kms_sysfs_edid_timing:
warn -> PASS (shard-apl) fdo#100047
fdo#105341 https://bugs.freedesktop.org/show_bug.cgi?id=105341
fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
fdo#100047 https://bugs.freedesktop.org/show_bug.cgi?id=100047
shard-apl total:3286 pass:1721 dwarn:1 dfail:0 fail:9 skip:1553 time:11853s
shard-hsw total:3441 pass:1766 dwarn:1 dfail:0 fail:1 skip:1672 time:11890s
shard-snb total:3441 pass:1356 dwarn:1 dfail:0 fail:3 skip:2081 time:7165s
Blacklisted hosts:
shard-kbl total:3425 pass:1925 dwarn:1 dfail:0 fail:9 skip:1488 time:9042s
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_8351/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-15 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 18:44 [PATCH v2] drm/i915: Use correct reST syntax for WOPCM and GuC kernel-doc diagrams Jackie Li
2018-03-14 19:26 ` Michal Wajdeczko
2018-03-14 20:09 ` Yaodong Li
2018-03-14 19:30 ` ✓ Fi.CI.BAT: success for drm/i915: Use correct reST syntax for WOPCM and GuC kernel-doc diagrams (rev2) Patchwork
2018-03-15 1:27 ` Patchwork [this message]
2018-03-15 6:54 ` [PATCH v2] drm/i915: Use correct reST syntax for WOPCM and GuC kernel-doc diagrams Sagar Arun Kamble
2018-03-15 16:43 ` Yaodong Li
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=20180315012723.32602.56981@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=yaodong.li@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