Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: igt-dev@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for runner/kmemleak: Remove unnecessary lseek() calls
Date: Wed, 12 Mar 2025 11:18:54 +0100	[thread overview]
Message-ID: <16ff23f4-19d0-4f7e-b152-b04f97665cd7@linux.intel.com> (raw)
In-Reply-To: <174172982249.22025.16092550615438407434@18a75f3d1eae>

Dear I915,

On 11.03.2025 22:50, Patchwork wrote:
> == Series Details ==
> 
> Series: runner/kmemleak: Remove unnecessary lseek() calls
> URL   : https://patchwork.freedesktop.org/series/146105/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from XEIGT_8270_full -> XEIGTPW_12739_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with XEIGTPW_12739_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in XEIGTPW_12739_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 XEIGTPW_12739_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@xe_fault_injection@vm-bind-fail-vm_bind_ioctl_ops_execute:
>     - shard-bmg:          [PASS][1] -> [ABORT][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8270/shard-bmg-2/igt@xe_fault_injection@vm-bind-fail-vm_bind_ioctl_ops_execute.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12739/shard-bmg-8/igt@xe_fault_injection@vm-bind-fail-vm_bind_ioctl_ops_execute.html
>     - shard-dg2-set2:     [PASS][3] -> [ABORT][4]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8270/shard-dg2-464/igt@xe_fault_injection@vm-bind-fail-vm_bind_ioctl_ops_execute.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12739/shard-dg2-466/igt@xe_fault_injection@vm-bind-fail-vm_bind_ioctl_ops_execute.html

These are unrelated to my change.

Thank you,

Peter

  reply	other threads:[~2025-03-12 10:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10 20:02 [PATCH i-g-t] runner/kmemleak: Remove unnecessary lseek() calls Peter Senna Tschudin
2025-03-11  1:38 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-03-11  1:47 ` ✗ i915.CI.BAT: failure " Patchwork
2025-03-11  7:10   ` Peter Senna Tschudin
2025-03-11  9:51     ` Ravali, JupallyX
2025-03-11  9:50 ` ✓ i915.CI.BAT: success " Patchwork
2025-03-11 13:45 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-11 15:21   ` Peter Senna Tschudin
2025-03-12  5:54     ` Ravali, JupallyX
2025-03-11 21:50 ` ✗ Xe.CI.Full: " Patchwork
2025-03-12 10:18   ` Peter Senna Tschudin [this message]
2025-03-12  5:51 ` ✓ i915.CI.Full: success " Patchwork
2025-03-13 10:58 ` [PATCH i-g-t] " Kamil Konieczny
2025-03-28 14:02 ` Kamil Konieczny

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=16ff23f4-19d0-4f7e-b152-b04f97665cd7@linux.intel.com \
    --to=peter.senna@linux.intel.com \
    --cc=I915-ci-infra@lists.freedesktop.org \
    --cc=igt-dev@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