From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for consistently use dma_resv locking wrappers
Date: Mon, 25 Nov 2019 12:20:51 -0000 [thread overview]
Message-ID: <157468445199.15531.2448398667328173923@emeril.freedesktop.org> (raw)
In-Reply-To: <20191125094356.161941-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: consistently use dma_resv locking wrappers
URL : https://patchwork.freedesktop.org/series/69970/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7416 -> Patchwork_15417
====================================================
Summary
-------
**WARNING**
Minor unknown changes coming with Patchwork_15417 need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_15417, 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_15417/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_15417:
### IGT changes ###
#### Warnings ####
* igt@i915_selftest@live_workarounds:
- fi-kbl-soraka: [TIMEOUT][1] ([fdo#112387]) -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-kbl-soraka/igt@i915_selftest@live_workarounds.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-kbl-soraka/igt@i915_selftest@live_workarounds.html
Known issues
------------
Here are the changes found in Patchwork_15417 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@module-reload:
- fi-skl-lmem: [PASS][3] -> [DMESG-WARN][4] ([fdo#112261])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-skl-lmem/igt@i915_pm_rpm@module-reload.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-skl-lmem/igt@i915_pm_rpm@module-reload.html
* igt@i915_selftest@live_blt:
- fi-hsw-peppy: [PASS][5] -> [DMESG-FAIL][6] ([fdo#112147])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-hsw-peppy/igt@i915_selftest@live_blt.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-hsw-peppy/igt@i915_selftest@live_blt.html
* igt@i915_selftest@live_hangcheck:
- fi-hsw-4770r: [PASS][7] -> [DMESG-FAIL][8] ([fdo#111991])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-hsw-4770r/igt@i915_selftest@live_hangcheck.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-hsw-4770r/igt@i915_selftest@live_hangcheck.html
#### Possible fixes ####
* igt@i915_pm_rpm@module-reload:
- fi-skl-6770hq: [FAIL][9] ([fdo#108511]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][11] ([fdo#111407]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
#### Warnings ####
* igt@gem_exec_suspend@basic-s0:
- fi-kbl-x1275: [DMESG-WARN][13] ([fdo#103558] / [fdo#105602]) -> [DMESG-WARN][14] ([fdo#103558] / [fdo#105602] / [fdo#105763]) +2 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-kbl-x1275/igt@gem_exec_suspend@basic-s0.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-kbl-x1275/igt@gem_exec_suspend@basic-s0.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-kbl-x1275: [DMESG-WARN][15] ([fdo#103558] / [fdo#105602] / [fdo#105763]) -> [DMESG-WARN][16] ([fdo#103558] / [fdo#105602]) +9 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-kbl-x1275/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-kbl-x1275/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
* igt@runner@aborted:
- fi-cfl-guc: [FAIL][17] ([fdo#110943]) -> [FAIL][18] ([fdo#110943] / [fdo#112387])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-cfl-guc/igt@runner@aborted.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-cfl-guc/igt@runner@aborted.html
- fi-kbl-x1275: [FAIL][19] ([fdo#112387]) -> [FAIL][20] ([fdo#105602])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-kbl-x1275/igt@runner@aborted.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-kbl-x1275/igt@runner@aborted.html
- fi-kbl-guc: [FAIL][21] ([fdo#110943]) -> [FAIL][22] ([fdo#110943] / [fdo#112387])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-kbl-guc/igt@runner@aborted.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-kbl-guc/igt@runner@aborted.html
[fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558
[fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602
[fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763
[fdo#108511]: https://bugs.freedesktop.org/show_bug.cgi?id=108511
[fdo#110943]: https://bugs.freedesktop.org/show_bug.cgi?id=110943
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
[fdo#111991]: https://bugs.freedesktop.org/show_bug.cgi?id=111991
[fdo#112147]: https://bugs.freedesktop.org/show_bug.cgi?id=112147
[fdo#112261]: https://bugs.freedesktop.org/show_bug.cgi?id=112261
[fdo#112387]: https://bugs.freedesktop.org/show_bug.cgi?id=112387
Participating hosts (47 -> 44)
------------------------------
Additional (2): fi-skl-guc fi-gdg-551
Missing (5): fi-ilk-m540 fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7416 -> Patchwork_15417
CI-20190529: 20190529
CI_DRM_7416: 27c78108eb4aa74878015666a796dcfe09dcbd00 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5305: eafaa79dfb71f7251126f1c000e0cbe94425c95a @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15417: 81996363592231adeb3e5612d7791e23ae3c8411 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
819963635922 drm/vc4: Use dma_resv locking wrappers
5e8c7f04d447 drm/msm: Use dma_resv locking wrappers
c13d788d8bd6 drm/i915: Use dma_resv locking wrappers
7776c394b6e2 drm/etnaviv: Use dma_resv locking wrappers
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
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: success for consistently use dma_resv locking wrappers
Date: Mon, 25 Nov 2019 12:20:51 -0000 [thread overview]
Message-ID: <157468445199.15531.2448398667328173923@emeril.freedesktop.org> (raw)
Message-ID: <20191125122051.4O4KFGaubogqkUY9eTJhi0p-dkkMK0EqcdSgTFMs8us@z> (raw)
In-Reply-To: <20191125094356.161941-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: consistently use dma_resv locking wrappers
URL : https://patchwork.freedesktop.org/series/69970/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7416 -> Patchwork_15417
====================================================
Summary
-------
**WARNING**
Minor unknown changes coming with Patchwork_15417 need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_15417, 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_15417/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_15417:
### IGT changes ###
#### Warnings ####
* igt@i915_selftest@live_workarounds:
- fi-kbl-soraka: [TIMEOUT][1] ([fdo#112387]) -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-kbl-soraka/igt@i915_selftest@live_workarounds.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-kbl-soraka/igt@i915_selftest@live_workarounds.html
Known issues
------------
Here are the changes found in Patchwork_15417 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@module-reload:
- fi-skl-lmem: [PASS][3] -> [DMESG-WARN][4] ([fdo#112261])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-skl-lmem/igt@i915_pm_rpm@module-reload.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-skl-lmem/igt@i915_pm_rpm@module-reload.html
* igt@i915_selftest@live_blt:
- fi-hsw-peppy: [PASS][5] -> [DMESG-FAIL][6] ([fdo#112147])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-hsw-peppy/igt@i915_selftest@live_blt.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-hsw-peppy/igt@i915_selftest@live_blt.html
* igt@i915_selftest@live_hangcheck:
- fi-hsw-4770r: [PASS][7] -> [DMESG-FAIL][8] ([fdo#111991])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-hsw-4770r/igt@i915_selftest@live_hangcheck.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-hsw-4770r/igt@i915_selftest@live_hangcheck.html
#### Possible fixes ####
* igt@i915_pm_rpm@module-reload:
- fi-skl-6770hq: [FAIL][9] ([fdo#108511]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][11] ([fdo#111407]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
#### Warnings ####
* igt@gem_exec_suspend@basic-s0:
- fi-kbl-x1275: [DMESG-WARN][13] ([fdo#103558] / [fdo#105602]) -> [DMESG-WARN][14] ([fdo#103558] / [fdo#105602] / [fdo#105763]) +2 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-kbl-x1275/igt@gem_exec_suspend@basic-s0.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-kbl-x1275/igt@gem_exec_suspend@basic-s0.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-kbl-x1275: [DMESG-WARN][15] ([fdo#103558] / [fdo#105602] / [fdo#105763]) -> [DMESG-WARN][16] ([fdo#103558] / [fdo#105602]) +9 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-kbl-x1275/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-kbl-x1275/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
* igt@runner@aborted:
- fi-cfl-guc: [FAIL][17] ([fdo#110943]) -> [FAIL][18] ([fdo#110943] / [fdo#112387])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-cfl-guc/igt@runner@aborted.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-cfl-guc/igt@runner@aborted.html
- fi-kbl-x1275: [FAIL][19] ([fdo#112387]) -> [FAIL][20] ([fdo#105602])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-kbl-x1275/igt@runner@aborted.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-kbl-x1275/igt@runner@aborted.html
- fi-kbl-guc: [FAIL][21] ([fdo#110943]) -> [FAIL][22] ([fdo#110943] / [fdo#112387])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7416/fi-kbl-guc/igt@runner@aborted.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/fi-kbl-guc/igt@runner@aborted.html
[fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558
[fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602
[fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763
[fdo#108511]: https://bugs.freedesktop.org/show_bug.cgi?id=108511
[fdo#110943]: https://bugs.freedesktop.org/show_bug.cgi?id=110943
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
[fdo#111991]: https://bugs.freedesktop.org/show_bug.cgi?id=111991
[fdo#112147]: https://bugs.freedesktop.org/show_bug.cgi?id=112147
[fdo#112261]: https://bugs.freedesktop.org/show_bug.cgi?id=112261
[fdo#112387]: https://bugs.freedesktop.org/show_bug.cgi?id=112387
Participating hosts (47 -> 44)
------------------------------
Additional (2): fi-skl-guc fi-gdg-551
Missing (5): fi-ilk-m540 fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7416 -> Patchwork_15417
CI-20190529: 20190529
CI_DRM_7416: 27c78108eb4aa74878015666a796dcfe09dcbd00 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5305: eafaa79dfb71f7251126f1c000e0cbe94425c95a @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15417: 81996363592231adeb3e5612d7791e23ae3c8411 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
819963635922 drm/vc4: Use dma_resv locking wrappers
5e8c7f04d447 drm/msm: Use dma_resv locking wrappers
c13d788d8bd6 drm/i915: Use dma_resv locking wrappers
7776c394b6e2 drm/etnaviv: Use dma_resv locking wrappers
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15417/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-25 12:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 9:43 [PATCH 0/4] consistently use dma_resv locking wrappers Daniel Vetter
2019-11-25 9:43 ` [Intel-gfx] " Daniel Vetter
2019-11-25 9:43 ` Daniel Vetter
2019-11-25 9:43 ` [PATCH 1/4] drm/etnaviv: Use " Daniel Vetter
2019-11-25 9:43 ` [Intel-gfx] " Daniel Vetter
2019-12-13 20:08 ` Daniel Vetter
2019-12-13 20:08 ` [Intel-gfx] " Daniel Vetter
2019-12-13 20:52 ` Ruhl, Michael J
2019-12-13 20:52 ` [Intel-gfx] " Ruhl, Michael J
2019-12-14 0:09 ` [PATCH] " Daniel Vetter
2019-12-16 14:29 ` Ruhl, Michael J
2019-12-16 15:14 ` Lucas Stach
2019-12-17 13:03 ` Daniel Vetter
2019-11-25 9:43 ` [PATCH 2/4] drm/i915: " Daniel Vetter
2019-11-25 9:43 ` [Intel-gfx] " Daniel Vetter
2019-12-14 0:10 ` Daniel Vetter
2019-12-14 0:10 ` [Intel-gfx] " Daniel Vetter
2019-11-25 9:43 ` [PATCH 3/4] drm/msm: " Daniel Vetter
2019-11-25 9:43 ` [Intel-gfx] " Daniel Vetter
2019-11-25 9:43 ` Daniel Vetter
2019-11-25 9:43 ` Daniel Vetter
2019-12-13 20:08 ` Daniel Vetter
2019-12-13 20:08 ` [Intel-gfx] " Daniel Vetter
2019-12-13 20:08 ` Daniel Vetter
2019-12-13 21:43 ` Eric Anholt
2019-12-13 21:43 ` [Intel-gfx] " Eric Anholt
2019-12-13 21:43 ` Eric Anholt
2019-11-25 9:43 ` [PATCH 4/4] drm/vc4: " Daniel Vetter
2019-11-25 9:43 ` [Intel-gfx] " Daniel Vetter
2019-11-25 9:43 ` Daniel Vetter
2019-12-13 20:10 ` Daniel Vetter
2019-12-13 20:10 ` [Intel-gfx] " Daniel Vetter
2019-12-13 21:40 ` Eric Anholt
2019-12-13 21:40 ` [Intel-gfx] " Eric Anholt
2019-11-25 11:55 ` ✗ Fi.CI.CHECKPATCH: warning for consistently use " Patchwork
2019-11-25 11:55 ` [Intel-gfx] " Patchwork
2019-11-25 12:20 ` Patchwork [this message]
2019-11-25 12:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2019-12-03 16:43 ` [PATCH 0/4] " Daniel Vetter
2019-12-03 16:43 ` [Intel-gfx] " Daniel Vetter
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=157468445199.15531.2448398667328173923@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.