From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/i915: Show vma allocator stack when in doubt (rev3)
Date: Thu, 28 Jun 2018 10:16:55 -0000 [thread overview]
Message-ID: <20180628101655.19699.75606@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 (rev3)
URL : https://patchwork.freedesktop.org/series/45562/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_4396 -> Patchwork_9462 =
== Summary - FAILURE ==
Serious unknown changes coming with Patchwork_9462 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_9462, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://patchwork.freedesktop.org/api/1.0/series/45562/revisions/3/mbox/
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_9462:
=== IGT changes ===
==== Possible regressions ====
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
fi-skl-6600u: PASS -> DMESG-WARN +4
== Known issues ==
Here are the changes found in Patchwork_9462 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@drv_module_reload@basic-reload:
fi-skl-6600u: PASS -> DMESG-WARN (fdo#106697)
igt@gem_exec_suspend@basic-s4-devices:
fi-kbl-7500u: PASS -> DMESG-WARN (fdo#105128)
fdo#105128 https://bugs.freedesktop.org/show_bug.cgi?id=105128
fdo#106697 https://bugs.freedesktop.org/show_bug.cgi?id=106697
== Participating hosts (43 -> 38) ==
Missing (5): fi-ctg-p8600 fi-kbl-7560u fi-byt-squawks fi-ilk-m540 fi-hsw-4200u
== Build changes ==
* Linux: CI_DRM_4396 -> Patchwork_9462
CI_DRM_4396: dd5f49f9686f412baa426502d417ac74a37fc77e @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4530: 0e98bf69f146eb72fe3a7c3b19a049b5786f0ca3 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9462: 0baf797439ce8499f92211da1b442b6ca94dd283 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
0baf797439ce drm/i915: Show vma allocator stack when in doubt
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9462/issues.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-06-28 10: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 ` Patchwork [this message]
2018-06-28 13:22 ` [PATCH v4] " 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 ` ✓ Fi.CI.IGT: " 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=20180628101655.19699.75606@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).