Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Auld" <matthew.auld@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ Xe.CI.BAT: failure for drm/xe/dma_buf: stop relying on placement in unmap (rev2)
Date: Thu, 10 Apr 2025 18:37:50 -0000	[thread overview]
Message-ID: <174431027004.367.13267155585568614263@32c37dd7f93d> (raw)
In-Reply-To: <20250410162716.159403-2-matthew.auld@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1919 bytes --]

== Series Details ==

Series: drm/xe/dma_buf: stop relying on placement in unmap (rev2)
URL   : https://patchwork.freedesktop.org/series/147218/
State : failure

== Summary ==

CI Bug Log - changes from xe-2931-457049ad31ee5b64dd86230518144d366c32bc04_BAT -> xe-pw-147218v2_BAT
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with xe-pw-147218v2_BAT absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in xe-pw-147218v2_BAT, 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 (9 -> 8)
------------------------------

  Missing    (1): bat-adlp-vm 

Possible new issues
-------------------

  Here are the unknown changes that may have been introduced in xe-pw-147218v2_BAT:

### IGT changes ###

#### Possible regressions ####

  * igt@intel_sysfs_debugfs@xe-debugfs-read-all-entries:
    - bat-adlp-vf:        NOTRUN -> [ABORT][1]
   [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-147218v2/bat-adlp-vf/igt@intel_sysfs_debugfs@xe-debugfs-read-all-entries.html
    - bat-lnl-2:          NOTRUN -> [ABORT][2]
   [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-147218v2/bat-lnl-2/igt@intel_sysfs_debugfs@xe-debugfs-read-all-entries.html

  


Build changes
-------------

  * IGT: IGT_8313 -> IGT_8314
  * Linux: xe-2931-457049ad31ee5b64dd86230518144d366c32bc04 -> xe-pw-147218v2

  IGT_8313: 8313
  IGT_8314: 337db6fa542d9c89500701f283a3cbeee4a61b50 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
  xe-2931-457049ad31ee5b64dd86230518144d366c32bc04: 457049ad31ee5b64dd86230518144d366c32bc04
  xe-pw-147218v2: 147218v2

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-147218v2/index.html

[-- Attachment #2: Type: text/html, Size: 2524 bytes --]

  parent reply	other threads:[~2025-04-10 18:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10 16:27 [PATCH] drm/xe/dma_buf: stop relying on placement in unmap Matthew Auld
2025-04-10 18:02 ` ✓ CI.Patch_applied: success for drm/xe/dma_buf: stop relying on placement in unmap (rev2) Patchwork
2025-04-10 18:02 ` ✓ CI.checkpatch: " Patchwork
2025-04-10 18:03 ` ✓ CI.KUnit: " Patchwork
2025-04-10 18:12 ` ✓ CI.Build: " Patchwork
2025-04-10 18:14 ` ✓ CI.Hooks: " Patchwork
2025-04-10 18:15 ` ✓ CI.checksparse: " Patchwork
2025-04-10 18:37 ` Patchwork [this message]
2025-04-10 23:38 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-17  5:01 ` [PATCH] drm/xe/dma_buf: stop relying on placement in unmap Matthew Brost

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=174431027004.367.13267155585568614263@32c37dd7f93d \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox