From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Nathan Chancellor" <nathan@kernel.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Fix CFI violations in gt_sysfs (rev4)
Date: Tue, 18 Oct 2022 18:32:51 -0000 [thread overview]
Message-ID: <166611797150.20427.8878126483673735753@emeril.freedesktop.org> (raw)
In-Reply-To: <20221013205909.1282545-1-nathan@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 5973 bytes --]
== Series Details ==
Series: drm/i915: Fix CFI violations in gt_sysfs (rev4)
URL : https://patchwork.freedesktop.org/series/108917/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12257 -> Patchwork_108917v4
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_108917v4 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_108917v4, 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_108917v4/index.html
Participating hosts (41 -> 39)
------------------------------
Additional (1): fi-icl-u2
Missing (3): bat-atsm-1 fi-bdw-samus fi-bsw-nick
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_108917v4:
### IGT changes ###
#### Possible regressions ####
* igt@i915_pm_rpm@basic-pci-d3-state:
- bat-adlp-4: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12257/bat-adlp-4/igt@i915_pm_rpm@basic-pci-d3-state.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/bat-adlp-4/igt@i915_pm_rpm@basic-pci-d3-state.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@i915_module_load@reload:
- {bat-rpls-2}: [DMESG-WARN][3] ([i915#5537]) -> [INCOMPLETE][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12257/bat-rpls-2/igt@i915_module_load@reload.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/bat-rpls-2/igt@i915_module_load@reload.html
Known issues
------------
Here are the changes found in Patchwork_108917v4 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_huc_copy@huc-copy:
- fi-icl-u2: NOTRUN -> [SKIP][5] ([i915#2190])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/fi-icl-u2/igt@gem_huc_copy@huc-copy.html
* igt@gem_lmem_swapping@random-engines:
- fi-icl-u2: NOTRUN -> [SKIP][6] ([i915#4613]) +3 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/fi-icl-u2/igt@gem_lmem_swapping@random-engines.html
* igt@i915_selftest@live@sanitycheck:
- fi-icl-u2: NOTRUN -> [INCOMPLETE][7] ([i915#7222])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/fi-icl-u2/igt@i915_selftest@live@sanitycheck.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-icl-u2: NOTRUN -> [SKIP][8] ([fdo#111827]) +7 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor:
- fi-icl-u2: NOTRUN -> [SKIP][9] ([i915#4103])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/fi-icl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor.html
* igt@kms_force_connector_basic@force-load-detect:
- fi-icl-u2: NOTRUN -> [SKIP][10] ([fdo#109285])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/fi-icl-u2/igt@kms_force_connector_basic@force-load-detect.html
* igt@kms_setmode@basic-clone-single-crtc:
- fi-icl-u2: NOTRUN -> [SKIP][11] ([i915#3555])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/fi-icl-u2/igt@kms_setmode@basic-clone-single-crtc.html
* igt@prime_vgem@basic-userptr:
- fi-icl-u2: NOTRUN -> [SKIP][12] ([fdo#109295] / [i915#3301])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/fi-icl-u2/igt@prime_vgem@basic-userptr.html
* igt@runner@aborted:
- fi-icl-u2: NOTRUN -> [FAIL][13] ([i915#4312])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/fi-icl-u2/igt@runner@aborted.html
#### Possible fixes ####
* igt@gem_exec_gttfill@basic:
- fi-pnv-d510: [SKIP][14] ([fdo#109271]) -> [PASS][15]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12257/fi-pnv-d510/igt@gem_exec_gttfill@basic.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/fi-pnv-d510/igt@gem_exec_gttfill@basic.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#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#5537]: https://gitlab.freedesktop.org/drm/intel/issues/5537
[i915#7222]: https://gitlab.freedesktop.org/drm/intel/issues/7222
Build changes
-------------
* Linux: CI_DRM_12257 -> Patchwork_108917v4
CI-20190529: 20190529
CI_DRM_12257: b249abef9f86f788e6bacc657ae8eb7743948200 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7018: 8312a2fe3f3287ba4ac4bc8d100de0734480f482 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_108917v4: b249abef9f86f788e6bacc657ae8eb7743948200 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
481260ab14eb drm/i915: Fix CFI violations in gt_sysfs
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108917v4/index.html
[-- Attachment #2: Type: text/html, Size: 6900 bytes --]
next prev parent reply other threads:[~2022-10-18 18:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 20:59 [PATCH v2] drm/i915: Fix CFI violations in gt_sysfs Nathan Chancellor
2022-10-13 20:59 ` [Intel-gfx] " Nathan Chancellor
2022-10-13 20:59 ` Nathan Chancellor
2022-10-13 22:13 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Fix CFI violations in gt_sysfs (rev3) Patchwork
2022-10-13 22:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-14 3:39 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-18 18:14 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Fix CFI violations in gt_sysfs (rev4) Patchwork
2022-10-18 18:32 ` Patchwork [this message]
2022-10-27 17:17 ` [PATCH v2] drm/i915: Fix CFI violations in gt_sysfs Andi Shyti
2022-10-27 17:17 ` [Intel-gfx] " Andi Shyti
2022-10-27 17:17 ` Andi Shyti
2023-01-12 10:08 ` Jocelyn Falempe
2023-01-12 10:08 ` Jocelyn Falempe
2023-01-12 10:08 ` [Intel-gfx] " Jocelyn Falempe
2023-01-12 15:56 ` Nathan Chancellor
2023-01-12 15:56 ` [Intel-gfx] " Nathan Chancellor
2023-01-12 15:56 ` Nathan Chancellor
2023-01-13 8:03 ` Jocelyn Falempe
2023-01-13 8:03 ` [Intel-gfx] " Jocelyn Falempe
2023-01-13 8:03 ` Jocelyn Falempe
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=166611797150.20427.8878126483673735753@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nathan@kernel.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.