From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: failure for series starting with [01/27] drm/i915: Squelch very verbose error logging
Date: Fri, 06 Jul 2018 21:31:51 -0000 [thread overview]
Message-ID: <20180706213151.22157.49647@emeril.freedesktop.org> (raw)
In-Reply-To: <20180706065332.15214-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [01/27] drm/i915: Squelch very verbose error logging
URL : https://patchwork.freedesktop.org/series/46051/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_4441_full -> Patchwork_9560_full =
== Summary - FAILURE ==
Serious unknown changes coming with Patchwork_9560_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_9560_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_9560_full:
=== IGT changes ===
==== Possible regressions ====
igt@kms_flip_tiling@flip-to-x-tiled:
shard-glk: PASS -> FAIL
igt@kms_universal_plane@cursor-fb-leak-pipe-b:
shard-apl: PASS -> FAIL
==== Warnings ====
igt@gem_exec_schedule@deep-bsd2:
shard-kbl: PASS -> SKIP +1
igt@gem_mocs_settings@mocs-rc6-vebox:
shard-kbl: SKIP -> PASS +4
== Known issues ==
Here are the changes found in Patchwork_9560_full that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@drv_suspend@shrink:
shard-apl: PASS -> INCOMPLETE (fdo#103927)
igt@gem_exec_reloc@basic-wc-gtt-active:
shard-snb: PASS -> INCOMPLETE (fdo#105411)
igt@kms_atomic_transition@1x-modeset-transitions-nonblocking:
shard-glk: PASS -> FAIL (fdo#105703)
igt@kms_flip@2x-flip-vs-blocking-wf-vblank:
shard-glk: PASS -> FAIL (fdo#100368)
igt@kms_flip@2x-flip-vs-expired-vblank:
shard-glk: PASS -> FAIL (fdo#105363)
igt@kms_flip_tiling@flip-x-tiled:
shard-glk: PASS -> FAIL (fdo#103822)
igt@kms_setmode@basic:
shard-apl: PASS -> FAIL (fdo#99912)
==== Possible fixes ====
igt@kms_flip@2x-plain-flip-ts-check:
shard-glk: FAIL -> PASS
igt@kms_setmode@basic:
shard-hsw: FAIL (fdo#99912) -> PASS
shard-kbl: FAIL (fdo#99912) -> PASS
==== Warnings ====
igt@drv_selftest@live_gtt:
shard-kbl: INCOMPLETE (fdo#107127, fdo#103665) -> FAIL (fdo#107127, fdo#105347)
fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
fdo#103665 https://bugs.freedesktop.org/show_bug.cgi?id=103665
fdo#103822 https://bugs.freedesktop.org/show_bug.cgi?id=103822
fdo#103927 https://bugs.freedesktop.org/show_bug.cgi?id=103927
fdo#105347 https://bugs.freedesktop.org/show_bug.cgi?id=105347
fdo#105363 https://bugs.freedesktop.org/show_bug.cgi?id=105363
fdo#105411 https://bugs.freedesktop.org/show_bug.cgi?id=105411
fdo#105703 https://bugs.freedesktop.org/show_bug.cgi?id=105703
fdo#107127 https://bugs.freedesktop.org/show_bug.cgi?id=107127
fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
== Participating hosts (5 -> 5) ==
No changes in participating hosts
== Build changes ==
* Linux: CI_DRM_4441 -> Patchwork_9560
CI_DRM_4441: 3fe30c1d16d414ebf8c3ca95af28add100b7975e @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4539: 8b3cc74c6911e9b2835fe6e160f84bae463a70ef @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9560: d45b72b8650c7c419f054cdf4503b54d133a46ca @ 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_9560/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-07-06 21:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 6:53 [PATCH 01/27] drm/i915: Squelch very verbose error logging Chris Wilson
2018-07-06 6:53 ` [PATCH 02/27] drm/i915/selftests: Destroy partial tiling vma after use Chris Wilson
2018-07-06 8:52 ` Matthew Auld
2018-07-06 6:53 ` [PATCH 03/27] drm/i915/selftests: Skip using the GPU if wedged Chris Wilson
2018-07-06 9:05 ` Matthew Auld
2018-07-06 6:53 ` [PATCH 04/27] drm/i915/selftests: Skip making an object busy if the GPU is wedged Chris Wilson
2018-07-06 9:10 ` Matthew Auld
2018-07-06 6:53 ` [PATCH 05/27] drm/i915/selftests: Skip all request selftests when wedged Chris Wilson
2018-07-06 9:11 ` Matthew Auld
2018-07-06 6:53 ` [PATCH 06/27] drm/i915/selftests: Skip workaround tests " Chris Wilson
2018-07-06 9:13 ` Matthew Auld
2018-07-06 6:53 ` [PATCH 07/27] drm/i915/selftests: Skip live eviction " Chris Wilson
2018-07-06 9:15 ` Matthew Auld
2018-07-06 6:53 ` [PATCH 08/27] drm/i915/selftests: Skip huge pages live tests if wedged Chris Wilson
2018-07-06 8:30 ` Matthew Auld
2018-07-06 6:53 ` [PATCH 09/27] drm/i915/selftests: Skip over live context testing when wedged Chris Wilson
2018-07-06 9:18 ` Matthew Auld
2018-07-06 6:53 ` [PATCH 10/27] drm/i915/selftests: Skip live context execution test without logical contexts Chris Wilson
2018-07-06 6:53 ` [PATCH 11/27] drm/i915: Refactor export_fence() after i915_vma_move_to_active() Chris Wilson
2018-07-06 6:53 ` [PATCH 12/27] drm/i915: Export i915_request_skip() Chris Wilson
2018-07-06 6:53 ` [PATCH 13/27] drm/i915: Start returning an error from i915_vma_move_to_active() Chris Wilson
2018-07-06 6:53 ` [PATCH 14/27] drm/i915: Move i915_vma_move_to_active() to i915_vma.c Chris Wilson
2018-07-06 6:53 ` [PATCH 15/27] drm/i915: Track vma activity per fence.context, not per engine Chris Wilson
2018-07-06 6:53 ` [PATCH 16/27] drm/i915: Track the last-active inside the i915_vma Chris Wilson
2018-07-06 6:53 ` [PATCH 17/27] drm/i915: Replace nested subclassing with explicit subclasses Chris Wilson
2018-07-06 13:17 ` Tvrtko Ursulin
2018-07-06 6:53 ` [PATCH 18/27] drm/i915: Only reset hangcheck at the start of an activity cycle Chris Wilson
2018-07-06 6:53 ` [PATCH 19/27] drm/i915: Stop tracking MRU activity on VMA Chris Wilson
2018-07-06 6:53 ` [PATCH 20/27] drm/i915: Introduce i915_address_space.mutex Chris Wilson
2018-07-06 6:53 ` [PATCH 21/27] drm/i915: Move fence register tracking to GGTT Chris Wilson
2018-07-06 6:53 ` [PATCH 22/27] drm/i915: Convert fences to use a GGTT lock rather than struct_mutex Chris Wilson
2018-07-06 6:53 ` [PATCH 23/27] drm/i915: Tidy i915_gem_suspend() Chris Wilson
2018-07-06 6:53 ` [PATCH 24/27] drm/i915: Move fence-reg interface to i915_gem_fence_reg.h Chris Wilson
2018-07-06 6:53 ` [PATCH 25/27] drm/i915: Dynamically allocate the array of drm_i915_gem_fence_reg Chris Wilson
2018-07-06 6:53 ` [PATCH 26/27] drm/i915: Pull all the reset functionality together into i915_reset.c Chris Wilson
2018-07-06 6:53 ` [PATCH 27/27] drm/i915: Remove GPU reset dependence on struct_mutex Chris Wilson
2018-07-06 7:33 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/27] drm/i915: Squelch very verbose error logging Patchwork
2018-07-06 7:43 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-07-06 7:50 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-06 9:00 ` [PATCH 01/27] " Matthew Auld
2018-07-06 21:31 ` 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=20180706213151.22157.49647@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).