From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Ro.CI.BAT: failure for drm/vgem: Attach sw fences to exported vGEM dma-buf (ioctl)
Date: Tue, 12 Jul 2016 16:13:18 -0000 [thread overview]
Message-ID: <20160712161318.12184.84320@emeril.freedesktop.org> (raw)
In-Reply-To: <1468327581-9579-1-git-send-email-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/vgem: Attach sw fences to exported vGEM dma-buf (ioctl)
URL : https://patchwork.freedesktop.org/series/9757/
State : failure
== Summary ==
Series 9757v1 drm/vgem: Attach sw fences to exported vGEM dma-buf (ioctl)
http://patchwork.freedesktop.org/api/1.0/series/9757/revisions/1/mbox
Test gem_sync:
Subgroup basic-store-each:
pass -> DMESG-FAIL (ro-bdw-i7-5600u)
Test kms_pipe_crc_basic:
Subgroup suspend-read-crc-pipe-a:
dmesg-warn -> SKIP (ro-bdw-i7-5557U)
fi-kbl-qkkr total:237 pass:174 dwarn:27 dfail:1 fail:7 skip:28
fi-skl-i5-6260u total:237 pass:218 dwarn:0 dfail:0 fail:7 skip:12
fi-skl-i7-6700k total:237 pass:204 dwarn:0 dfail:0 fail:7 skip:26
fi-snb-i7-2600 total:237 pass:190 dwarn:0 dfail:0 fail:7 skip:40
ro-bdw-i5-5250u total:237 pass:213 dwarn:1 dfail:0 fail:7 skip:16
ro-bdw-i7-5557U total:237 pass:213 dwarn:1 dfail:0 fail:7 skip:16
ro-bdw-i7-5600u total:237 pass:198 dwarn:0 dfail:1 fail:7 skip:31
ro-bsw-n3050 total:217 pass:172 dwarn:0 dfail:0 fail:2 skip:42
ro-byt-n2820 total:237 pass:191 dwarn:0 dfail:0 fail:8 skip:38
ro-hsw-i3-4010u total:237 pass:206 dwarn:0 dfail:0 fail:7 skip:24
ro-hsw-i7-4770r total:237 pass:206 dwarn:0 dfail:0 fail:7 skip:24
ro-ilk-i7-620lm total:237 pass:166 dwarn:0 dfail:0 fail:8 skip:63
ro-ilk1-i5-650 total:232 pass:166 dwarn:0 dfail:0 fail:8 skip:58
ro-ivb-i7-3770 total:237 pass:197 dwarn:0 dfail:0 fail:7 skip:33
ro-skl3-i5-6260u total:237 pass:217 dwarn:1 dfail:0 fail:7 skip:12
ro-snb-i7-2620M total:237 pass:188 dwarn:0 dfail:0 fail:8 skip:41
Results at /archive/results/CI_IGT_test/RO_Patchwork_1474/
9561f5c drm-intel-nightly: 2016y-07m-12d-15h-14m-43s UTC integration manifest
befd5bc drm/vgem: Attach sw fences to exported vGEM dma-buf (ioctl)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-07-12 16:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 12:46 [PATCH v2] drm/vgem: Attach sw fences to exported vGEM dma-buf (ioctl) Chris Wilson
2016-07-12 16:13 ` Patchwork [this message]
2016-07-13 18:57 ` Chris Wilson
2016-07-13 20:29 ` Gustavo Padovan
2016-07-13 20:46 ` Chris Wilson
2016-07-14 7:04 ` [PATCH v3] " Chris Wilson
2016-07-14 8:12 ` Daniel Vetter
2016-07-14 9:59 ` Chris Wilson
2016-07-14 10:11 ` Chris Wilson
2016-07-14 12:15 ` [Intel-gfx] " Chris Wilson
2016-07-14 12:40 ` Daniel Vetter
2016-07-14 13:23 ` Chris Wilson
2016-07-14 13:39 ` Chris Wilson
2016-07-14 14:36 ` [Intel-gfx] " Daniel Vetter
2016-07-14 15:24 ` Chris Wilson
2016-07-15 7:08 ` [Intel-gfx] " Daniel Vetter
2016-07-14 14:33 ` Daniel Vetter
2016-07-15 8:31 ` [PATCH v4] " Chris Wilson
2016-07-18 6:34 ` Daniel Vetter
2016-07-15 9:15 ` ✗ Ro.CI.BAT: failure for drm/vgem: Attach sw fences to exported vGEM dma-buf (ioctl) (rev2) Patchwork
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=20160712161318.12184.84320@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--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.