From: Arthur Grillo <arthurgrillo@riseup.net>
To: igt-dev@lists.freedesktop.org
Cc: I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for benchmarks/kms_fb_stress: benchmark formats (rev3)
Date: Fri, 13 Sep 2024 09:03:36 -0300 [thread overview]
Message-ID: <a161b76d-d855-4367-8461-956daeb6b9e7@riseup.net> (raw)
In-Reply-To: <172619197765.994521.13831879263501632417@2413ebb6fbb6>
On 12/09/24 22:46, Patchwork wrote:
> == Series Details ==
>
> Series: benchmarks/kms_fb_stress: benchmark formats (rev3)
> URL : https://patchwork.freedesktop.org/series/132328/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_15408 -> IGTPW_11738
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with IGTPW_11738 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_11738, 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_11738/index.html
>
> Participating hosts (39 -> 34)
> ------------------------------
>
> Additional (2): fi-cfl-8109u fi-bsw-n3050
> Missing (7): bat-adlp-11 fi-snb-2520m bat-adlp-6 fi-kbl-8809g bat-dg2-14 bat-dg2-13 bat-mtlp-6
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in IGTPW_11738:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@i915_selftest@live@ring_submission:
> - bat-arls-2: [PASS][1] -> [DMESG-WARN][2]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15408/bat-arls-2/igt@i915_selftest@live@ring_submission.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_11738/bat-arls-2/igt@i915_selftest@live@ring_submission.html
>
>
> Known issues
> ------------
I think they are unrelated to my patchset.
Best Regards,
~Arthur Grillo
next prev parent reply other threads:[~2024-09-13 12:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 0:39 [PATCH i-g-t v6 00/12] benchmarks/kms_fb_stress: benchmark formats Arthur Grillo
2024-09-13 0:39 ` [PATCH i-g-t v6 01/12] benchmarks/kms_fb_stress: Set DRM_CLIENT_CAP_WRITEBACK_CONNECTORS before igt_require() Arthur Grillo
2024-10-22 16:41 ` Kamil Konieczny
2024-09-13 0:39 ` [PATCH i-g-t v6 02/12] benchmarks/kms_fb_stress: Assert that we have a supported pipe Arthur Grillo
2024-09-13 0:39 ` [PATCH i-g-t v6 03/12] benchmarks/kms_fb_stress: Separate the benchmark in a subtest Arthur Grillo
2024-09-13 0:39 ` [PATCH i-g-t v6 04/12] benchmarks/kms_fb_stress: Free resources on the stress procedure Arthur Grillo
2024-09-13 0:39 ` [PATCH i-g-t v6 05/12] benchmarks/kms_fb_stress: Move FB creation to a separate function Arthur Grillo
2024-09-13 0:39 ` [PATCH i-g-t v6 06/12] benchmarks/kms_fb_stress: Don't paint the FB's if the format is not supported by Pixman Arthur Grillo
2024-09-13 0:39 ` [PATCH i-g-t v6 07/12] benchmarks/kms_fb_stress: Set writeback rectangle size outside the loop Arthur Grillo
2024-09-13 0:39 ` [PATCH i-g-t v6 08/12] benchmarks/kms_fb_stress: Add enable switches for every plane Arthur Grillo
2024-09-13 0:39 ` [PATCH i-g-t v6 09/12] benchmarks/kms_fb_stress: Log the KMS structure Arthur Grillo
2024-09-13 0:39 ` [PATCH i-g-t v6 10/12] benchmarks/kms_fb_stress: Create a benchmark for primary plane formats Arthur Grillo
2024-09-13 0:39 ` [PATCH i-g-t v6 11/12] benchmarks/kms_fb_stress: Create a benchmark for writeback formats Arthur Grillo
2024-09-13 0:39 ` [PATCH i-g-t v6 12/12] lib/igt_fb: Add non sub-sampled YUV formats Arthur Grillo
2024-10-22 15:06 ` Kamil Konieczny
2024-10-28 15:34 ` Kamil Konieczny
2024-10-28 16:07 ` Ville Syrjälä
2024-09-13 1:26 ` ✓ CI.xeBAT: success for benchmarks/kms_fb_stress: benchmark formats (rev3) Patchwork
2024-09-13 1:46 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-09-13 12:03 ` Arthur Grillo [this message]
2024-09-13 18:36 ` ✗ CI.xeFULL: " 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=a161b76d-d855-4367-8461-956daeb6b9e7@riseup.net \
--to=arthurgrillo@riseup.net \
--cc=I915-ci-infra@lists.freedesktop.org \
--cc=igt-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox