From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Stanislav Lisovskiy" <stanislav.lisovskiy@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Enable second dbuf slice for ICL and TGL
Date: Thu, 07 Nov 2019 18:12:52 -0000 [thread overview]
Message-ID: <157315037282.21751.4237226621583602038@emeril.freedesktop.org> (raw)
Message-ID: <20191107181252.tYuovTP0AsV7cWecIjV6mDSMq0QZqvlt4xDfYL-NKQI@z> (raw)
In-Reply-To: <20191107131020.12869-1-stanislav.lisovskiy@intel.com>
== Series Details ==
Series: drm/i915: Enable second dbuf slice for ICL and TGL
URL : https://patchwork.freedesktop.org/series/69124/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7288 -> Patchwork_15174
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_15174 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_15174, 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_15174/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_15174:
### IGT changes ###
#### Possible regressions ####
* igt@kms_busy@basic-flip-c:
- fi-icl-dsi: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7288/fi-icl-dsi/igt@kms_busy@basic-flip-c.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15174/fi-icl-dsi/igt@kms_busy@basic-flip-c.html
- fi-icl-u4: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7288/fi-icl-u4/igt@kms_busy@basic-flip-c.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15174/fi-icl-u4/igt@kms_busy@basic-flip-c.html
- fi-icl-u3: [PASS][5] -> [DMESG-WARN][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7288/fi-icl-u3/igt@kms_busy@basic-flip-c.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15174/fi-icl-u3/igt@kms_busy@basic-flip-c.html
- fi-icl-guc: [PASS][7] -> [DMESG-WARN][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7288/fi-icl-guc/igt@kms_busy@basic-flip-c.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15174/fi-icl-guc/igt@kms_busy@basic-flip-c.html
- fi-icl-u2: [PASS][9] -> [DMESG-WARN][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7288/fi-icl-u2/igt@kms_busy@basic-flip-c.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15174/fi-icl-u2/igt@kms_busy@basic-flip-c.html
Known issues
------------
Here are the changes found in Patchwork_15174 that come from known issues:
### IGT changes ###
#### Possible fixes ####
* igt@gem_exec_create@basic:
- {fi-tgl-u}: [INCOMPLETE][11] ([fdo#111736]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7288/fi-tgl-u/igt@gem_exec_create@basic.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15174/fi-tgl-u/igt@gem_exec_create@basic.html
* igt@gem_exec_suspend@basic-s3:
- fi-cml-s: [DMESG-WARN][13] ([fdo#111764]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7288/fi-cml-s/igt@gem_exec_suspend@basic-s3.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15174/fi-cml-s/igt@gem_exec_suspend@basic-s3.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][15] ([fdo#111407]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7288/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15174/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-skl-6700k2: [INCOMPLETE][17] ([fdo#104108]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7288/fi-skl-6700k2/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15174/fi-skl-6700k2/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
[fdo#111736]: https://bugs.freedesktop.org/show_bug.cgi?id=111736
[fdo#111764]: https://bugs.freedesktop.org/show_bug.cgi?id=111764
Participating hosts (51 -> 44)
------------------------------
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-icl-y fi-byt-clapper
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7288 -> Patchwork_15174
CI-20190529: 20190529
CI_DRM_7288: 41eb27f39e60d822edc75e6aaeb416b72bc1dcf2 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5266: 60a67653613c87a69ebecf12cf00aa362ac87597 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15174: 2fdfc3b51c5b0bcac8efab38bf28704298f6e9f7 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
2fdfc3b51c5b drm/i915: Enable second dbuf slice for ICL and TGL
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15174/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-07 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 13:10 [PATCH v4] drm/i915: Enable second dbuf slice for ICL and TGL Stanislav Lisovskiy
2019-11-07 13:10 ` [Intel-gfx] " Stanislav Lisovskiy
2019-11-07 17:40 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-11-07 17:40 ` [Intel-gfx] " Patchwork
2019-11-07 17:41 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-11-07 17:41 ` [Intel-gfx] " Patchwork
2019-11-07 18:12 ` Patchwork [this message]
2019-11-07 18:12 ` [Intel-gfx] ✗ 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=157315037282.21751.4237226621583602038@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stanislav.lisovskiy@intel.com \
/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.