From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Daniel Vetter" <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/4] drm: Complain if drivers still use the ->load callback
Date: Tue, 28 Jan 2020 19:44:00 -0000 [thread overview]
Message-ID: <158024064003.20535.6792906101773835177@emeril.freedesktop.org> (raw)
In-Reply-To: <20200128104602.1459802-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: series starting with [1/4] drm: Complain if drivers still use the ->load callback
URL : https://patchwork.freedesktop.org/series/72652/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7833 -> Patchwork_16292
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_16292 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_16292, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_16292:
### IGT changes ###
#### Possible regressions ####
* igt@core_auth@basic-auth:
- fi-bwr-2160: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7833/fi-bwr-2160/igt@core_auth@basic-auth.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/fi-bwr-2160/igt@core_auth@basic-auth.html
- fi-kbl-guc: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7833/fi-kbl-guc/igt@core_auth@basic-auth.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/fi-kbl-guc/igt@core_auth@basic-auth.html
- fi-cfl-8700k: [PASS][5] -> [INCOMPLETE][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7833/fi-cfl-8700k/igt@core_auth@basic-auth.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/fi-cfl-8700k/igt@core_auth@basic-auth.html
- fi-blb-e6850: [PASS][7] -> [INCOMPLETE][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7833/fi-blb-e6850/igt@core_auth@basic-auth.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/fi-blb-e6850/igt@core_auth@basic-auth.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@runner@aborted:
- {fi-ehl-1}: NOTRUN -> [FAIL][9]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/fi-ehl-1/igt@runner@aborted.html
Known issues
------------
Here are the changes found in Patchwork_16292 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@core_auth@basic-auth:
- fi-icl-u2: [PASS][10] -> [INCOMPLETE][11] ([i915#140])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7833/fi-icl-u2/igt@core_auth@basic-auth.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/fi-icl-u2/igt@core_auth@basic-auth.html
- fi-icl-guc: [PASS][12] -> [INCOMPLETE][13] ([i915#140])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7833/fi-icl-guc/igt@core_auth@basic-auth.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/fi-icl-guc/igt@core_auth@basic-auth.html
- fi-elk-e7500: [PASS][14] -> [INCOMPLETE][15] ([i915#66])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7833/fi-elk-e7500/igt@core_auth@basic-auth.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/fi-elk-e7500/igt@core_auth@basic-auth.html
- fi-cml-s: [PASS][16] -> [INCOMPLETE][17] ([i915#283])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7833/fi-cml-s/igt@core_auth@basic-auth.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/fi-cml-s/igt@core_auth@basic-auth.html
- fi-icl-u3: [PASS][18] -> [INCOMPLETE][19] ([i915#140])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7833/fi-icl-u3/igt@core_auth@basic-auth.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/fi-icl-u3/igt@core_auth@basic-auth.html
- fi-gdg-551: [PASS][20] -> [INCOMPLETE][21] ([i915#172])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7833/fi-gdg-551/igt@core_auth@basic-auth.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/fi-gdg-551/igt@core_auth@basic-auth.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#140]: https://gitlab.freedesktop.org/drm/intel/issues/140
[i915#172]: https://gitlab.freedesktop.org/drm/intel/issues/172
[i915#283]: https://gitlab.freedesktop.org/drm/intel/issues/283
[i915#66]: https://gitlab.freedesktop.org/drm/intel/issues/66
Participating hosts (50 -> 13)
------------------------------
ERROR: It appears as if the changes made in Patchwork_16292 prevented too many machines from booting.
Missing (37): fi-apl-guc fi-pnv-d510 fi-icl-y fi-skl-lmem fi-byt-n2820 fi-icl-dsi fi-skl-6600u fi-snb-2600 fi-hsw-4770r fi-cml-u2 fi-bxt-dsi fi-bdw-5557u fi-tgl-u fi-bsw-n3050 fi-byt-j1900 fi-glk-dsi fi-ilk-650 fi-kbl-7500u fi-ctg-p8600 fi-hsw-4770 fi-ivb-3770 fi-kbl-7560u fi-skl-6700k2 fi-kbl-r fi-ilk-m540 fi-skl-guc fi-hsw-peppy fi-byt-squawks fi-bsw-cyan fi-cfl-guc fi-whl-u fi-kbl-x1275 fi-cfl-8109u fi-kbl-8809g fi-bsw-kefka fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7833 -> Patchwork_16292
CI-20190529: 20190529
CI_DRM_7833: 8210f0f999e2d396a8611e0cabc2f6c6a52468de @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5394: 991fd07bcd7add7a5beca2c95b72a994e62fbb75 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16292: d229dd0db3a6f3d8c60fed5860754ef1dd765ebb @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
d229dd0db3a6 drm: Nerv drm_global_mutex BKL for good drivers
b3d3b03017d2 drm: Push drm_global_mutex locking in drm_open
51b7fc1c6674 drm/fbdev-helper: don't force restores
4b3af837d222 drm: Complain if drivers still use the ->load callback
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16292/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-01-28 19:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 10:45 [PATCH 1/4] drm: Complain if drivers still use the ->load callback Daniel Vetter
2020-01-28 10:45 ` [Intel-gfx] " Daniel Vetter
2020-01-28 10:45 ` [PATCH 2/4] drm/fbdev-helper: don't force restores Daniel Vetter
2020-01-28 10:45 ` [Intel-gfx] " Daniel Vetter
2020-01-28 11:52 ` Noralf Trønnes
2020-01-28 11:52 ` [Intel-gfx] " Noralf Trønnes
2020-01-28 14:55 ` Daniel Vetter
2020-01-28 14:55 ` [Intel-gfx] " Daniel Vetter
2020-01-28 10:46 ` [PATCH 3/4] drm: Push drm_global_mutex locking in drm_open Daniel Vetter
2020-01-28 10:46 ` [Intel-gfx] " Daniel Vetter
2020-01-28 10:49 ` Chris Wilson
2020-01-28 10:49 ` [Intel-gfx] " Chris Wilson
2020-01-28 10:46 ` [PATCH 4/4] drm: Nerv drm_global_mutex BKL for good drivers Daniel Vetter
2020-01-28 10:46 ` [Intel-gfx] " Daniel Vetter
2020-01-28 11:00 ` Chris Wilson
2020-01-28 11:00 ` [Intel-gfx] " Chris Wilson
2020-01-28 14:59 ` Daniel Vetter
2020-01-28 14:59 ` [Intel-gfx] " Daniel Vetter
2020-01-28 10:47 ` [Intel-gfx] [PATCH 1/4] drm: Complain if drivers still use the ->load callback Chris Wilson
2020-01-28 10:47 ` Chris Wilson
2020-01-28 11:01 ` Chris Wilson
2020-01-28 11:01 ` Chris Wilson
2020-01-28 15:02 ` Daniel Vetter
2020-01-28 15:02 ` Daniel Vetter
2020-01-28 13:41 ` Thomas Zimmermann
2020-01-28 13:41 ` [Intel-gfx] " Thomas Zimmermann
2020-01-28 14:53 ` Daniel Vetter
2020-01-28 14:53 ` [Intel-gfx] " Daniel Vetter
2020-01-28 18:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] " Patchwork
2020-01-28 19:44 ` 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=158024064003.20535.6792906101773835177@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.