From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe: Prefer USEC_PER_SEC over MICRO
Date: Wed, 12 Mar 2025 11:23:03 +0100 [thread overview]
Message-ID: <9ab77838-d511-42ea-a431-bc8c62ecf8f9@intel.com> (raw)
In-Reply-To: <174177017993.23959.14332523214559178350@18a75f3d1eae>
On 12.03.2025 10:02, Patchwork wrote:
> == Series Details ==
>
> Series: drm/xe: Prefer USEC_PER_SEC over MICRO
> URL : https://patchwork.freedesktop.org/series/146141/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-2795-f8df428b3850ed87a1e2f3b12b6025328d8a6373_full -> xe-pw-146141v1_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-146141v1_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-146141v1_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-146141v1_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_async_flips@async-flip-with-page-flip-events-atomic:
> - shard-dg2-set2: [PASS][1] -> [INCOMPLETE][2] +1 other test incomplete
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2795-f8df428b3850ed87a1e2f3b12b6025328d8a6373/shard-dg2-433/igt@kms_async_flips@async-flip-with-page-flip-events-atomic.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146141v1/shard-dg2-435/igt@kms_async_flips@async-flip-with-page-flip-events-atomic.html
>
looks more like a CI glitch during collecting the logs
can't be related to this patch
prev parent reply other threads:[~2025-03-12 10:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 14:01 [PATCH] drm/xe: Prefer USEC_PER_SEC over MICRO Michal Wajdeczko
2025-03-11 14:34 ` Ghimiray, Himal Prasad
2025-03-11 16:12 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-11 16:13 ` ✓ CI.checkpatch: " Patchwork
2025-03-11 16:14 ` ✓ CI.KUnit: " Patchwork
2025-03-11 16:31 ` ✓ CI.Build: " Patchwork
2025-03-11 16:33 ` ✓ CI.Hooks: " Patchwork
2025-03-11 16:34 ` ✓ CI.checksparse: " Patchwork
2025-03-11 16:56 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-12 9:02 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-12 10:23 ` 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=9ab77838-d511-42ea-a431-bc8c62ecf8f9@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