From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: igt-dev@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for man/lsgpu: Add man page for lsgpu (rev2)
Date: Mon, 31 Mar 2025 10:43:48 +0200 [thread overview]
Message-ID: <36cb6a97-d985-48df-9140-0a5f2d67fb88@linux.intel.com> (raw)
In-Reply-To: <174329656986.18497.6873104803547611447@e6b6f09ec485>
Dear I915,
On 3/30/2025 3:02 AM, Patchwork wrote:
> == Series Details ==
>
> Series: man/lsgpu: Add man page for lsgpu (rev2)
> URL : https://patchwork.freedesktop.org/series/146860/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from XEIGT_8292_FULL -> XEIGTPW_12885_FULL
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with XEIGTPW_12885_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in XEIGTPW_12885_FULL, 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.
>
>
>
> Participating hosts (4 -> 4)
> ------------------------------
>
> No changes in participating hosts
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in XEIGTPW_12885_FULL:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_pipe_crc_basic@suspend-read-crc:
> - shard-bmg: [PASS][1] -> [INCOMPLETE][2] +1 other test incomplete
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8292/shard-bmg-7/igt@kms_pipe_crc_basic@suspend-read-crc.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12885/shard-bmg-7/igt@kms_pipe_crc_basic@suspend-read-crc.html
>
> * igt@xe_fault_injection@inject-fault-probe-function-wait_for_lmem_ready:
> - shard-lnl: [PASS][3] -> [ABORT][4]
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8292/shard-lnl-8/igt@xe_fault_injection@inject-fault-probe-function-wait_for_lmem_ready.html
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12885/shard-lnl-7/igt@xe_fault_injection@inject-fault-probe-function-wait_for_lmem_ready.html
>
>
> #### Warnings ####
>
> * igt@kms_content_protection@srm:
> - shard-bmg: [FAIL][5] ([Intel XE#1178]) -> [INCOMPLETE][6] +1 other test incomplete
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8292/shard-bmg-3/igt@kms_content_protection@srm.html
> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12885/shard-bmg-2/igt@kms_content_protection@srm.html
>
> * igt@kms_plane_multiple@2x-tiling-yf:
> - shard-bmg: [SKIP][7] ([Intel XE#4596]) -> [SKIP][8]
> [7]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8292/shard-bmg-4/igt@kms_plane_multiple@2x-tiling-yf.html
> [8]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12885/shard-bmg-6/igt@kms_plane_multiple@2x-tiling-yf.html
>
These are unrelated to my change.
[...]
Thank you!
next prev parent reply other threads:[~2025-03-31 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-29 14:36 [PATCH v2 i-g-t] man/lsgpu: Add man page for lsgpu Peter Senna Tschudin
2025-03-29 15:32 ` ✓ i915.CI.BAT: success for man/lsgpu: Add man page for lsgpu (rev2) Patchwork
2025-03-29 15:40 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-29 17:09 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-31 8:44 ` Peter Senna Tschudin
2025-04-01 10:26 ` Ravali, JupallyX
2025-03-30 1:02 ` ✗ Xe.CI.Full: " Patchwork
2025-03-31 8:43 ` Peter Senna Tschudin [this message]
2025-03-31 14:22 ` [PATCH v2 i-g-t] man/lsgpu: Add man page for lsgpu Kamil Konieczny
2025-04-01 10:21 ` ✓ i915.CI.Full: success for man/lsgpu: Add man page for lsgpu (rev2) Patchwork
2025-04-01 12:37 ` [PATCH v2 i-g-t] man/lsgpu: Add man page for lsgpu Kamil Konieczny
2025-04-06 20:50 ` ✗ Xe.CI.Full: failure for man/lsgpu: Add man page for lsgpu (rev2) 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=36cb6a97-d985-48df-9140-0a5f2d67fb88@linux.intel.com \
--to=peter.senna@linux.intel.com \
--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 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.