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/12] locking/lockdep: restore cross-release checks
Date: Fri, 02 Nov 2018 10:04:48 -0000 [thread overview]
Message-ID: <20181102100448.3496.41497@emeril.freedesktop.org> (raw)
In-Reply-To: <20181102091531.7775-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: series starting with [01/12] locking/lockdep: restore cross-release checks
URL : https://patchwork.freedesktop.org/series/51923/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_5077 -> Patchwork_10706 =
== Summary - FAILURE ==
Serious unknown changes coming with Patchwork_10706 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_10706, 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/51923/revisions/1/mbox/
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_10706:
=== IGT changes ===
==== Possible regressions ====
igt@gem_exec_gttfill@basic:
fi-kbl-7567u: PASS -> DMESG-WARN
igt@gem_sync@basic-each:
fi-bdw-gvtdvm: PASS -> DMESG-WARN
fi-kbl-guc: PASS -> DMESG-WARN
fi-bdw-5557u: PASS -> DMESG-WARN
fi-kbl-r: PASS -> DMESG-WARN
fi-hsw-4770r: PASS -> DMESG-WARN
fi-skl-6260u: PASS -> DMESG-WARN
fi-bsw-kefka: PASS -> DMESG-WARN
fi-kbl-x1275: PASS -> DMESG-WARN
fi-skl-gvtdvm: PASS -> DMESG-WARN
fi-bsw-n3050: PASS -> DMESG-WARN
fi-skl-6700k2: PASS -> DMESG-WARN
fi-skl-6770hq: PASS -> DMESG-WARN
fi-cfl-guc: PASS -> DMESG-WARN
fi-skl-iommu: PASS -> DMESG-WARN
fi-apl-guc: PASS -> DMESG-WARN
fi-bxt-dsi: PASS -> DMESG-WARN
fi-kbl-7560u: PASS -> DMESG-WARN
fi-ivb-3770: PASS -> DMESG-WARN
fi-skl-6600u: PASS -> DMESG-WARN
fi-whl-u: PASS -> DMESG-WARN
fi-cfl-8700k: PASS -> DMESG-WARN
fi-kbl-7500u: PASS -> DMESG-WARN
fi-skl-guc: PASS -> DMESG-WARN
fi-cnl-u: PASS -> DMESG-WARN
fi-glk-j4005: PASS -> DMESG-WARN
fi-glk-dsi: PASS -> DMESG-WARN
fi-hsw-peppy: PASS -> DMESG-WARN
fi-skl-6700hq: PASS -> DMESG-WARN
fi-bxt-j4205: PASS -> DMESG-WARN
fi-icl-u2: PASS -> DMESG-WARN
fi-cfl-s3: PASS -> DMESG-WARN
igt@gem_sync@basic-many-each:
fi-byt-j1900: PASS -> DMESG-WARN
fi-byt-clapper: PASS -> DMESG-WARN
fi-snb-2600: PASS -> DMESG-WARN
fi-ivb-3520m: PASS -> DMESG-WARN
fi-hsw-4770: PASS -> DMESG-WARN
igt@prime_vgem@basic-fence-flip:
fi-gdg-551: PASS -> DMESG-WARN
fi-pnv-d510: PASS -> DMESG-WARN
== Known issues ==
Here are the changes found in Patchwork_10706 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_ctx_switch@basic-default:
fi-icl-u: NOTRUN -> INCOMPLETE (fdo#108535, fdo#108315)
igt@gem_exec_suspend@basic-s3:
fi-kbl-soraka: NOTRUN -> INCOMPLETE (fdo#107859, fdo#107774, fdo#107556)
igt@kms_flip@basic-flip-vs-modeset:
fi-skl-6700hq: PASS -> DMESG-WARN (fdo#105998) +1
igt@kms_frontbuffer_tracking@basic:
fi-hsw-peppy: PASS -> DMESG-WARN (fdo#102614)
==== Possible fixes ====
igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b-frame-sequence:
fi-byt-clapper: FAIL (fdo#107362, fdo#103191) -> PASS +1
==== Warnings ====
igt@drv_selftest@live_contexts:
fi-icl-u2: DMESG-FAIL (fdo#108569) -> INCOMPLETE (fdo#108315)
fdo#102614 https://bugs.freedesktop.org/show_bug.cgi?id=102614
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#105998 https://bugs.freedesktop.org/show_bug.cgi?id=105998
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
fdo#107556 https://bugs.freedesktop.org/show_bug.cgi?id=107556
fdo#107774 https://bugs.freedesktop.org/show_bug.cgi?id=107774
fdo#107859 https://bugs.freedesktop.org/show_bug.cgi?id=107859
fdo#108315 https://bugs.freedesktop.org/show_bug.cgi?id=108315
fdo#108535 https://bugs.freedesktop.org/show_bug.cgi?id=108535
fdo#108569 https://bugs.freedesktop.org/show_bug.cgi?id=108569
== Participating hosts (43 -> 42) ==
Additional (2): fi-kbl-soraka fi-icl-u
Missing (3): fi-ilk-m540 fi-byt-squawks fi-bsw-cyan
== Build changes ==
* Linux: CI_DRM_5077 -> Patchwork_10706
CI_DRM_5077: 1915c67b9e2886117ec217e75ff9cfde8b1e3099 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4704: ace031dcb1e8bf2b32b4b0d54a55eb30e8f41d6f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10706: 262367da82b761679e95dd0817a377b4a4dd4556 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
262367da82b7 HAX FOR CI: Enable cross-release
db3377b5b42b drm/i915: annotate intel_atomic_commit_fence_wait
6d110e32e829 drm/i915: Annotate dma_fence waits
4c2654cb3a9e reservation: Annotate dma_fence waits
27877d64e988 dma-fence: cross-release annotations
d532af81d6ac mm, notifier: Add a lockdep map for invalidate_range_start
82d4533cb449 mm, notifier: Catch sleeping/blocking for !blockable
7e4ead273b8d mm: Check if mmu notifier callbacks are allowed to fail
80a1555c61a6 kernel/lockdep: Make cross-release a config option
21688b527b8d lockdep: Remove GFP_NOLOCKDEP annotation
d5e92af47f86 kthread: finer-grained lockdep/cross-release completion
11e54ecf16c4 locking/lockdep: restore cross-release checks
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10706/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-11-02 10:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 9:15 [PATCH 01/12] locking/lockdep: restore cross-release checks Daniel Vetter
2018-11-02 9:15 ` [PATCH 02/12] kthread: finer-grained lockdep/cross-release completion Daniel Vetter
2018-11-02 9:15 ` [PATCH 03/12] lockdep: Remove GFP_NOLOCKDEP annotation Daniel Vetter
2018-11-02 9:15 ` [PATCH 04/12] kernel/lockdep: Make cross-release a config option Daniel Vetter
2018-11-02 9:15 ` [PATCH 05/12] mm: Check if mmu notifier callbacks are allowed to fail Daniel Vetter
2018-11-02 9:15 ` [PATCH 06/12] mm, notifier: Catch sleeping/blocking for !blockable Daniel Vetter
2018-11-02 9:15 ` [PATCH 07/12] mm, notifier: Add a lockdep map for invalidate_range_start Daniel Vetter
2018-11-02 9:15 ` [PATCH 08/12] dma-fence: cross-release annotations Daniel Vetter
2018-11-02 9:15 ` [PATCH 09/12] reservation: Annotate dma_fence waits Daniel Vetter
2018-11-02 9:15 ` [PATCH 10/12] drm/i915: " Daniel Vetter
2018-11-06 13:55 ` [PATCH] " Daniel Vetter
2018-11-06 16:48 ` kbuild test robot
2018-11-06 16:48 ` kbuild test robot
2018-11-02 9:15 ` [PATCH 11/12] drm/i915: annotate intel_atomic_commit_fence_wait Daniel Vetter
2018-11-02 9:15 ` [PATCH 12/12] HAX FOR CI: Enable cross-release Daniel Vetter
2018-11-02 9:43 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/12] locking/lockdep: restore cross-release checks Patchwork
2018-11-02 9:49 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-02 10:04 ` Patchwork [this message]
2018-11-06 14:14 ` ✗ Fi.CI.BAT: failure for series starting with [01/12] locking/lockdep: restore cross-release checks (rev2) Patchwork
2018-11-06 15:05 ` [PATCH] locking/lockdep: restore cross-release checks Daniel Vetter
2018-11-06 15:50 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with locking/lockdep: restore cross-release checks (rev3) Patchwork
2018-11-06 15:56 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-07 9:14 ` ✗ Fi.CI.BAT: failure " 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=20181102100448.3496.41497@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