Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: I915-ci-infra@lists.freedesktop.org,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: ✗ CI.xeFULL: failure for runner/executor.c: Detect tests killed by a signal (rev6)
Date: Fri, 4 Oct 2024 07:30:42 +0200	[thread overview]
Message-ID: <3d020bc9-fe0f-4fa3-98ef-995cb5061ff5@linux.intel.com> (raw)
In-Reply-To: <172797844004.1169872.3510633666920658161@2413ebb6fbb6>

Dear I915,

On 03.10.2024 20:00, Patchwork wrote:
> == Series Details ==
> 
> Series: runner/executor.c: Detect tests killed by a signal (rev6)
> URL   : https://patchwork.freedesktop.org/series/137879/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from XEIGT_8051_full -> XEIGTPW_11864_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with XEIGTPW_11864_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in XEIGTPW_11864_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_11864_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@kms_ccs@random-ccs-data-4-tiled-dg2-mc-ccs@pipe-b-hdmi-a-6:
>     - shard-dg2-set2:     NOTRUN -> [DMESG-WARN][1]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11864/shard-dg2-435/igt@kms_ccs@random-ccs-data-4-tiled-dg2-mc-ccs@pipe-b-hdmi-a-6.html
> 
>   * igt@kms_cursor_crc@cursor-random-512x170:
>     - shard-lnl:          NOTRUN -> [SKIP][2]
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11864/shard-lnl-3/igt@kms_cursor_crc@cursor-random-512x170.html
> 
>   * igt@kms_psr_stress_test@flip-primary-invalidate-overlay:
>     - shard-dg2-set2:     NOTRUN -> [SKIP][3]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11864/shard-dg2-466/igt@kms_psr_stress_test@flip-primary-invalidate-overlay.html
> 
>   * igt@xe_ccs@suspend-resume@xmajor-compressed-compfmt0-system-system:
>     - shard-lnl:          [PASS][4] -> [DMESG-WARN][5]
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8051/shard-lnl-3/igt@xe_ccs@suspend-resume@xmajor-compressed-compfmt0-system-system.html
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11864/shard-lnl-8/igt@xe_ccs@suspend-resume@xmajor-compressed-compfmt0-system-system.html
> 
>   * igt@xe_compute_preempt@compute-preempt-many@engine-drm_xe_engine_class_compute:
>     - shard-lnl:          [PASS][6] -> [FAIL][7] +2 other tests fail
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8051/shard-lnl-2/igt@xe_compute_preempt@compute-preempt-many@engine-drm_xe_engine_class_compute.html
>    [7]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11864/shard-lnl-5/igt@xe_compute_preempt@compute-preempt-many@engine-drm_xe_engine_class_compute.html
> 
>   * igt@xe_oa@oa-exponents:
>     - shard-lnl:          [PASS][8] -> [ABORT][9]
>    [8]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8051/shard-lnl-7/igt@xe_oa@oa-exponents.html
>    [9]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11864/shard-lnl-3/igt@xe_oa@oa-exponents.html
> 
>   * igt@xe_oa@oa-exponents@ccs-0:
>     - shard-lnl:          NOTRUN -> [ABORT][10]
>    [10]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11864/shard-lnl-3/igt@xe_oa@oa-exponents@ccs-0.html
> 

These are unrelated to my change. Thank you!

  reply	other threads:[~2024-10-04  5:30 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28  6:40 [PATCH i-g-t] runner/executor.c: Detect tests killed by a signal Peter Senna Tschudin
2024-08-28  8:37 ` ✗ GitLab.Pipeline: warning for " Patchwork
2024-08-28  8:40 ` ✓ CI.xeBAT: success " Patchwork
2024-08-28  8:52 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-08-28 13:15 ` ✗ CI.xeFULL: " Patchwork
2024-08-29 12:13 ` [PATCH i-g-t v2] runner/executor: Detect when child process is " Peter Senna Tschudin
2024-08-29 17:37 ` ✗ CI.xeBAT: failure for runner/executor.c: Detect tests killed by a signal (rev2) Patchwork
2024-08-30  4:28   ` Peter Senna Tschudin
2024-08-29 17:49 ` ✓ Fi.CI.BAT: success " Patchwork
2024-08-30  6:34 ` ✗ CI.xeFULL: failure " Patchwork
2024-08-30 12:39 ` [PATCH i-g-t v3] runner/executor: Detect when child process is killed by a signal Peter Senna Tschudin
2024-08-30 16:19 ` ✓ CI.xeBAT: success for runner/executor.c: Detect tests killed by a signal (rev3) Patchwork
2024-08-30 16:31 ` ✓ Fi.CI.BAT: " Patchwork
2024-08-31  0:57 ` ✗ Fi.CI.IGT: failure for runner/executor.c: Detect tests killed by a signal (rev2) Patchwork
2024-08-31  4:32 ` ✓ CI.xeFULL: success for runner/executor.c: Detect tests killed by a signal (rev3) Patchwork
2024-09-01  3:32 ` ✓ Fi.CI.IGT: " Patchwork
2024-09-03  6:19 ` [PATCH i-g-t v4] runner/executor: Detect when child process is killed by a signal Peter Senna Tschudin
2024-09-03 11:44 ` ✗ Fi.CI.BUILD: failure for runner/executor.c: Detect tests killed by a signal (rev4) Patchwork
2024-09-03 12:05 ` [PATCH i-g-t v5] runner/executor: Detect when child process is killed by a signal Peter Senna Tschudin
2024-09-10 15:58   ` Kamil Konieczny
2024-09-11  7:06     ` Peter Senna Tschudin
2024-09-11 10:50       ` Kamil Konieczny
2024-09-03 12:36 ` ✓ CI.xeBAT: success for runner/executor.c: Detect tests killed by a signal (rev5) Patchwork
2024-09-03 13:04 ` ✓ Fi.CI.BAT: " Patchwork
2024-09-03 14:46 ` ✗ CI.xeFULL: failure " Patchwork
2024-09-03 14:56   ` Peter Senna Tschudin
2024-09-04 14:34 ` ✓ Fi.CI.IGT: success " Patchwork
2024-09-05 10:44 ` ✗ GitLab.Pipeline: warning for runner/executor.c: Detect tests killed by a signal (rev4) Patchwork
2024-10-03 13:27 ` [PATCH i-g-t v6] runner/executor: Abort when child process is killed by a signal Peter Senna Tschudin
2024-10-09 14:46   ` Kamil Konieczny
2024-10-09 16:36   ` Kamil Konieczny
2024-10-11 15:18   ` Kamil Konieczny
2024-10-03 16:17 ` ✓ CI.xeBAT: success for runner/executor.c: Detect tests killed by a signal (rev6) Patchwork
2024-10-03 16:29 ` ✓ Fi.CI.BAT: " Patchwork
2024-10-03 18:00 ` ✗ CI.xeFULL: failure " Patchwork
2024-10-04  5:30   ` Peter Senna Tschudin [this message]
2024-10-04 10:34 ` ✗ GitLab.Pipeline: warning " Patchwork
2024-10-08  3:28 ` ✗ Fi.CI.IGT: failure " 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=3d020bc9-fe0f-4fa3-98ef-995cb5061ff5@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