Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ CI.BAT: failure for drm/xe: Take ref to VM in delayed snapshot
Date: Fri, 26 Jul 2024 12:36:42 +0000	[thread overview]
Message-ID: <ZqOYWvU3HnXX8c/B@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <172195507613.384426.14292273587651231613@2413ebb6fbb6>

On Fri, Jul 26, 2024 at 12:51:16AM +0000, Patchwork wrote:
>    Patch Details
> 
>    Series:  drm/xe: Take ref to VM in delayed snapshot
>    URL:     [1]https://patchwork.freedesktop.org/series/136541/
>    State:   failure
>    Details:
>    [2]https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136541v1/index.html
> 
>  CI Bug Log - changes from xe-1668-1c38b092d18ce973d9ec31a4ab097fbc344ab8f2_BAT
>                              -> xe-pw-136541v1_BAT
> 
> Summary
> 
>    FAILURE
> 
>    Serious unknown changes coming with xe-pw-136541v1_BAT absolutely need
>    to be
>    verified manually.
> 
>    If you think the reported changes have nothing to do with the changes
>    introduced in xe-pw-136541v1_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 (7 -> 7)
> 
>    No changes in participating hosts
> 
> Possible new issues
> 
>    Here are the unknown changes that may have been introduced in
>    xe-pw-136541v1_BAT:
> 
>   IGT changes
> 
>     Possible regressions
> 
>      * igt@xe_debugfs@gt:
>           + bat-lnl-1: [3]PASS -> [4]ABORT

CI doesn't like this as is, this is needed but need to rethink. Let me look into this.

Matt

> 
>     Suppressed
> 
>    The following results come from untrusted machines, tests, or statuses.
>    They do not affect the overall result.
>      * igt@xe_debugfs@gt:
>           + {bat-lnl-2}: [5]PASS -> [6]ABORT
> 
> Known issues
> 
>    Here are the changes found in xe-pw-136541v1_BAT that come from known
>    issues:
> 
>   IGT changes
> 
>     Issues hit
> 
>      * igt@kms_frontbuffer_tracking@basic:
>           + bat-adlp-7: [7]PASS -> [8]DMESG-WARN ([9]Intel XE#324)
> 
>     Possible fixes
> 
>      * igt@xe_evict@evict-small-external:
>           + {bat-bmg-1}: [10]DMESG-WARN -> [11]PASS
> 
>    {name}: This element is suppressed. This means it is ignored when
>    computing
>    the status of the difference (SUCCESS, WARNING, or FAILURE).
> 
> Build changes
> 
>      * Linux: xe-1668-1c38b092d18ce973d9ec31a4ab097fbc344ab8f2 ->
>        xe-pw-136541v1
> 
>    IGT_7937: eba69333dfe8c295d053997367e395d7bde2b4b4 @
>    https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>    xe-1668-1c38b092d18ce973d9ec31a4ab097fbc344ab8f2:
>    1c38b092d18ce973d9ec31a4ab097fbc344ab8f2
>    xe-pw-136541v1: 136541v1
> 
> References
> 
>    1. https://patchwork.freedesktop.org/series/136541/
>    2. https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136541v1/index.html
>    3. https://intel-gfx-ci.01.org/tree/intel-xe/xe-1668-1c38b092d18ce973d9ec31a4ab097fbc344ab8f2/bat-lnl-1/igt@xe_debugfs@gt.html
>    4. https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136541v1/bat-lnl-1/igt@xe_debugfs@gt.html
>    5. https://intel-gfx-ci.01.org/tree/intel-xe/xe-1668-1c38b092d18ce973d9ec31a4ab097fbc344ab8f2/bat-lnl-2/igt@xe_debugfs@gt.html
>    6. https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136541v1/bat-lnl-2/igt@xe_debugfs@gt.html
>    7. https://intel-gfx-ci.01.org/tree/intel-xe/xe-1668-1c38b092d18ce973d9ec31a4ab097fbc344ab8f2/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html
>    8. https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136541v1/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html
>    9. https://gitlab.freedesktop.org/drm/xe/kernel/issues/324
>   10. https://intel-gfx-ci.01.org/tree/intel-xe/xe-1668-1c38b092d18ce973d9ec31a4ab097fbc344ab8f2/bat-bmg-1/igt@xe_evict@evict-small-external.html
>   11. https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136541v1/bat-bmg-1/igt@xe_evict@evict-small-external.html

  reply	other threads:[~2024-07-26 12:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 23:24 [PATCH] drm/xe: Take ref to VM in delayed snapshot Matthew Brost
2024-07-26  0:09 ` ✓ CI.Patch_applied: success for " Patchwork
2024-07-26  0:10 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-26  0:11 ` ✓ CI.KUnit: success " Patchwork
2024-07-26  0:23 ` ✓ CI.Build: " Patchwork
2024-07-26  0:26 ` ✓ CI.Hooks: " Patchwork
2024-07-26  0:28 ` ✓ CI.checksparse: " Patchwork
2024-07-26  0:51 ` ✗ CI.BAT: failure " Patchwork
2024-07-26 12:36   ` Matthew Brost [this message]
2024-07-26  8:17 ` [PATCH] " Upadhyay, Tejas
2024-07-26 12:13   ` Matthew Brost
2024-07-26  9:27 ` ✗ CI.FULL: failure for " Patchwork

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=ZqOYWvU3HnXX8c/B@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@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