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 (rev3)
Date: Tue, 20 Nov 2018 12:53:38 -0000 [thread overview]
Message-ID: <20181120125338.22659.4812@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 (rev3)
URL : https://patchwork.freedesktop.org/series/52167/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_5171 -> Patchwork_10859 =
== Summary - FAILURE ==
Serious unknown changes coming with Patchwork_10859 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_10859, 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/3/mbox/
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_10859:
=== IGT changes ===
==== Possible regressions ====
igt@gem_tiled_fence_blits@basic:
fi-elk-e7500: PASS -> DMESG-WARN
fi-skl-6700k2: PASS -> DMESG-WARN
fi-cfl-guc: PASS -> DMESG-WARN
fi-skl-6700hq: PASS -> DMESG-WARN
fi-hsw-4770r: PASS -> DMESG-WARN
fi-kbl-x1275: PASS -> DMESG-WARN
fi-bdw-5557u: 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-icl-u2: 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-kbl-r: PASS -> DMESG-WARN
fi-skl-guc: PASS -> DMESG-WARN
fi-kbl-guc: PASS -> DMESG-WARN
fi-skl-6600u: PASS -> DMESG-WARN
fi-cfl-8700k: PASS -> DMESG-WARN
igt@prime_vgem@basic-fence-flip:
fi-blb-e6850: PASS -> DMESG-WARN
== Known issues ==
Here are the changes found in Patchwork_10859 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_exec_suspend@basic-s3:
fi-icl-u2: PASS -> DMESG-WARN (fdo#107724)
igt@gem_mmap_gtt@basic-small-bo-tiledy:
fi-glk-dsi: PASS -> INCOMPLETE (fdo#103359, k.org#198133)
igt@kms_frontbuffer_tracking@basic:
fi-byt-clapper: PASS -> FAIL (fdo#103167)
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
fi-cfl-8109u: PASS -> INCOMPLETE (fdo#106070, fdo#108126)
==== Possible fixes ====
igt@gem_ctx_create@basic-files:
fi-icl-u2: DMESG-WARN (fdo#107724) -> PASS
igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b-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#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#103359 https://bugs.freedesktop.org/show_bug.cgi?id=103359
fdo#106070 https://bugs.freedesktop.org/show_bug.cgi?id=106070
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
fdo#107724 https://bugs.freedesktop.org/show_bug.cgi?id=107724
fdo#108126 https://bugs.freedesktop.org/show_bug.cgi?id=108126
k.org#198133 https://bugzilla.kernel.org/show_bug.cgi?id=198133
== Participating hosts (48 -> 44) ==
Additional (2): fi-kbl-7560u fi-gdg-551
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_5171 -> Patchwork_10859
CI_DRM_5171: 84e7dbc23b35bf21bac105e72e0ba7023847f5ac @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4721: 68264891ceee34195839d82d4d87cbae08ef2431 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10859: a92325ed09f8cc6b5aacf1b6c2fe23978cf4e8ea @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
a92325ed09f8 Revert "locking/lockdep, cpu/hotplug: Annotate AP thread"
4717d45fe1b6 HAX FOR CI: Enable cross-release
401b2d631fb5 drm/i915: annotate intel_atomic_commit_fence_wait
e60856ea5d1f drm/i915: Annotate dma_fence waits
dd811c8f1350 reservation: Annotate dma_fence waits
8dcf3bbce92f dma-fence: cross-release annotations
89c0437e66b9 mm, notifier: Add a lockdep map for invalidate_range_start
2b0ed181506c mm, notifier: Catch sleeping/blocking for !blockable
c48434bf624c mm: Check if mmu notifier callbacks are allowed to fail
5b3e8d1062cc kernel/lockdep: Make cross-release a config option
132a5d524bf5 lockdep: Remove GFP_NOLOCKDEP annotation
7a874678febd kthread: finer-grained lockdep/cross-release completion
a3b9f37357c8 locking/lockdep: restore cross-release checks
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10859/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-20 12:53 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 ` Patchwork [this message]
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 ` ✗ 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=20181120125338.22659.4812@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.