All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nguyen, Brian" <brian3.nguyen@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for drm/xe: Implement print vfunc for page fault info logging (rev3)
Date: Wed, 30 Sep 2026 14:08:58 -0700	[thread overview]
Message-ID: <b1717a63-df2e-4cf4-ae7f-5239c015eef7@intel.com> (raw)
In-Reply-To: <179065853962.217537.14659824266134611479@61270ab9df2a>


On 9/28/2026 10:08 PM, Patchwork wrote:
> == Series Details ==
>
> Series: drm/xe: Implement print vfunc for page fault info logging (rev3)
> URL   : https://patchwork.freedesktop.org/series/175024/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-5837-972eeb850a4ca07aba05ccb805db28a33eab2c9a_FULL -> xe-pw-175024v3_FULL
> ====================================================
>
> Summary
> -------
>
>   **FAILURE**
>
>   Serious unknown changes coming with xe-pw-175024v3_FULL absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-175024v3_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 (3 -> 3)
> ------------------------------
>
>   No changes in participating hosts
>
> Possible new issues
> -------------------
>
>   Here are the unknown changes that may have been introduced in xe-pw-175024v3_FULL:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
>   * igt@core_hotunplug@hotreplug-with-load:
>     - shard-bmg:          [PASS][1] -> [ABORT][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-5837-972eeb850a4ca07aba05ccb805db28a33eab2c9a/shard-bmg-5/igt@core_hotunplug@hotreplug-with-load.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-175024v3/shard-bmg-7/igt@core_hotunplug@hotreplug-with-load.html
>
>   * igt@xe_configfs@ctx-restore-post-bb:
>     - shard-bmg:          NOTRUN -> [ABORT][3]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-175024v3/shard-bmg-9/igt@xe_configfs@ctx-restore-post-bb.html
>

Issues are unrelated to this patch, as it only modifies logging output.

So, this patch should be good to merge, thanks.


Brian


> Build changes
> -------------
>
>   * IGT: IGT_9113 -> IGT_9114
>   * Linux: xe-5837-972eeb850a4ca07aba05ccb805db28a33eab2c9a -> xe-pw-175024v3
>
>   IGT_9113: 691cc6fd50d5a3f6f2b5805c9698af1df28f6830 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>   IGT_9114: 916c79cfb7675ca01607dcd821f8c49d4f633a6f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>   xe-5837-972eeb850a4ca07aba05ccb805db28a33eab2c9a: 972eeb850a4ca07aba05ccb805db28a33eab2c9a
>   xe-pw-175024v3: 175024v3
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-175024v3/index.html

      reply	other threads:[~2026-09-30 21:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 22:22 [PATCH v3] drm/xe: Implement print vfunc for page fault info logging Brian Nguyen
2026-09-28 22:30 ` ✓ CI.KUnit: success for drm/xe: Implement print vfunc for page fault info logging (rev3) Patchwork
2026-09-28 23:34 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-29  5:08 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-09-30 21:08   ` Nguyen, Brian [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=b1717a63-df2e-4cf4-ae7f-5239c015eef7@intel.com \
    --to=brian3.nguyen@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 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.