From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: warning for drm: rework delayed connector cleanup in connector_iter (rev2)
Date: Wed, 13 Dec 2017 17:30:08 -0000 [thread overview]
Message-ID: <20171213173008.10061.29462@emeril.freedesktop.org> (raw)
In-Reply-To: <20171213104553.30821-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: drm: rework delayed connector cleanup in connector_iter (rev2)
URL : https://patchwork.freedesktop.org/series/35282/
State : warning
== Summary ==
Warning: bzip CI_DRM_3507/shard-glkb6/results33.json.bz2 wasn't in correct JSON format
Test kms_setmode:
Subgroup basic:
pass -> FAIL (shard-hsw) fdo#99912
Test kms_cursor_crc:
Subgroup cursor-256x256-suspend:
pass -> SKIP (shard-snb) fdo#103375 +2
Subgroup cursor-256x256-offscreen:
pass -> SKIP (shard-hsw)
Test kms_frontbuffer_tracking:
Subgroup fbc-1p-offscren-pri-shrfb-draw-blt:
pass -> FAIL (shard-snb) fdo#101623 +1
Subgroup fbc-1p-primscrn-pri-shrfb-draw-render:
pass -> FAIL (shard-hsw) fdo#103167
Test kms_flip:
Subgroup blt-wf_vblank-vs-dpms:
pass -> SKIP (shard-hsw) fdo#102614
Subgroup flip-vs-dpms-interruptible:
pass -> SKIP (shard-hsw)
Test kms_pipe_crc_basic:
Subgroup hang-read-crc-pipe-a:
pass -> SKIP (shard-hsw)
Test kms_busy:
Subgroup extended-modeset-hang-oldfb-render-b:
pass -> SKIP (shard-hsw)
Test kms_draw_crc:
Subgroup draw-method-xrgb2101010-blt-xtiled:
pass -> SKIP (shard-hsw)
fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
fdo#103375 https://bugs.freedesktop.org/show_bug.cgi?id=103375
fdo#101623 https://bugs.freedesktop.org/show_bug.cgi?id=101623
fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
fdo#102614 https://bugs.freedesktop.org/show_bug.cgi?id=102614
shard-hsw total:2712 pass:1529 dwarn:1 dfail:0 fail:11 skip:1171 time:9152s
shard-snb total:2636 pass:1277 dwarn:1 dfail:0 fail:13 skip:1345 time:7954s
Blacklisted hosts:
shard-apl total:2694 pass:1675 dwarn:1 dfail:0 fail:21 skip:996 time:13516s
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7483/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-12-13 17:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171213104607epcas4p420c1a7a83a19c1924318207c0bb2e8e2@epcas4p4.samsung.com>
2017-12-13 10:45 ` [PATCH] drm: rework delayed connector cleanup in connector_iter Daniel Vetter
2017-12-13 10:45 ` Daniel Vetter
2017-12-13 11:04 ` Chris Wilson
2017-12-13 11:04 ` Chris Wilson
2017-12-13 11:48 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-12-13 12:27 ` [PATCH] " Marek Szyprowski
2017-12-13 12:49 ` Daniel Vetter
2017-12-13 12:49 ` Daniel Vetter
2017-12-13 13:01 ` Marek Szyprowski
2017-12-13 13:05 ` Chris Wilson
2017-12-13 13:05 ` Chris Wilson
2017-12-13 13:35 ` Daniel Vetter
2017-12-13 13:35 ` Daniel Vetter
2017-12-13 21:59 ` Daniel Vetter
2017-12-13 21:59 ` Daniel Vetter
2017-12-13 14:48 ` ✓ Fi.CI.BAT: success for drm: rework delayed connector cleanup in connector_iter (rev2) Patchwork
2017-12-13 17:30 ` Patchwork [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=20171213173008.10061.29462@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.