From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: igt-dev@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ i915.CI.Full: failure for man/lsgpu: Add man page for lsgpu
Date: Thu, 27 Mar 2025 21:03:05 +0100 [thread overview]
Message-ID: <e3e6a7ba-e49b-41b9-ba38-d27e253a09f4@linux.intel.com> (raw)
In-Reply-To: <174309460093.11772.18289412343678412859@e6b6f09ec485>
Dear I915,
On 3/27/2025 5:56 PM, Patchwork wrote:
> == Series Details ==
>
> Series: man/lsgpu: Add man page for lsgpu
> URL : https://patchwork.freedesktop.org/series/146860/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_16326_full -> IGTPW_12857_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with IGTPW_12857_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_12857_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.
>
> External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12857/index.html
>
> Participating hosts (10 -> 10)
> ------------------------------
>
> No changes in participating hosts
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in IGTPW_12857_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
> - shard-rkl: [PASS][1] -> [FAIL][2]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16326/shard-rkl-5/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12857/shard-rkl-5/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
>
> * igt@kms_plane_multiple@2x-tiling-4:
> - shard-dg2: NOTRUN -> [SKIP][3] +2 other tests skip
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12857/shard-dg2-6/igt@kms_plane_multiple@2x-tiling-4.html
> - shard-dg1: NOTRUN -> [SKIP][4]
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12857/shard-dg1-15/igt@kms_plane_multiple@2x-tiling-4.html
>
> * igt@kms_plane_multiple@2x-tiling-none:
> - shard-mtlp: NOTRUN -> [SKIP][5] +1 other test skip
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12857/shard-mtlp-6/igt@kms_plane_multiple@2x-tiling-none.html
> - shard-dg2-9: NOTRUN -> [SKIP][6]
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12857/shard-dg2-9/igt@kms_plane_multiple@2x-tiling-none.html
>
> * igt@kms_plane_multiple@2x-tiling-x:
> - shard-tglu-1: NOTRUN -> [SKIP][7]
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12857/shard-tglu-1/igt@kms_plane_multiple@2x-tiling-x.html
>
> * igt@kms_plane_multiple@2x-tiling-y:
> - shard-rkl: NOTRUN -> [SKIP][8]
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12857/shard-rkl-5/igt@kms_plane_multiple@2x-tiling-y.html
> - shard-tglu: NOTRUN -> [SKIP][9]
> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12857/shard-tglu-5/igt@kms_plane_multiple@2x-tiling-y.html
>
> * igt@kms_vblank@ts-continuation-dpms-suspend:
> - shard-rkl: [PASS][10] -> [INCOMPLETE][11] +1 other test incomplete
> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16326/shard-rkl-5/igt@kms_vblank@ts-continuation-dpms-suspend.html
> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12857/shard-rkl-3/igt@kms_vblank@ts-continuation-dpms-suspend.html
>
> * igt@perf_pmu@rc6@runtime-pm-gt0:
> - shard-rkl: [PASS][12] -> [SKIP][13]
> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16326/shard-rkl-1/igt@perf_pmu@rc6@runtime-pm-gt0.html
> [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12857/shard-rkl-6/igt@perf_pmu@rc6@runtime-pm-gt0.html
>
These are unrelated to my change. Please fix and resubmit.
Thank you,
Peter
next prev parent reply other threads:[~2025-03-27 20:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 11:06 [PATCH i-g-t] man/lsgpu: Add man page for lsgpu Peter Senna Tschudin
2025-03-27 14:54 ` ✗ Xe.CI.BAT: failure for " Patchwork
2025-03-27 16:07 ` Peter Senna Tschudin
2025-03-27 15:13 ` ✓ i915.CI.BAT: success " Patchwork
2025-03-27 16:56 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-27 20:03 ` Peter Senna Tschudin [this message]
2025-03-28 5:30 ` Ravali, JupallyX
2025-03-27 22:40 ` ✗ Xe.CI.Full: " Patchwork
2025-03-28 5:28 ` ✓ i915.CI.Full: success " Patchwork
2025-03-28 8:58 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-28 14:28 ` [PATCH i-g-t] " Kamil Konieczny
2025-04-06 14:37 ` ✗ Xe.CI.Full: failure for " 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=e3e6a7ba-e49b-41b9-ba38-d27e253a09f4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox