From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Janusz Krzysztofik" <janusz.krzysztofik@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for lib/kunit: Execute test cases synchronously (rev4)
Date: Thu, 07 Mar 2024 18:21:07 -0000 [thread overview]
Message-ID: <170983566757.580282.6853893858242634477@8e613ede5ea5> (raw)
In-Reply-To: <20240227151128.16802-4-janusz.krzysztofik@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 3535 bytes --]
== Series Details ==
Series: lib/kunit: Execute test cases synchronously (rev4)
URL : https://patchwork.freedesktop.org/series/126017/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_14405 -> IGTPW_10792
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_10792 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_10792, please notify your bug team (I915-ci-infra@lists.freedesktop.org) 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/IGTPW_10792/index.html
Participating hosts (40 -> 38)
------------------------------
Missing (2): bat-mtlp-8 fi-snb-2520m
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_10792:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@objects:
- bat-arls-2: [PASS][1] -> [ABORT][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14405/bat-arls-2/igt@i915_selftest@live@objects.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10792/bat-arls-2/igt@i915_selftest@live@objects.html
Known issues
------------
Here are the changes found in IGTPW_10792 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_lmem_swapping@basic:
- fi-apl-guc: NOTRUN -> [SKIP][3] ([i915#4613]) +3 other tests skip
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10792/fi-apl-guc/igt@gem_lmem_swapping@basic.html
* igt@gem_lmem_swapping@basic@lmem0:
- bat-dg2-11: [PASS][4] -> [FAIL][5] ([i915#10378])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14405/bat-dg2-11/igt@gem_lmem_swapping@basic@lmem0.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10792/bat-dg2-11/igt@gem_lmem_swapping@basic@lmem0.html
* igt@gem_lmem_swapping@random-engines:
- fi-bsw-n3050: NOTRUN -> [SKIP][6] +19 other tests skip
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10792/fi-bsw-n3050/igt@gem_lmem_swapping@random-engines.html
* igt@kms_hdmi_inject@inject-audio:
- fi-apl-guc: NOTRUN -> [SKIP][7] +17 other tests skip
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10792/fi-apl-guc/igt@kms_hdmi_inject@inject-audio.html
#### Possible fixes ####
* igt@i915_selftest@live@hangcheck:
- bat-rplp-1: [ABORT][8] ([i915#10021]) -> [PASS][9]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14405/bat-rplp-1/igt@i915_selftest@live@hangcheck.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10792/bat-rplp-1/igt@i915_selftest@live@hangcheck.html
[i915#10021]: https://gitlab.freedesktop.org/drm/intel/issues/10021
[i915#10378]: https://gitlab.freedesktop.org/drm/intel/issues/10378
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_7749 -> IGTPW_10792
CI-20190529: 20190529
CI_DRM_14405: 56720b5e1da1b816a1bf532359941adb002c4432 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_10792: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10792/index.html
IGT_7749: 2fd91b8c3cf9aa2b0bb78537a6b5e2bc3de50e0e @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10792/index.html
[-- Attachment #2: Type: text/html, Size: 4286 bytes --]
next prev parent reply other threads:[~2024-03-07 18:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 15:10 [PATCH i-g-t v2 0/2] lib/kunit: Execute test cases synchronously Janusz Krzysztofik
2024-02-27 15:10 ` [PATCH i-g-t v2 1/2] " Janusz Krzysztofik
2024-03-07 17:54 ` Kamil Konieczny
2024-03-14 10:29 ` Kamil Konieczny
2024-03-14 11:48 ` Janusz Krzysztofik
2024-02-27 15:10 ` [PATCH i-g-t v2 2/2] lib/kunit: Minimize code duplication Janusz Krzysztofik
2024-03-07 17:48 ` Kamil Konieczny
2024-02-27 15:19 ` ✗ CI.Patch_applied: failure for lib/kunit: Execute test cases synchronously (rev2) Patchwork
2024-02-27 15:38 ` ✓ CI.xeBAT: success " Patchwork
2024-02-27 15:48 ` ✓ Fi.CI.BAT: " Patchwork
2024-02-28 2:33 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-03-07 10:25 ` ✓ CI.xeBAT: success for lib/kunit: Execute test cases synchronously (rev3) Patchwork
2024-03-07 10:32 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-03-07 18:21 ` Patchwork [this message]
2024-03-07 18:24 ` ✓ CI.xeBAT: success for lib/kunit: Execute test cases synchronously (rev4) Patchwork
2024-03-07 20:58 ` [PATCH i-g-t v2 0/2] lib/kunit: Execute test cases synchronously Cavitt, Jonathan
2024-03-13 11:59 ` ✓ CI.xeBAT: success for lib/kunit: Execute test cases synchronously (rev5) Patchwork
2024-03-13 12:16 ` ✓ Fi.CI.BAT: " Patchwork
2024-03-13 16:33 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-03-13 16:52 ` Janusz Krzysztofik
2024-03-14 19:24 ` 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=170983566757.580282.6853893858242634477@8e613ede5ea5 \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.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.