Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: <igt-dev@lists.freedesktop.org>,
	Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
	<I915-ci-infra@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.Full: failure for tools/igt_power: fix Xe crash via drmtest path helpers
Date: Wed, 3 Jun 2026 09:49:42 +0200	[thread overview]
Message-ID: <DIZ8ZWJ2AQJU.138ZNL1LXVX04@intel.com> (raw)
In-Reply-To: <178045488091.38098.11789898288908217698@6beec6c84f66>

Hi CI-infra team

On Wed Jun 3, 2026 at 4:48 AM CEST, Patchwork wrote:
> == Series Details ==
>
> Series: tools/igt_power: fix Xe crash via drmtest path helpers
> URL   : https://patchwork.freedesktop.org/series/167738/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_18603_full -> IGTPW_15285_full
> ====================================================
>
> Summary
> -------
>
>   **FAILURE**
>
>   Serious unknown changes coming with IGTPW_15285_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_15285_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_15285/index.html
>
> Participating hosts (11 -> 10)
> ------------------------------
>
>   Missing    (1): pig-kbl-iris 
>
> Possible new issues
> -------------------
>
>   Here are the unknown changes that may have been introduced in IGTPW_15285_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
>   * igt@i915_module_load@fault-injection@uc_fw_rsa_data_create:
>     - shard-dg2:          [PASS][1] -> [DMESG-WARN][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18603/shard-dg2-1/igt@i915_module_load@fault-injection@uc_fw_rsa_data_create.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_15285/shard-dg2-7/igt@i915_module_load@fault-injection@uc_fw_rsa_data_create.html
>
>   * igt@syncobj_wait (NEW):
>     - shard-snb:          NOTRUN -> [INCOMPLETE][3]
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_15285/shard-snb4/igt@syncobj_wait.html
>
>   
These failures are not related to the series. The series only resolves
the issue with the tool.


-- 
Best regards,
Sebastian


      reply	other threads:[~2026-06-03  7:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 11:50 [PATCH i-g-t v6 0/2] tools/igt_power: fix Xe crash via drmtest path helpers Sebastian Brzezinka
2026-06-02 11:50 ` [PATCH v6 1/2] lib/drmtest: add drm_open_driver_path() Sebastian Brzezinka
2026-06-02 14:00   ` Kamil Konieczny
2026-06-03  8:41   ` Krzysztof Karas
2026-06-02 11:50 ` [PATCH v6 2/2] tools/igt_power: initialize xe_device cache Sebastian Brzezinka
2026-06-03  8:42   ` Krzysztof Karas
2026-06-02 15:30 ` ✓ Xe.CI.BAT: success for tools/igt_power: fix Xe crash via drmtest path helpers Patchwork
2026-06-02 15:41 ` ✓ i915.CI.BAT: " Patchwork
2026-06-02 23:01 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-06-11 11:11   ` Sebastian Brzezinka
2026-06-03  2:48 ` ✗ i915.CI.Full: " Patchwork
2026-06-03  7:49   ` Sebastian Brzezinka [this message]

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=DIZ8ZWJ2AQJU.138ZNL1LXVX04@intel.com \
    --to=sebastian.brzezinka@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