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 lib/igt_kmemleak: library to interact with kmemleak (rev2)
Date: Mon, 13 Jan 2025 09:00:26 +0100	[thread overview]
Message-ID: <70130f72-1bb6-492b-8760-e5a523109e4f@linux.intel.com> (raw)
In-Reply-To: <173667139526.2829460.13324038630832694591@b555e5b46a47>

Dear I915,


On 12.01.2025 09:43, Patchwork wrote:
> == Series Details ==
> 
> Series: lib/igt_kmemleak: library to interact with kmemleak (rev2)
> URL   : https://patchwork.freedesktop.org/series/142673/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from XEIGT_8184_full -> XEIGTPW_12421_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with XEIGTPW_12421_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in XEIGTPW_12421_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_12421_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@xe_pm_residency@cpg-basic:
>     - shard-dg2-set2:     [PASS][1] -> [ABORT][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8184/shard-dg2-433/igt@xe_pm_residency@cpg-basic.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12421/shard-dg2-432/igt@xe_pm_residency@cpg-basic.html
> 
>   
> #### Warnings ####
> 
>   * igt@xe_evict@evict-mixed-threads-large:
>     - shard-bmg:          [INCOMPLETE][3] ([Intel XE#1473]) -> [DMESG-FAIL][4]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8184/shard-bmg-2/igt@xe_evict@evict-mixed-threads-large.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12421/shard-bmg-1/igt@xe_evict@evict-mixed-threads-large.html
> 
>   * igt@xe_mmap@pci-membarrier-bad-object:
>     - shard-bmg:          [SKIP][5] ([Intel XE#1130]) -> [SKIP][6]
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8184/shard-bmg-4/igt@xe_mmap@pci-membarrier-bad-object.html
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12421/shard-bmg-8/igt@xe_mmap@pci-membarrier-bad-object.html

These warnings and regression are unrelated. Please fix and re-run.

Thank you!

[...]

  reply	other threads:[~2025-01-13  8:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 18:10 [PATCH i-g-t] lib/igt_kmemleak: library to interact with kmemleak Peter Senna Tschudin
2025-01-09 19:13 ` Cavitt, Jonathan
2025-01-09 20:37 ` ✗ i915.CI.BAT: failure for lib/igt_kmemleak: library to interact with kmemleak (rev2) Patchwork
2025-01-09 21:08   ` Peter Senna Tschudin
2025-01-10  9:39     ` Ravali, JupallyX
2025-01-09 21:18 ` ✓ Xe.CI.BAT: success " Patchwork
2025-01-10  9:34 ` ✓ i915.CI.BAT: " Patchwork
2025-01-12  8:43 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-13  8:00   ` Peter Senna Tschudin [this message]
2025-01-13 10:04     ` Ravali, JupallyX
2025-01-13 12:25 ` [PATCH i-g-t] lib/igt_kmemleak: library to interact with kmemleak Kamil Konieczny
2025-01-13 12:54 ` ✗ i915.CI.Full: failure for lib/igt_kmemleak: library to interact with kmemleak (rev2) Patchwork
2025-01-14  8:16   ` Peter Senna Tschudin
2025-01-16  4:51     ` Ravali, JupallyX
2025-01-15 19:41 ` ✓ i915.CI.Full: success " 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=70130f72-1bb6-492b-8760-e5a523109e4f@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