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 locking/lockdep: restore cross-release checks (rev3)
Date: Wed, 07 Nov 2018 09:14:39 -0000 [thread overview]
Message-ID: <20181107091439.31412.21508@emeril.freedesktop.org> (raw)
In-Reply-To: <20181102091531.7775-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: series starting with locking/lockdep: restore cross-release checks (rev3)
URL : https://patchwork.freedesktop.org/series/51923/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_5095 -> Patchwork_10738 =
== Summary - FAILURE ==
Serious unknown changes coming with Patchwork_10738 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_10738, 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/3/mbox/
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_10738:
=== IGT changes ===
==== Possible regressions ====
igt@gem_tiled_fence_blits@basic:
fi-skl-gvtdvm: PASS -> DMESG-WARN
fi-bdw-gvtdvm: PASS -> DMESG-WARN
== Known issues ==
Here are the changes found in Patchwork_10738 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@amdgpu/amd_basic@cs-compute:
fi-kbl-8809g: NOTRUN -> FAIL (fdo#108094)
igt@amdgpu/amd_prime@amd-to-i915:
fi-kbl-8809g: NOTRUN -> FAIL (fdo#107341)
igt@drv_selftest@live_contexts:
fi-icl-u: NOTRUN -> DMESG-FAIL (fdo#108569)
igt@gem_exec_suspend@basic-s3:
fi-kbl-soraka: NOTRUN -> INCOMPLETE (fdo#107556, fdo#107859, fdo#107774)
fi-blb-e6850: PASS -> INCOMPLETE (fdo#107718)
igt@kms_pipe_crc_basic@hang-read-crc-pipe-a:
fi-snb-2520m: PASS -> DMESG-FAIL (fdo#103713)
igt@kms_pipe_crc_basic@hang-read-crc-pipe-b:
fi-snb-2520m: PASS -> INCOMPLETE (fdo#103713)
==== Possible fixes ====
igt@drv_selftest@live_contexts:
fi-bsw-kefka: DMESG-FAIL (fdo#108656) -> PASS
igt@gem_ctx_switch@basic-default:
fi-icl-u: INCOMPLETE (fdo#108535, fdo#108315) -> PASS
igt@kms_frontbuffer_tracking@basic:
fi-byt-clapper: FAIL (fdo#103167) -> PASS
igt@kms_pipe_crc_basic@read-crc-pipe-c:
fi-skl-guc: FAIL (fdo#103191, fdo#107362) -> PASS
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
fi-byt-clapper: FAIL (fdo#103191, fdo#107362) -> PASS +1
fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#103713 https://bugs.freedesktop.org/show_bug.cgi?id=103713
fdo#107341 https://bugs.freedesktop.org/show_bug.cgi?id=107341
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
fdo#107556 https://bugs.freedesktop.org/show_bug.cgi?id=107556
fdo#107718 https://bugs.freedesktop.org/show_bug.cgi?id=107718
fdo#107774 https://bugs.freedesktop.org/show_bug.cgi?id=107774
fdo#107859 https://bugs.freedesktop.org/show_bug.cgi?id=107859
fdo#108094 https://bugs.freedesktop.org/show_bug.cgi?id=108094
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
fdo#108656 https://bugs.freedesktop.org/show_bug.cgi?id=108656
== Participating hosts (52 -> 48) ==
Additional (1): fi-kbl-soraka
Missing (5): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600
== Build changes ==
* Linux: CI_DRM_5095 -> Patchwork_10738
CI_DRM_5095: 69a3d10e9a8e4733b81ab69cbeac1f0edd3b9e9d @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4710: 431f0cfa1475dcaa475d6c30610317b3467bd4e4 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10738: 0913556fbd7aeb8ed24a352e2fb6307192b45773 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
0913556fbd7a HAX FOR CI: Enable cross-release
e29afdbed41f drm/i915: annotate intel_atomic_commit_fence_wait
f2202d11beed drm/i915: Annotate dma_fence waits
0ac294b32321 reservation: Annotate dma_fence waits
8900507a5a3c dma-fence: cross-release annotations
c83af5577f98 mm, notifier: Add a lockdep map for invalidate_range_start
a156b1095372 mm, notifier: Catch sleeping/blocking for !blockable
f346774550fb mm: Check if mmu notifier callbacks are allowed to fail
1e6a69b82bb7 kernel/lockdep: Make cross-release a config option
f22f9b50acb9 lockdep: Remove GFP_NOLOCKDEP annotation
afcdf6b27fd4 kthread: finer-grained lockdep/cross-release completion
8236b690a94e locking/lockdep: restore cross-release checks
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10738/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-07 9:14 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 ` ✗ Fi.CI.BAT: failure " Patchwork
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 ` 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=20181107091439.31412.21508@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