Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Maslak <jan.maslak@intel.com>
To: <igt-dev@lists.freedesktop.org>
Cc: <I915-ci-infra@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.Full: failure for tests/intel/xe_eudebug_online: Introduce pagefault stress tests
Date: Thu, 20 Nov 2025 14:31:38 +0100	[thread overview]
Message-ID: <aR8YOhebjyDB/O1K@ART-DEV-395> (raw)
In-Reply-To: <174822733954.19430.1302441528162758370@1538d3639d33>

On Mon, May 26, 2025 at 02:42:19AM +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: tests/intel/xe_eudebug_online: Introduce pagefault stress tests
> URL   : https://patchwork.freedesktop.org/series/149473/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_16594_full -> IGTPW_13178_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_13178_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_13178_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_13178/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_13178_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@i915_module_load@reload-with-fault-injection:
>     - shard-tglu:         NOTRUN -> [DMESG-WARN][1]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13178/shard-tglu-7/igt@i915_module_load@reload-with-fault-injection.html
> 
>   * igt@kms_async_flips@alternate-sync-async-flip@pipe-a-dp-3:
>     - shard-dg2:          NOTRUN -> [FAIL][2]
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13178/shard-dg2-11/igt@kms_async_flips@alternate-sync-async-flip@pipe-a-dp-3.html
> 
>   * igt@kms_flip@flip-vs-suspend-interruptible@a-hdmi-a2 (NEW):
>     - shard-rkl:          NOTRUN -> [INCOMPLETE][3]
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13178/shard-rkl-3/igt@kms_flip@flip-vs-suspend-interruptible@a-hdmi-a2.html
> 
>   * igt@kms_psr@psr2-primary-mmap-cpu:
>     - shard-mtlp:         [PASS][4] -> [FAIL][5] +1 other test fail
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16594/shard-mtlp-6/igt@kms_psr@psr2-primary-mmap-cpu.html
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13178/shard-mtlp-8/igt@kms_psr@psr2-primary-mmap-cpu.html
> 
>   * igt@kms_setmode@basic@pipe-a-hdmi-a-2:
>     - shard-rkl:          [PASS][6] -> [FAIL][7]
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16594/shard-rkl-8/igt@kms_setmode@basic@pipe-a-hdmi-a-2.html
>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13178/shard-rkl-8/igt@kms_setmode@basic@pipe-a-hdmi-a-2.html

These regressions aren't related to my Xe IGT patches.

      reply	other threads:[~2025-11-20 13:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26  0:13 [PATCH 0/2] tests/intel/xe_eudebug_online: Introduce pagefault stress tests Jan Maslak
2025-05-26  0:13 ` [PATCH 1/2] lib/gpu_cmds: expose num_threads_in_tg parameter for tests Jan Maslak
2025-06-02 12:54   ` Gwan-gyeong Mun
2025-06-02 19:19     ` Zbigniew Kempczyński
2025-05-26  0:13 ` [PATCH 2/2] tests/intel/xe_eudebug_online: Add pagefault stress tests Jan Maslak
2025-06-02 15:14   ` Gwan-gyeong Mun
2025-05-26  0:48 ` ✓ Xe.CI.BAT: success for tests/intel/xe_eudebug_online: Introduce " Patchwork
2025-05-26  1:00 ` ✓ i915.CI.BAT: " Patchwork
2025-05-26  2:36 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-26  2:42 ` ✗ i915.CI.Full: " Patchwork
2025-11-20 13:31   ` Jan Maslak [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=aR8YOhebjyDB/O1K@ART-DEV-395 \
    --to=jan.maslak@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