From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for series starting with [01/13] locking/lockdep: restore cross-release checks (rev7)
Date: Fri, 23 Nov 2018 14:12:46 -0000 [thread overview]
Message-ID: <20181123141246.3993.54846@emeril.freedesktop.org> (raw)
In-Reply-To: <20181107153019.26401-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: series starting with [01/13] locking/lockdep: restore cross-release checks (rev7)
URL : https://patchwork.freedesktop.org/series/52167/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_5195 -> Patchwork_10897 =
== Summary - FAILURE ==
Serious unknown changes coming with Patchwork_10897 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_10897, 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/52167/revisions/7/mbox/
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_10897:
=== IGT changes ===
==== Possible regressions ====
igt@gem_tiled_fence_blits@basic:
fi-apl-guc: PASS -> DMESG-WARN
fi-elk-e7500: PASS -> DMESG-WARN
fi-cfl-guc: PASS -> DMESG-WARN
fi-skl-6700hq: NOTRUN -> DMESG-WARN
fi-hsw-4770r: PASS -> DMESG-WARN
fi-kbl-x1275: PASS -> DMESG-WARN
fi-glk-dsi: PASS -> DMESG-WARN
fi-glk-j4005: PASS -> DMESG-WARN
{fi-kbl-7567u}: PASS -> DMESG-WARN
fi-hsw-4770: PASS -> DMESG-WARN
{fi-kbl-7500u}: PASS -> DMESG-WARN
fi-whl-u: PASS -> DMESG-WARN
fi-ivb-3770: PASS -> DMESG-WARN
fi-bxt-dsi: PASS -> DMESG-WARN
fi-skl-iommu: PASS -> DMESG-WARN
fi-skl-6770hq: PASS -> DMESG-WARN
fi-ilk-650: PASS -> DMESG-WARN
fi-cfl-8109u: PASS -> DMESG-WARN
fi-skl-guc: PASS -> DMESG-WARN
fi-kbl-guc: PASS -> DMESG-WARN
fi-skl-6600u: PASS -> DMESG-WARN
fi-kbl-7560u: PASS -> DMESG-WARN
igt@prime_vgem@basic-fence-flip:
fi-blb-e6850: PASS -> DMESG-WARN
{igt@runner@aborted}:
fi-ilk-650: NOTRUN -> FAIL
fi-cfl-8109u: NOTRUN -> FAIL
fi-glk-dsi: NOTRUN -> FAIL
fi-hsw-4770: NOTRUN -> FAIL
{fi-kbl-7500u}: NOTRUN -> FAIL
fi-skl-6700hq: NOTRUN -> FAIL
fi-whl-u: NOTRUN -> FAIL
fi-ivb-3770: NOTRUN -> FAIL
fi-kbl-7560u: NOTRUN -> FAIL
fi-bxt-dsi: NOTRUN -> FAIL
fi-skl-iommu: NOTRUN -> FAIL
fi-cfl-guc: NOTRUN -> FAIL
fi-glk-j4005: NOTRUN -> FAIL
{fi-kbl-7567u}: NOTRUN -> FAIL
fi-skl-guc: NOTRUN -> FAIL
fi-kbl-x1275: NOTRUN -> FAIL
fi-hsw-4770r: NOTRUN -> FAIL
fi-skl-6600u: NOTRUN -> FAIL
fi-apl-guc: NOTRUN -> FAIL
fi-skl-6770hq: NOTRUN -> FAIL
fi-kbl-guc: NOTRUN -> FAIL
fi-elk-e7500: NOTRUN -> FAIL
== Known issues ==
Here are the changes found in Patchwork_10897 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_ctx_switch@basic-default-heavy:
fi-icl-u2: PASS -> DMESG-WARN (fdo#107724)
igt@gem_exec_suspend@basic-s3:
fi-skl-6700k2: PASS -> INCOMPLETE (fdo#105524, fdo#104108, k.org#199541, fdo#107773)
igt@prime_vgem@basic-fence-flip:
fi-bdw-gvtdvm: PASS -> FAIL (fdo#103182)
==== Possible fixes ====
igt@gem_ctx_switch@basic-default:
fi-icl-u2: DMESG-WARN (fdo#107724) -> PASS
igt@i915_selftest@live_coherency:
fi-gdg-551: DMESG-FAIL (fdo#107164) -> PASS
igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence:
fi-byt-clapper: FAIL (fdo#103191, fdo#107362) -> PASS
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
fdo#103182 https://bugs.freedesktop.org/show_bug.cgi?id=103182
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#104108 https://bugs.freedesktop.org/show_bug.cgi?id=104108
fdo#105524 https://bugs.freedesktop.org/show_bug.cgi?id=105524
fdo#107164 https://bugs.freedesktop.org/show_bug.cgi?id=107164
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
fdo#107724 https://bugs.freedesktop.org/show_bug.cgi?id=107724
fdo#107773 https://bugs.freedesktop.org/show_bug.cgi?id=107773
k.org#199541 https://bugzilla.kernel.org/show_bug.cgi?id=199541
== Participating hosts (46 -> 41) ==
Additional (1): fi-skl-6700hq
Missing (6): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-u3
== Build changes ==
* Linux: CI_DRM_5195 -> Patchwork_10897
CI_DRM_5195: b6df470d38bf4580c00e3f5008d795ec2a901066 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4725: 9dc7c41d1c600133d6e3e63f1941c2e75d23bd3b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10897: 0a2238307a58d2a8ea5ce080def35469365b8cc1 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
0a2238307a58 Revert "locking/lockdep, cpu/hotplug: Annotate AP thread"
0c81db8403c2 HAX FOR CI: Enable cross-release
06397e4e6592 drm/i915: annotate intel_atomic_commit_fence_wait
697082174040 drm/i915: Annotate dma_fence waits
58bb1f3ee989 reservation: Annotate dma_fence waits
c1921f8ad940 dma-fence: cross-release annotations
2a288a5aa876 mm, notifier: Add a lockdep map for invalidate_range_start
ae78d029fb92 mm, notifier: Catch sleeping/blocking for !blockable
3cfce1971136 mm: Check if mmu notifier callbacks are allowed to fail
5e33a73d37ce kernel/lockdep: Make cross-release a config option
0e61dc89b9d4 lockdep: Remove GFP_NOLOCKDEP annotation
e41dae845069 kthread: finer-grained lockdep/cross-release completion
0449bd050c17 locking/lockdep: restore cross-release checks
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10897/issues.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-11-23 14:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 15:30 [PATCH 01/13] locking/lockdep: restore cross-release checks Daniel Vetter
2018-11-07 15:30 ` [PATCH 02/13] kthread: finer-grained lockdep/cross-release completion Daniel Vetter
2018-11-07 15:30 ` [PATCH 03/13] lockdep: Remove GFP_NOLOCKDEP annotation Daniel Vetter
2018-11-07 15:30 ` [PATCH 04/13] kernel/lockdep: Make cross-release a config option Daniel Vetter
2018-11-07 15:30 ` [PATCH 05/13] mm: Check if mmu notifier callbacks are allowed to fail Daniel Vetter
2018-11-07 15:30 ` [PATCH 06/13] mm, notifier: Catch sleeping/blocking for !blockable Daniel Vetter
2018-11-07 15:30 ` [PATCH 07/13] mm, notifier: Add a lockdep map for invalidate_range_start Daniel Vetter
2018-11-07 15:30 ` [PATCH 08/13] dma-fence: cross-release annotations Daniel Vetter
2018-11-07 15:30 ` [PATCH 09/13] reservation: Annotate dma_fence waits Daniel Vetter
2018-11-07 15:30 ` [PATCH 10/13] drm/i915: " Daniel Vetter
2018-11-07 15:30 ` [PATCH 11/13] drm/i915: annotate intel_atomic_commit_fence_wait Daniel Vetter
2018-11-07 15:30 ` [PATCH 12/13] HAX FOR CI: Enable cross-release Daniel Vetter
2018-11-08 9:31 ` [PATCH] " Daniel Vetter
2018-11-08 9:41 ` Chris Wilson
2018-11-20 11:00 ` Daniel Vetter
2018-11-20 10:58 ` Daniel Vetter
2018-11-22 16:35 ` Daniel Vetter
2018-11-23 8:53 ` Daniel Vetter
2018-11-23 12:45 ` Daniel Vetter
2018-11-23 13:24 ` Daniel Vetter
2018-11-07 15:30 ` [PATCH 13/13] Revert "locking/lockdep, cpu/hotplug: Annotate AP thread" Daniel Vetter
2018-11-07 16:51 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/13] locking/lockdep: restore cross-release checks Patchwork
2018-11-07 16:57 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-07 17:07 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-11-08 10:04 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/13] locking/lockdep: restore cross-release checks (rev2) Patchwork
2018-11-08 10:10 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-08 10:21 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-11-20 12:33 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/13] locking/lockdep: restore cross-release checks (rev3) Patchwork
2018-11-20 12:39 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-20 12:53 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-11-22 16:39 ` ✗ Fi.CI.BAT: failure for series starting with [01/13] locking/lockdep: restore cross-release checks (rev4) Patchwork
2018-11-23 8:57 ` ✗ Fi.CI.BAT: failure for series starting with [01/13] locking/lockdep: restore cross-release checks (rev5) Patchwork
2018-11-23 12:51 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/13] locking/lockdep: restore cross-release checks (rev6) Patchwork
2018-11-23 12:57 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-23 13:08 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-11-23 13:55 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/13] locking/lockdep: restore cross-release checks (rev7) Patchwork
2018-11-23 14:01 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-23 14:12 ` 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=20181123141246.3993.54846@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--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