From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Michał Winiarski" <michal.winiarski@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for drm/i915/guc: Don't try to enable GuC logging when we're not using GuC (rev3)
Date: Tue, 20 Mar 2018 14:52:05 -0000 [thread overview]
Message-ID: <20180320145205.32268.2129@emeril.freedesktop.org> (raw)
In-Reply-To: <20180320001337.23676-1-michal.winiarski@intel.com>
== Series Details ==
Series: drm/i915/guc: Don't try to enable GuC logging when we're not using GuC (rev3)
URL : https://patchwork.freedesktop.org/series/40239/
State : success
== Summary ==
---- Known issues:
Test kms_flip:
Subgroup flip-vs-expired-vblank-interruptible:
pass -> FAIL (shard-hsw) fdo#102887
Test kms_pipe_crc_basic:
Subgroup suspend-read-crc-pipe-c:
incomplete -> PASS (shard-hsw) fdo#103375
Test kms_sysfs_edid_timing:
warn -> PASS (shard-apl) fdo#100047
Test perf:
Subgroup polling:
fail -> PASS (shard-hsw) fdo#102252
fdo#102887 https://bugs.freedesktop.org/show_bug.cgi?id=102887
fdo#103375 https://bugs.freedesktop.org/show_bug.cgi?id=103375
fdo#100047 https://bugs.freedesktop.org/show_bug.cgi?id=100047
fdo#102252 https://bugs.freedesktop.org/show_bug.cgi?id=102252
shard-apl total:3478 pass:1815 dwarn:1 dfail:0 fail:7 skip:1655 time:13007s
shard-hsw total:3478 pass:1767 dwarn:1 dfail:0 fail:2 skip:1707 time:11713s
shard-snb total:3478 pass:1357 dwarn:1 dfail:0 fail:2 skip:2118 time:7143s
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_8413/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-20 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 0:13 [PATCH] drm/i915/guc: Don't try to enable GuC logging when we're not using GuC Michał Winiarski
2018-03-20 0:18 ` Chris Wilson
2018-03-20 1:20 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-03-20 6:00 ` ✗ Fi.CI.IGT: warning " Patchwork
2018-03-20 8:49 ` [PATCH v2] " Michał Winiarski
2018-03-20 11:00 ` Chris Wilson
2018-03-20 11:55 ` [PATCH v3] " Michał Winiarski
2018-03-20 9:16 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Don't try to enable GuC logging when we're not using GuC (rev2) Patchwork
2018-03-20 10:30 ` ✓ Fi.CI.IGT: " Patchwork
2018-03-20 12:31 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Don't try to enable GuC logging when we're not using GuC (rev3) Patchwork
2018-03-20 14:52 ` Patchwork [this message]
2018-03-20 14:55 ` ✓ Fi.CI.IGT: " Chris Wilson
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=20180320145205.32268.2129@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.winiarski@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 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.