Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Hajda <andrzej.hajda@intel.com>
To: intel-xe@lists.freedesktop.org,
	Patchwork <patchwork@emeril.freedesktop.org>,
	I915-ci-infra@lists.freedesktop.org
Subject: Re: â CI.BAT: failure for drm/xe: flush gtt before signalling user fence on all engines
Date: Fri, 24 May 2024 16:22:53 +0200	[thread overview]
Message-ID: <02161ef7-84ea-4411-84e7-9f309ed6d32c@intel.com> (raw)
In-Reply-To: <171636721390.2166515.6639451569991799640@8e613ede5ea5>

On 22.05.2024 10:40, Patchwork wrote:
> *Patch Details*
> *Series:*	drm/xe: flush gtt before signalling user fence on all engines
> *URL:*	https://patchwork.freedesktop.org/series/133906/ 
> <https://patchwork.freedesktop.org/series/133906/>
> *State:*	failure
> *Details:* 
> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-133906v1/index.html 
> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-133906v1/index.html>
> 
> 
>   CI Bug Log - changes from
>   xe-1323-b134db8544f8d5b8a960b368afe12820c3cbe8cd_BAT -> xe-pw-133906v1_BAT
> 
> 
>     Summary
> 
> *FAILURE*
> 
> Serious unknown changes coming with xe-pw-133906v1_BAT absolutely need to be
> verified manually.
> 
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-133906v1_BAT, 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 (5 -> 4)
> 
> Missing (1): bat-pvc-2
> 
> 
>     Possible new issues
> 
> Here are the unknown changes that may have been introduced in 
> xe-pw-133906v1_BAT:
> 
> 
>       IGT changes
> 
> 
>         Possible regressions
> 
>   * igt@xe_exec_threads@threads-mixed-shared-vm-userptr-invalidate-race:
>       o bat-atsm-2: NOTRUN -> INCOMPLETE
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-133906v1/bat-atsm-2/igt@xe_exec_threads@threads-mixed-shared-vm-userptr-invalidate-race.html>

Not related, already observed on[1]

[1]: 
https://intel-gfx-ci.01.org/tree/intel-xe/xe-1317-39e2349c88dab7b39cf2c9549783e9b1e03311ad/bat-lnl-1/igt@xe_exec_threads@threads-mixed-fd-basic.html



> 
> 
>         Suppressed
> 
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
> 
>   * igt@xe_dma_buf_sync@export-dma-buf-once:
>       o {bat-lnl-1}: PASS
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-1323-b134db8544f8d5b8a960b368afe12820c3cbe8cd/bat-lnl-1/igt@xe_dma_buf_sync@export-dma-buf-once.html> -> ABORT <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-133906v1/bat-lnl-1/igt@xe_dma_buf_sync@export-dma-buf-once.html>

ditto

Apparently there is bug filled for it [2], probably created after this 
run. Re-test submitted.

[2]: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/1908

Regards
Andrzej

> 
> 
>     Known issues
> 
> Here are the changes found in xe-pw-133906v1_BAT that come from known 
> issues:
> 
> 
>       IGT changes
> 
> 
>         Issues hit
> 
>   *
> 
>     igt@xe_evict@evict-small-cm:
> 
>       o bat-adlp-7: NOTRUN -> SKIP
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-133906v1/bat-adlp-7/igt@xe_evict@evict-small-cm.html> (Intel XE#261 <https://gitlab.freedesktop.org/drm/xe/kernel/issues/261> / Intel XE#688 <https://gitlab.freedesktop.org/drm/xe/kernel/issues/688>) +15 other tests skip
>   *
> 
>     igt@xe_exec_fault_mode@twice-userptr-invalidate-imm:
> 
>       o bat-atsm-2: NOTRUN -> SKIP
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-133906v1/bat-atsm-2/igt@xe_exec_fault_mode@twice-userptr-invalidate-imm.html> (Intel XE#288 <https://gitlab.freedesktop.org/drm/xe/kernel/issues/288>) +32 other tests skip
>   *
> 
>     igt@xe_huc_copy@huc_copy:
> 
>       o bat-atsm-2: NOTRUN -> SKIP
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-133906v1/bat-atsm-2/igt@xe_huc_copy@huc_copy.html> (Intel XE#255 <https://gitlab.freedesktop.org/drm/xe/kernel/issues/255>)
>   *
> 
>     igt@xe_pat@pat-index-xe2:
> 
>       o bat-atsm-2: NOTRUN -> SKIP
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-133906v1/bat-atsm-2/igt@xe_pat@pat-index-xe2.html> (Intel XE#977 <https://gitlab.freedesktop.org/drm/xe/kernel/issues/977>)
>   *
> 
>     igt@xe_pat@pat-index-xehpc:
> 
>       o bat-atsm-2: NOTRUN -> SKIP
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-133906v1/bat-atsm-2/igt@xe_pat@pat-index-xehpc.html> (Intel XE#979 <https://gitlab.freedesktop.org/drm/xe/kernel/issues/979>) +1 other test skip
> 
> 
>         Possible fixes
> 
>   * igt@xe_exec_threads@threads-mixed-fd-basic:
>       o bat-adlp-7: ABORT
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-1323-b134db8544f8d5b8a960b368afe12820c3cbe8cd/bat-adlp-7/igt@xe_exec_threads@threads-mixed-fd-basic.html> (Intel XE#1908 <https://gitlab.freedesktop.org/drm/xe/kernel/issues/1908>) -> PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-133906v1/bat-adlp-7/igt@xe_exec_threads@threads-mixed-fd-basic.html>
> 
> {name}: This element is suppressed. This means it is ignored when computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
> 
> 
>     Build changes
> 
>   * Linux: xe-1323-b134db8544f8d5b8a960b368afe12820c3cbe8cd ->
>     xe-pw-133906v1
> 
> IGT_7867: f3006a13799e3bc45d754aa8ad318394277d69ac @ 
> https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> xe-1323-b134db8544f8d5b8a960b368afe12820c3cbe8cd: 
> b134db8544f8d5b8a960b368afe12820c3cbe8cd
> xe-pw-133906v1: 133906v1
> 


  reply	other threads:[~2024-05-24 14:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22  7:27 [PATCH v2] drm/xe: flush gtt before signalling user fence on all engines Andrzej Hajda
2024-05-22  7:33 ` ✓ CI.Patch_applied: success for " Patchwork
2024-05-22  7:33 ` ✓ CI.checkpatch: " Patchwork
2024-05-22  7:34 ` ✓ CI.KUnit: " Patchwork
2024-05-22  7:46 ` ✓ CI.Build: " Patchwork
2024-05-22  7:48 ` ✓ CI.Hooks: " Patchwork
2024-05-22  7:50 ` ✓ CI.checksparse: " Patchwork
2024-05-22  8:40 ` ✗ CI.BAT: failure " Patchwork
2024-05-24 14:22   ` Andrzej Hajda [this message]
2024-05-22 10:34 ` ✗ CI.FULL: " Patchwork
2024-05-24 14:30   ` â " Andrzej Hajda
2024-05-24 14:33 ` ✓ CI.Patch_applied: success for drm/xe: flush gtt before signalling user fence on all engines (rev2) Patchwork
2024-05-24 14:33 ` ✓ CI.checkpatch: " Patchwork
2024-05-24 14:34 ` ✓ CI.KUnit: " Patchwork
2024-05-24 14:45 ` ✓ CI.Build: " Patchwork
2024-05-24 14:48 ` ✓ CI.Hooks: " Patchwork
2024-05-24 14:49 ` ✓ CI.checksparse: " Patchwork
2024-05-24 15:17 ` ✓ CI.BAT: " Patchwork
2024-05-27 13:31 ` ✓ CI.FULL: " Patchwork
2024-05-28 11:35 ` [PATCH v2] drm/xe: flush gtt before signalling user fence on all engines Andrzej Hajda
2024-05-28 12:41   ` Nirmoy Das
2024-05-30 11:17 ` Thomas Hellström
2024-05-30 20:45   ` Matthew Brost
2024-06-03  7:35     ` Thomas Hellström
2024-06-03  8:11       ` Andrzej Hajda
2024-06-03  8:47         ` Thomas Hellström
2024-06-03  9:31           ` Thomas Hellström
2024-06-03 10:19             ` Andrzej Hajda
2024-06-03 11:59               ` Thomas Hellström
2024-06-03 17:42           ` Matthew Brost
2024-06-03 20:35             ` Thomas Hellström
2024-06-03 22:28               ` Matthew Brost

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=02161ef7-84ea-4411-84e7-9f309ed6d32c@intel.com \
    --to=andrzej.hajda@intel.com \
    --cc=I915-ci-infra@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=patchwork@emeril.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