From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Piotr Piórkowski" <piotr.piorkowski@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for Cleaning up code related to VRAM regions and its initialization - part 1 (rev3)
Date: Mon, 10 Feb 2025 13:10:49 +0100 [thread overview]
Message-ID: <0cd36529-ffe0-45ca-a22d-463de827aaa3@intel.com> (raw)
In-Reply-To: <20250210113151.tc5pryyky66kfbal@intel.com>
On 10.02.2025 12:31, Piotr Piórkowski wrote:
> Patchwork <patchwork@emeril.freedesktop.org> wrote on pon [2025-lut-10 11:15:32 +0000]:
>> == Series Details ==
>>
>> Series: Cleaning up code related to VRAM regions and its initialization - part 1 (rev3)
>> URL : https://patchwork.freedesktop.org/series/144172/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from xe-2625-24a5696cb262c7829956cc708c7fc715fefc92fe_full -> xe-pw-144172v3_full
>> ====================================================
>>
>> Summary
>> -------
>>
>> **FAILURE**
>>
>> Serious unknown changes coming with xe-pw-144172v3_full absolutely need to be
>> verified manually.
>>
>> If you think the reported changes have nothing to do with the changes
>> introduced in xe-pw-144172v3_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-144172v3_full:
>>
>> ### IGT changes ###
>>
>> #### Possible regressions ####
>>
>> * igt@xe_vm@munmap-style-unbind-one-partial:
>> - shard-dg2-set2: [PASS][1] -> [INCOMPLETE][2]
>> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2625-24a5696cb262c7829956cc708c7fc715fefc92fe/shard-dg2-464/igt@xe_vm@munmap-style-unbind-one-partial.html
>> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-144172v3/shard-dg2-466/igt@xe_vm@munmap-style-unbind-one-partial.html
>
> No logs to deduce something, but for the v2 version which in practice had the same code
> (only change in doc) this problem did not occur so I assume it is a random thing.
from dmesg20
<7>[ 253.361476] [IGT] xe_vm: executing
<7>[ 253.376891] [IGT] xe_vm: starting subtest
munmap-style-unbind-one-partial
<7>[ 253.379893] [IGT] xe_vm: finished subtest
munmap-style-unbind-one-partial, SUCCESS
<7>[ 253.391373] [IGT] xe_vm: exiting, ret=0
so pushed to drm-xe-next
prev parent reply other threads:[~2025-02-10 12:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 8:15 [PATCH v3 0/2] Cleaning up code related to VRAM regions and its initialization - part 1 Piórkowski, Piotr
2025-02-10 8:15 ` [PATCH v3 1/2] drm/xe: Rename struct xe_mem_region to struct xe_vram_region Piórkowski, Piotr
2025-02-10 8:15 ` [PATCH v3 2/2] drm/xe: Move VRAM manager " Piórkowski, Piotr
2025-02-10 8:31 ` ✓ CI.Patch_applied: success for Cleaning up code related to VRAM regions and its initialization - part 1 (rev3) Patchwork
2025-02-10 8:31 ` ✓ CI.checkpatch: " Patchwork
2025-02-10 8:32 ` ✓ CI.KUnit: " Patchwork
2025-02-10 8:49 ` ✓ CI.Build: " Patchwork
2025-02-10 8:51 ` ✓ CI.Hooks: " Patchwork
2025-02-10 8:52 ` ✓ CI.checksparse: " Patchwork
2025-02-10 9:11 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-10 11:15 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-10 11:31 ` Piotr Piórkowski
2025-02-10 12:10 ` 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=0cd36529-ffe0-45ca-a22d-463de827aaa3@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=piotr.piorkowski@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.