From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: igt-dev@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ CI.xeFULL: failure for tests/intel/xe_pm: Fix code style issues (rev2)
Date: Mon, 14 Oct 2024 07:25:40 +0200 [thread overview]
Message-ID: <89e0b566-6af7-47dd-8090-51e1c8f6de39@linux.intel.com> (raw)
In-Reply-To: <172781790041.1143800.3127418124277242020@2413ebb6fbb6>
Dear I915,
On 01.10.2024 23:25, Patchwork wrote:
> == Series Details ==
>
> Series: tests/intel/xe_pm: Fix code style issues (rev2)
> URL : https://patchwork.freedesktop.org/series/139357/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from XEIGT_8047_full -> XEIGTPW_11851_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with XEIGTPW_11851_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in XEIGTPW_11851_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_11851_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_3d:
> - shard-lnl: NOTRUN -> [SKIP][1]
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11851/shard-lnl-3/igt@kms_3d.html
>
> * igt@xe_exec_compute_mode@many-bindexecqueue-userptr-invalidate-race:
> - shard-lnl: [PASS][2] -> [FAIL][3]
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8047/shard-lnl-2/igt@xe_exec_compute_mode@many-bindexecqueue-userptr-invalidate-race.html
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11851/shard-lnl-4/igt@xe_exec_compute_mode@many-bindexecqueue-userptr-invalidate-race.html
>
> * igt@xe_exec_compute_mode@once-bindexecqueue-userptr-invalidate-race:
> - shard-lnl: NOTRUN -> [FAIL][4]
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11851/shard-lnl-1/igt@xe_exec_compute_mode@once-bindexecqueue-userptr-invalidate-race.html
>
> * igt@xe_exec_mix_modes@exec-simple-batch-store-lr:
> - shard-dg2-set2: NOTRUN -> [SKIP][5] +3 other tests skip
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11851/shard-dg2-433/igt@xe_exec_mix_modes@exec-simple-batch-store-lr.html
>
> * igt@xe_pm_residency@gt-c6-freeze:
> - shard-dg2-set2: NOTRUN -> [ABORT][6] +1 other test abort
> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11851/shard-dg2-466/igt@xe_pm_residency@gt-c6-freeze.html
>
> * igt@xe_tlb@basic-tlb:
> - shard-dg2-set2: NOTRUN -> [FAIL][7]
> [7]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11851/shard-dg2-435/igt@xe_tlb@basic-tlb.html
These are unrelated to my change.
Thanks,
Peter
next prev parent reply other threads:[~2024-10-14 5:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 5:13 [PATCH] tests/intel/xe_pm: Fix code style issues Peter Senna Tschudin
2024-10-01 7:36 ` ✓ CI.xeBAT: success for " Patchwork
2024-10-01 7:50 ` ✓ Fi.CI.BAT: " Patchwork
2024-10-01 11:38 ` [PATCH] " Kamil Konieczny
2024-10-01 11:55 ` [PATCH i-g-t V2] " Peter Senna Tschudin
2024-10-01 13:26 ` ✓ CI.xeBAT: success for tests/intel/xe_pm: Fix code style issues (rev2) Patchwork
2024-10-01 13:49 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-10-01 14:16 ` Peter Senna Tschudin
2024-10-01 14:51 ` ✗ CI.xeFULL: failure for tests/intel/xe_pm: Fix code style issues Patchwork
2024-10-01 21:25 ` ✗ CI.xeFULL: failure for tests/intel/xe_pm: Fix code style issues (rev2) Patchwork
2024-10-14 5:25 ` Peter Senna Tschudin [this message]
2024-10-02 0:22 ` ✗ Fi.CI.IGT: failure for tests/intel/xe_pm: Fix code style issues 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=89e0b566-6af7-47dd-8090-51e1c8f6de39@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