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.BAT: failure for lib/xe/xe_legacy: Move test_legacy_mode to lib/
Date: Fri, 18 Apr 2025 11:21:55 +0200 [thread overview]
Message-ID: <e1f151be-b065-4a46-8631-a6b5ba113ec1@linux.intel.com> (raw)
In-Reply-To: <174492616955.16326.17505699909884413079@b68e5b3b99e1>
Dear I915,
On 4/17/2025 11:42 PM, Patchwork wrote:
> == Series Details ==
>
> Series: lib/xe/xe_legacy: Move test_legacy_mode to lib/
> URL : https://patchwork.freedesktop.org/series/147939/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from IGT_8326 -> IGTPW_13004
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with IGTPW_13004 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_13004, 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_13004/index.html
>
> Participating hosts (45 -> 44)
> ------------------------------
>
> Missing (1): fi-snb-2520m
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in IGTPW_13004:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@i915_selftest@live@workarounds:
> - bat-rplp-1: [PASS][1] -> [ABORT][2] +1 other test abort
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8326/bat-rplp-1/igt@i915_selftest@live@workarounds.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13004/bat-rplp-1/igt@i915_selftest@live@workarounds.html
>
Unrelated to my change. Please fix and re-run.
Thank you,
Peter
next prev parent reply other threads:[~2025-04-18 9:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 19:30 [PATCH RFC i-g-t] lib/xe/xe_legacy: Move test_legacy_mode to lib/ Peter Senna Tschudin
2025-04-17 21:42 ` ✗ i915.CI.BAT: failure for " Patchwork
2025-04-18 9:21 ` Peter Senna Tschudin [this message]
2025-04-21 12:21 ` Ravali, JupallyX
2025-04-17 22:00 ` ✗ Xe.CI.BAT: " Patchwork
2025-04-18 9:20 ` Peter Senna Tschudin
2025-04-18 15:43 ` ✗ Xe.CI.Full: " Patchwork
2025-04-21 10:32 ` ✗ i915.CI.BAT: " Patchwork
2025-04-21 11:02 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-21 12:34 ` ✓ i915.CI.Full: " Patchwork
2025-04-24 17:36 ` [PATCH i-g-t] " Peter Senna Tschudin
2025-04-28 21:40 ` Dong, Zhanjun
2025-04-24 18:57 ` ✗ i915.CI.BAT: failure for lib/xe/xe_legacy: Move test_legacy_mode to lib/ (rev2) Patchwork
2025-04-26 8:06 ` Peter Senna Tschudin
2025-04-24 19:12 ` ✓ Xe.CI.BAT: success " Patchwork
2025-05-08 10:10 ` [PATCH v2 i-g-t] lib/xe/xe_legacy: Move test_legacy_mode to lib/ Peter Senna Tschudin
2025-05-12 23:26 ` Dong, Zhanjun
2025-05-08 19:52 ` ✓ Xe.CI.BAT: success for lib/xe/xe_legacy: Move test_legacy_mode to lib/ (rev3) Patchwork
2025-05-08 20:05 ` ✓ i915.CI.BAT: " Patchwork
2025-05-08 22:54 ` ✗ i915.CI.Full: failure " Patchwork
2025-05-09 7:39 ` Peter Senna Tschudin
2025-05-09 11:32 ` ✗ Xe.CI.Full: " Patchwork
2025-05-09 11:46 ` Peter Senna Tschudin
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=e1f151be-b065-4a46-8631-a6b5ba113ec1@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