Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: igt-dev@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for igt_facts for fact tracking (rev2)
Date: Tue, 17 Dec 2024 06:14:27 +0100	[thread overview]
Message-ID: <b94c44a9-fb30-494c-bb94-f9dd4dd51cdf@linux.intel.com> (raw)
In-Reply-To: <173440905071.3597928.14164347048680210557@b555e5b46a47>

Dear I915,

On 17.12.2024 05:17, Patchwork wrote:
> == Series Details ==
> 
> Series: igt_facts for fact tracking (rev2)
> URL   : https://patchwork.freedesktop.org/series/142628/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from XEIGT_8157_full -> XEIGTPW_12325_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with XEIGTPW_12325_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in XEIGTPW_12325_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_12325_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@kms_async_flips@crc-atomic@pipe-a-hdmi-a-6:
>     - shard-dg2-set2:     NOTRUN -> [INCOMPLETE][1] +3 other tests incomplete
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12325/shard-dg2-463/igt@kms_async_flips@crc-atomic@pipe-a-hdmi-a-6.html
> 
>   * igt@kms_flip@2x-flip-vs-suspend-interruptible@ab-dp2-hdmi-a3:
>     - shard-bmg:          NOTRUN -> [FAIL][2]
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12325/shard-bmg-3/igt@kms_flip@2x-flip-vs-suspend-interruptible@ab-dp2-hdmi-a3.html
> 
>   * igt@kms_flip@2x-plain-flip-ts-check-interruptible@ab-hdmi-a6-dp4:
>     - shard-dg2-set2:     [PASS][3] -> [FAIL][4] +2 other tests fail
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8157/shard-dg2-463/igt@kms_flip@2x-plain-flip-ts-check-interruptible@ab-hdmi-a6-dp4.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12325/shard-dg2-464/igt@kms_flip@2x-plain-flip-ts-check-interruptible@ab-hdmi-a6-dp4.html
> 
>   * igt@kms_flip@flip-vs-expired-vblank-interruptible@a-hdmi-a6:
>     - shard-dg2-set2:     NOTRUN -> [FAIL][5]
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12325/shard-dg2-436/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-hdmi-a6.html
> 
>   * igt@kms_flip@flip-vs-suspend-interruptible@d-dp2:
>     - shard-bmg:          [PASS][6] -> [FAIL][7] +1 other test fail
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8157/shard-bmg-4/igt@kms_flip@flip-vs-suspend-interruptible@d-dp2.html
>    [7]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12325/shard-bmg-4/igt@kms_flip@flip-vs-suspend-interruptible@d-dp2.html
> 
>   * igt@kms_pipe_crc_basic@suspend-read-crc@pipe-b-dp-4:
>     - shard-dg2-set2:     [PASS][8] -> [INCOMPLETE][9] +1 other test incomplete
>    [8]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8157/shard-dg2-433/igt@kms_pipe_crc_basic@suspend-read-crc@pipe-b-dp-4.html
>    [9]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12325/shard-dg2-436/igt@kms_pipe_crc_basic@suspend-read-crc@pipe-b-dp-4.html
> 
>   * igt@kms_vblank@ts-continuation-suspend:
>     - shard-bmg:          [PASS][10] -> [INCOMPLETE][11] +9 other tests incomplete
>    [10]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8157/shard-bmg-8/igt@kms_vblank@ts-continuation-suspend.html
>    [11]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12325/shard-bmg-7/igt@kms_vblank@ts-continuation-suspend.html
> 
>   * igt@xe_wedged@basic-wedged:
>     - shard-bmg:          [PASS][12] -> [ABORT][13]
>    [12]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8157/shard-bmg-2/igt@xe_wedged@basic-wedged.html
>    [13]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12325/shard-bmg-5/igt@xe_wedged@basic-wedged.html
> 
>   
> #### Warnings ####
> 
>   * igt@xe_live_ktest@xe_bo:
>     - shard-dg2-set2:     [TIMEOUT][14] ([Intel XE#2961] / [Intel XE#2998]) -> [INCOMPLETE][15] +1 other test incomplete
>    [14]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8157/shard-dg2-436/igt@xe_live_ktest@xe_bo.html
>    [15]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12325/shard-dg2-464/igt@xe_live_ktest@xe_bo.html
> 

Possible regressions and warnings are not related to my change. Please fix and re-run.

[...]

Thank you!

  reply	other threads:[~2024-12-17  5:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 15:14 [PATCH i-g-t v14 resend 0/3] igt_facts for fact tracking Peter Senna Tschudin
2024-12-16 15:14 ` [PATCH i-g-t v14 resend 1/3] lib/igt_facts: Library and unit testing " Peter Senna Tschudin
2024-12-19 12:40   ` Kamil Konieczny
2025-01-21  8:16     ` Peter Senna Tschudin
2025-01-21 11:52       ` Kamil Konieczny
2024-12-20  8:50   ` Kamil Konieczny
2024-12-16 15:14 ` [PATCH i-g-t v14 resend 2/3] tools/lsfacts: Add tool for listing facts Peter Senna Tschudin
2024-12-16 15:14 ` [PATCH i-g-t v14 resend 3/3] runner/executor: Integrate igt_facts functionality Peter Senna Tschudin
2024-12-16 21:40 ` ✗ i915.CI.BAT: failure for igt_facts for fact tracking (rev2) Patchwork
2024-12-17  5:12   ` Peter Senna Tschudin
2024-12-17 13:58     ` Ravali, JupallyX
2024-12-17  0:00 ` ✓ Xe.CI.BAT: success " Patchwork
2024-12-17  4:17 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-17  5:14   ` Peter Senna Tschudin [this message]
2024-12-17  9:33 ` ✓ i915.CI.BAT: success " Patchwork
2024-12-17 14:25 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-18  5:18   ` Peter Senna Tschudin
2024-12-19  4:56     ` Peter Senna Tschudin
2024-12-19  7:28     ` Ravali, JupallyX
2024-12-19  7:18 ` ✓ i915.CI.Full: success " 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=b94c44a9-fb30-494c-bb94-f9dd4dd51cdf@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