From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jouni Högander" <jouni.hogander@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for Fixes for selective fetch area calculation (rev5)
Date: Fri, 13 May 2022 15:21:35 -0000 [thread overview]
Message-ID: <165245529521.9637.8284356757316442134@emeril.freedesktop.org> (raw)
In-Reply-To: <20220513142811.779331-1-jouni.hogander@intel.com>
[-- Attachment #1: Type: text/plain, Size: 5873 bytes --]
== Series Details ==
Series: Fixes for selective fetch area calculation (rev5)
URL : https://patchwork.freedesktop.org/series/103659/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11649 -> Patchwork_103659v5
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/index.html
Participating hosts (39 -> 39)
------------------------------
Additional (1): fi-blb-e6850
Missing (1): bat-adlm-1
Known issues
------------
Here are the changes found in Patchwork_103659v5 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live@hangcheck:
- fi-hsw-g3258: [PASS][1] -> [INCOMPLETE][2] ([i915#3303] / [i915#4785])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11649/fi-hsw-g3258/igt@i915_selftest@live@hangcheck.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/fi-hsw-g3258/igt@i915_selftest@live@hangcheck.html
* igt@i915_selftest@live@requests:
- fi-blb-e6850: NOTRUN -> [DMESG-FAIL][3] ([i915#4528])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/fi-blb-e6850/igt@i915_selftest@live@requests.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-hsw-4770: NOTRUN -> [SKIP][4] ([fdo#109271] / [fdo#111827])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/fi-hsw-4770/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_force_connector_basic@force-connector-state:
- fi-bdw-gvtdvm: [PASS][5] -> [DMESG-WARN][6] ([i915#5922])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11649/fi-bdw-gvtdvm/igt@kms_force_connector_basic@force-connector-state.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/fi-bdw-gvtdvm/igt@kms_force_connector_basic@force-connector-state.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-blb-e6850: NOTRUN -> [SKIP][7] ([fdo#109271]) +39 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/fi-blb-e6850/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
* igt@runner@aborted:
- fi-bdw-gvtdvm: NOTRUN -> [FAIL][8] ([i915#4312])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/fi-bdw-gvtdvm/igt@runner@aborted.html
- fi-hsw-g3258: NOTRUN -> [FAIL][9] ([fdo#109271] / [i915#4312])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/fi-hsw-g3258/igt@runner@aborted.html
- fi-blb-e6850: NOTRUN -> [FAIL][10] ([fdo#109271] / [i915#2403] / [i915#4312])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/fi-blb-e6850/igt@runner@aborted.html
#### Possible fixes ####
* igt@i915_selftest@live@gt_heartbeat:
- {fi-jsl-1}: [DMESG-FAIL][11] ([i915#5334]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11649/fi-jsl-1/igt@i915_selftest@live@gt_heartbeat.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/fi-jsl-1/igt@i915_selftest@live@gt_heartbeat.html
* igt@i915_selftest@live@hangcheck:
- fi-hsw-4770: [INCOMPLETE][13] ([i915#4785]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11649/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html
* igt@i915_selftest@live@migrate:
- {bat-dg2-9}: [DMESG-WARN][15] ([i915#5763]) -> [PASS][16] +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11649/bat-dg2-9/igt@i915_selftest@live@migrate.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/bat-dg2-9/igt@i915_selftest@live@migrate.html
* igt@kms_flip@basic-flip-vs-modeset@a-edp1:
- {bat-adlp-6}: [DMESG-WARN][17] ([i915#3576]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11649/bat-adlp-6/igt@kms_flip@basic-flip-vs-modeset@a-edp1.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/bat-adlp-6/igt@kms_flip@basic-flip-vs-modeset@a-edp1.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#2403]: https://gitlab.freedesktop.org/drm/intel/issues/2403
[i915#3303]: https://gitlab.freedesktop.org/drm/intel/issues/3303
[i915#3576]: https://gitlab.freedesktop.org/drm/intel/issues/3576
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4528]: https://gitlab.freedesktop.org/drm/intel/issues/4528
[i915#4785]: https://gitlab.freedesktop.org/drm/intel/issues/4785
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#5763]: https://gitlab.freedesktop.org/drm/intel/issues/5763
[i915#5879]: https://gitlab.freedesktop.org/drm/intel/issues/5879
[i915#5922]: https://gitlab.freedesktop.org/drm/intel/issues/5922
Build changes
-------------
* Linux: CI_DRM_11649 -> Patchwork_103659v5
CI-20190529: 20190529
CI_DRM_11649: 41053495dd77aa5604144477ef59334a9492a169 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6472: c815c94f0ceb33ae852622538f0136cf44c5725d @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_103659v5: 41053495dd77aa5604144477ef59334a9492a169 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
069fcfef9181 drm/i915: Ensure damage clip area is within pipe area
ad67b6e22ff4 drm/i915/psr: Use full update In case of area calculation fails
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103659v5/index.html
[-- Attachment #2: Type: text/html, Size: 7099 bytes --]
next prev parent reply other threads:[~2022-05-13 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 14:28 [Intel-gfx] [PATCH v5 0/2] Fixes for selective fetch area calculation Jouni Högander
2022-05-13 14:28 ` [Intel-gfx] [PATCH v5 1/2] drm/i915/psr: Use full update In case of area calculation fails Jouni Högander
2022-05-13 16:35 ` Souza, Jose
2022-05-13 14:28 ` [Intel-gfx] [PATCH v5 2/2] drm/i915: Ensure damage clip area is within pipe area Jouni Högander
2022-05-13 15:21 ` Patchwork [this message]
2022-05-13 17:34 ` [Intel-gfx] ✓ Fi.CI.IGT: success for Fixes for selective fetch area calculation (rev5) 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=165245529521.9637.8284356757316442134@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jouni.hogander@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.