From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for drm/i915: Show vma allocator stack when in doubt (rev4)
Date: Thu, 28 Jun 2018 16:16:23 -0000 [thread overview]
Message-ID: <20180628161623.19699.7837@emeril.freedesktop.org> (raw)
In-Reply-To: <20180628082615.10805-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915: Show vma allocator stack when in doubt (rev4)
URL : https://patchwork.freedesktop.org/series/45562/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4397_full -> Patchwork_9470_full =
== Summary - SUCCESS ==
No regressions found.
== Known issues ==
Here are the changes found in Patchwork_9470_full that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@drv_selftest@live_hangcheck:
shard-kbl: PASS -> DMESG-FAIL (fdo#106947, fdo#106560)
shard-apl: PASS -> DMESG-FAIL (fdo#106947, fdo#106560)
igt@drv_suspend@shrink:
shard-snb: PASS -> FAIL (fdo#106886)
igt@gem_mmap_gtt@coherency:
shard-glk: NOTRUN -> FAIL (fdo#100587)
igt@kms_available_modes_crc@available_mode_test_crc:
{shard-glk9}: NOTRUN -> FAIL (fdo#106641)
igt@kms_flip@2x-flip-vs-expired-vblank:
{shard-glk9}: NOTRUN -> FAIL (fdo#105363)
igt@kms_flip@2x-plain-flip-fb-recreate-interruptible:
shard-glk: NOTRUN -> FAIL (fdo#100368)
igt@perf_pmu@busy-accuracy-98-vcs1:
shard-snb: NOTRUN -> INCOMPLETE (fdo#105411)
==== Possible fixes ====
igt@gem_exec_schedule@preemptive-hang-render:
shard-snb: INCOMPLETE (fdo#105411) -> SKIP
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
fdo#100587 https://bugs.freedesktop.org/show_bug.cgi?id=100587
fdo#105363 https://bugs.freedesktop.org/show_bug.cgi?id=105363
fdo#105411 https://bugs.freedesktop.org/show_bug.cgi?id=105411
fdo#106560 https://bugs.freedesktop.org/show_bug.cgi?id=106560
fdo#106641 https://bugs.freedesktop.org/show_bug.cgi?id=106641
fdo#106886 https://bugs.freedesktop.org/show_bug.cgi?id=106886
fdo#106947 https://bugs.freedesktop.org/show_bug.cgi?id=106947
== Participating hosts (6 -> 6) ==
No changes in participating hosts
== Build changes ==
* Linux: CI_DRM_4397 -> Patchwork_9470
CI_DRM_4397: 7306233935b0e426454e8adcf09a8022faa03cbc @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4530: 0e98bf69f146eb72fe3a7c3b19a049b5786f0ca3 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9470: 41116ddd6b73c10a63409baea4d9a435221b4754 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9470/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-06-28 16:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 8:26 [PATCH] drm/i915: Show vma allocator stack when in doubt Chris Wilson
2018-06-28 8:55 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-06-28 9:00 ` Chris Wilson
2018-06-28 9:02 ` [PATCH v2] " Chris Wilson
2018-06-28 9:33 ` ✓ Fi.CI.BAT: success for drm/i915: Show vma allocator stack when in doubt (rev2) Patchwork
2018-06-28 9:43 ` [PATCH v3] drm/i915: Show vma allocator stack when in doubt Chris Wilson
2018-06-28 10:16 ` ✗ Fi.CI.BAT: failure for drm/i915: Show vma allocator stack when in doubt (rev3) Patchwork
2018-06-28 13:22 ` [PATCH v4] drm/i915: Show vma allocator stack when in doubt Chris Wilson
2018-06-28 13:42 ` Mika Kuoppala
2018-06-28 14:09 ` ✓ Fi.CI.BAT: success for drm/i915: Show vma allocator stack when in doubt (rev4) Patchwork
2018-06-28 16:16 ` 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=20180628161623.19699.7837@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).