From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ CI.FULL: failure for Prefer GT oriented logs/asserts in submit code
Date: Sat, 9 Nov 2024 15:14:59 +0100 [thread overview]
Message-ID: <05a4c78c-22a0-4a3b-bc4e-66577637859e@intel.com> (raw)
In-Reply-To: <173111858505.1509041.12925856584925267535@2413ebb6fbb6>
On 09.11.2024 03:16, Patchwork wrote:
> == Series Details ==
>
> Series: Prefer GT oriented logs/asserts in submit code
> URL : https://patchwork.freedesktop.org/series/141063/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-2184-85b1b17ed748e1f68ac83052916a95d624405c97_full -> xe-pw-141063v1_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-141063v1_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-141063v1_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-141063v1_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
all unrelated
>
> * igt@core_getversion@all-cards:
> - shard-dg2-set2: [PASS][1] -> [FAIL][2]
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2184-85b1b17ed748e1f68ac83052916a95d624405c97/shard-dg2-466/igt@core_getversion@all-cards.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141063v1/shard-dg2-434/igt@core_getversion@all-cards.html
(core_getversion:2196) drmtest-DEBUG: Looking for devices to open using
filter 0: pci:vendor=intel,device=discrete,card=0
(core_getversion:2196) drmtest-WARNING: No card matches the filter!
[pci:vendor=intel,device=discrete,card=0]
>
> * igt@kms_flip@plain-flip-ts-check-interruptible@a-hdmi-a3:
> - shard-bmg: NOTRUN -> [INCOMPLETE][3]
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141063v1/shard-bmg-1/igt@kms_flip@plain-flip-ts-check-interruptible@a-hdmi-a3.html
>
> * igt@kms_rotation_crc@primary-y-tiled-reflect-x-90:
> - shard-dg2-set2: NOTRUN -> [SKIP][4]
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141063v1/shard-dg2-433/igt@kms_rotation_crc@primary-y-tiled-reflect-x-90.html
>
prev parent reply other threads:[~2024-11-09 14:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 19:47 [PATCH 0/2] Prefer GT oriented logs/asserts in submit code Michal Wajdeczko
2024-11-07 19:47 ` [PATCH 1/2] drm/xe/guc: Prefer GT oriented asserts " Michal Wajdeczko
2024-11-07 22:15 ` Matthew Brost
2024-11-07 19:47 ` [PATCH 2/2] drm/xe/guc: Prefer GT oriented logs " Michal Wajdeczko
2024-11-07 22:19 ` Matthew Brost
2024-11-07 19:53 ` ✓ CI.Patch_applied: success for Prefer GT oriented logs/asserts " Patchwork
2024-11-07 19:54 ` ✓ CI.checkpatch: " Patchwork
2024-11-07 19:55 ` ✓ CI.KUnit: " Patchwork
2024-11-07 20:06 ` ✓ CI.Build: " Patchwork
2024-11-07 20:09 ` ✓ CI.Hooks: " Patchwork
2024-11-07 20:10 ` ✓ CI.checksparse: " Patchwork
2024-11-07 20:34 ` ✓ CI.BAT: " Patchwork
2024-11-09 2:16 ` ✗ CI.FULL: failure " Patchwork
2024-11-09 14:14 ` Michal Wajdeczko [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=05a4c78c-22a0-4a3b-bc4e-66577637859e@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@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