Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pawel Sikora <pawel.sikora@linux.intel.com>
To: igt-dev@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ i915.CI.Full: failure for lib/igt_core: capture logs for child processes (rev4)
Date: Mon, 24 Mar 2025 12:00:12 +0100	[thread overview]
Message-ID: <20250324110012.llo2qrnuaqqggbxe@pawelsik-desk> (raw)
In-Reply-To: <174260451131.66435.3086604280866089528@18a75f3d1eae>

Hi I915,

On Sat, Mar 22, 2025 at 12:48:31AM -0000, Patchwork wrote:
> == Series Details ==
> 
> Series: lib/igt_core: capture logs for child processes (rev4)
> URL   : https://patchwork.freedesktop.org/series/146262/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_16301_full -> IGTPW_12812_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_12812_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_12812_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_12812/index.html
> 
> Participating hosts (9 -> 10)
> ------------------------------
> 
>   Additional (1): shard-glk-0 
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_12812_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@kms_flip@flip-vs-blocking-wf-vblank:
>     - shard-snb:          [PASS][1] -> [FAIL][2] +1 other test fail
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16301/shard-snb2/igt@kms_flip@flip-vs-blocking-wf-vblank.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12812/shard-snb6/igt@kms_flip@flip-vs-blocking-wf-vblank.html
> 
>   * igt@kms_flip@flip-vs-blocking-wf-vblank@a-edp1:
>     - shard-mtlp:         [PASS][3] -> [FAIL][4] +1 other test fail
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16301/shard-mtlp-1/igt@kms_flip@flip-vs-blocking-wf-vblank@a-edp1.html
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12812/shard-mtlp-8/igt@kms_flip@flip-vs-blocking-wf-vblank@a-edp1.html
> 
>   * igt@kms_flip@flip-vs-blocking-wf-vblank@b-dp4:
>     - shard-dg2:          [PASS][5] -> [FAIL][6] +2 other tests fail
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16301/shard-dg2-10/igt@kms_flip@flip-vs-blocking-wf-vblank@b-dp4.html
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12812/shard-dg2-10/igt@kms_flip@flip-vs-blocking-wf-vblank@b-dp4.html
> 
>   * igt@kms_flip@wf_vblank-ts-check-interruptible@b-hdmi-a1:
>     - shard-tglu:         NOTRUN -> [FAIL][7] +1 other test fail
>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12812/shard-tglu-7/igt@kms_flip@wf_vblank-ts-check-interruptible@b-hdmi-a1.html
> 

Unrelated to my change.

Regards,
Pawel

      reply	other threads:[~2025-03-24 11:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21 12:03 [PATCH i-g-t v3 0/1] lib/igt_core: capture logs for child processes Pawel Sikora
2025-03-21 12:03 ` [PATCH i-g-t v3 1/1] " Pawel Sikora
2025-03-21 18:28   ` Kamil Konieczny
2025-03-21 20:15 ` ✓ Xe.CI.BAT: success for lib/igt_core: capture logs for child processes (rev4) Patchwork
2025-03-21 20:19 ` ✓ i915.CI.BAT: " Patchwork
2025-03-21 22:14 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-24 11:02   ` Pawel Sikora
2025-03-22  0:48 ` ✗ i915.CI.Full: " Patchwork
2025-03-24 11:00   ` Pawel Sikora [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=20250324110012.llo2qrnuaqqggbxe@pawelsik-desk \
    --to=pawel.sikora@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