Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hajda, Andrzej" <andrzej.hajda@intel.com>
To: <intel-xe@lists.freedesktop.org>,
	Patchwork <patchwork@emeril.freedesktop.org>,
	<I915-ci-infra@lists.freedesktop.org>
Subject: Re: â CI.FULL: failure for drm/xe: add system memory page iterator support to xe_res_cursor (rev3)
Date: Fri, 18 Oct 2024 14:08:25 +0200	[thread overview]
Message-ID: <cb7ce6ea-826b-47b3-ab3d-a12d938956f8@intel.com> (raw)
In-Reply-To: <172863688596.1239783.15277639754896881103@2413ebb6fbb6>

W dniu 11.10.2024 o 10:54, Patchwork pisze:
> *Patch Details*
> *Series:*	drm/xe: add system memory page iterator support to 
> xe_res_cursor (rev3)
> *URL:*	https://patchwork.freedesktop.org/series/139780/ <https:// 
> patchwork.freedesktop.org/series/139780/>
> *State:*	failure
> *Details:*	https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-139780v3/ 
> index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-139780v3/ 
> index.html>
> 
> 
>   CI Bug Log - changes from xe-2046-
>   f3354eab2a45420cf38a67f6d7735d5dff53eb6f_full -> xe-pw-139780v3_full
> 
> 
>     Summary
> 
> *FAILURE*
> 
> Serious unknown changes coming with xe-pw-139780v3_full absolutely need 
> to be
> verified manually.
> 
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-139780v3_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 xe- 
> pw-139780v3_full:
> 
> 
>       IGT changes
> 
> 
>         Possible regressions
> 
>   *
> 
>     igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc@pipe-a-hdmi-a-6:
> 
>       o shard-dg2-set2: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/
>         xe-2046-f3354eab2a45420cf38a67f6d7735d5dff53eb6f/shard-dg2-434/
>         igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc@pipe-a-hdmi-
>         a-6.html> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/intel-
>         xe/xe-pw-139780v3/shard-dg2-434/igt@kms_ccs@random-ccs-data-4-
>         tiled-dg2-rc-ccs-cc@pipe-a-hdmi-a-6.html>
>   *
> 
>     igt@kms_flip@plain-flip-ts-check:
> 
>       o shard-adlp: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/
>         xe-2046-f3354eab2a45420cf38a67f6d7735d5dff53eb6f/shard-adlp-4/
>         igt@kms_flip@plain-flip-ts-check.html> -> FAIL <https://intel-
>         gfx-ci.01.org/tree/intel-xe/xe-pw-139780v3/shard-adlp-1/
>         igt@kms_flip@plain-flip-ts-check.html> +2 other tests fail
>   *
> 
>     igt@kms_hdmi_inject@inject-4k:
> 
>       o shard-adlp: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/
>         xe-2046-f3354eab2a45420cf38a67f6d7735d5dff53eb6f/shard-adlp-3/
>         igt@kms_hdmi_inject@inject-4k.html> -> DMESG-WARN <https://
>         intel-gfx-ci.01.org/tree/intel-xe/xe-pw-139780v3/shard-adlp-6/
>         igt@kms_hdmi_inject@inject-4k.html> +1 other test dmesg-warn
>   *
> 
>     igt@xe_drm_fdinfo@utilization-single-full-load-isolation:
> 
>       o shard-lnl: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/
>         xe-2046-f3354eab2a45420cf38a67f6d7735d5dff53eb6f/shard-lnl-8/
>         igt@xe_drm_fdinfo@utilization-single-full-load-isolation.html> -
>          > INCOMPLETE <https://intel-gfx-ci.01.org/tree/intel-xe/xe-
>         pw-139780v3/shard-lnl-4/igt@xe_drm_fdinfo@utilization-single-
>         full-load-isolation.html>
> 
> 
>         Suppressed
> 
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
> 
>   *
> 
>     igt@kms_async_flips@async-flip-suspend-resume@pipe-d-dp-2:
> 
>       o {shard-bmg}: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/
>         xe-2046-f3354eab2a45420cf38a67f6d7735d5dff53eb6f/shard-bmg-4/
>         igt@kms_async_flips@async-flip-suspend-resume@pipe-d-dp-2.html>
>         -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/intel-xe/xe-
>         pw-139780v3/shard-bmg-7/igt@kms_async_flips@async-flip-suspend-
>         resume@pipe-d-dp-2.html>
>   *
> 
>     igt@kms_big_fb@linear-32bpp-rotate-0:
> 
>       o {shard-bmg}: NOTRUN -> INCOMPLETE <https://intel-gfx-ci.01.org/
>         tree/intel-xe/xe-pw-139780v3/shard-bmg-6/
>         igt@kms_big_fb@linear-32bpp-rotate-0.html>
>   *
> 
>     igt@xe_gt_freq@throttle_basic_api:
> 
>       o {shard-bmg}: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/
>         xe-2046-f3354eab2a45420cf38a67f6d7735d5dff53eb6f/shard-bmg-2/
>         igt@xe_gt_freq@throttle_basic_api.html> -> FAIL <https://intel-
>         gfx-ci.01.org/tree/intel-xe/xe-pw-139780v3/shard-bmg-4/
>         igt@xe_gt_freq@throttle_basic_api.html>
> 


Nothing related to the patch, please update the filters.

Anyway, the patch is not accepted atm for merge.

Regards
Andrzej


  reply	other threads:[~2024-10-18 12:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  7:26 [PATCH v3] drm/xe: add system memory page iterator support to xe_res_cursor Andrzej Hajda
2024-10-11  7:31 ` ✓ CI.Patch_applied: success for drm/xe: add system memory page iterator support to xe_res_cursor (rev3) Patchwork
2024-10-11  7:31 ` ✓ CI.checkpatch: " Patchwork
2024-10-11  7:33 ` ✓ CI.KUnit: " Patchwork
2024-10-11  7:44 ` ✓ CI.Build: " Patchwork
2024-10-11  7:46 ` ✓ CI.Hooks: " Patchwork
2024-10-11  7:48 ` ✓ CI.checksparse: " Patchwork
2024-10-11  8:07 ` ✓ CI.BAT: " Patchwork
2024-10-11  8:54 ` ✗ CI.FULL: failure " Patchwork
2024-10-18 12:08   ` Hajda, Andrzej [this message]
2024-10-12  2:23 ` [PATCH v3] drm/xe: add system memory page iterator support to xe_res_cursor Matthew Brost
2024-10-14  8:18   ` Hajda, Andrzej
2024-10-15  4:58     ` Matthew Brost
2024-10-15 10:48       ` Hajda, Andrzej

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=cb7ce6ea-826b-47b3-ab3d-a12d938956f8@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