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: ✗ i915.CI.BAT: failure for igt_facts for fact tracking (rev2)
Date: Tue, 17 Dec 2024 06:12:48 +0100	[thread overview]
Message-ID: <d48d2b4a-c16d-4cbe-b5ec-7d8cc03e167d@linux.intel.com> (raw)
In-Reply-To: <173438521433.3440302.591192445303267909@b555e5b46a47>

Dear I915,

On 16.12.2024 22:40, Patchwork wrote:
> == Series Details ==
> 
> Series: igt_facts for fact tracking (rev2)
> URL   : https://patchwork.freedesktop.org/series/142628/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from IGT_8157 -> IGTPW_12325
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_12325 absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_12325, 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.
> 
>   External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12325/index.html
> 
> Participating hosts (45 -> 44)
> ------------------------------
> 
>   Missing    (1): fi-snb-2520m 
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_12325:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@i915_pm_rpm@module-reload:
>     - bat-arlh-3:         [PASS][1] -> [INCOMPLETE][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8157/bat-arlh-3/igt@i915_pm_rpm@module-reload.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12325/bat-arlh-3/igt@i915_pm_rpm@module-reload.html

Not related to change. Please fix and re-run.

Thank you!

[...]

  reply	other threads:[~2024-12-17  5:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 15:14 [PATCH i-g-t v14 resend 0/3] igt_facts for fact tracking Peter Senna Tschudin
2024-12-16 15:14 ` [PATCH i-g-t v14 resend 1/3] lib/igt_facts: Library and unit testing " Peter Senna Tschudin
2024-12-19 12:40   ` Kamil Konieczny
2025-01-21  8:16     ` Peter Senna Tschudin
2025-01-21 11:52       ` Kamil Konieczny
2024-12-20  8:50   ` Kamil Konieczny
2024-12-16 15:14 ` [PATCH i-g-t v14 resend 2/3] tools/lsfacts: Add tool for listing facts Peter Senna Tschudin
2024-12-16 15:14 ` [PATCH i-g-t v14 resend 3/3] runner/executor: Integrate igt_facts functionality Peter Senna Tschudin
2024-12-16 21:40 ` ✗ i915.CI.BAT: failure for igt_facts for fact tracking (rev2) Patchwork
2024-12-17  5:12   ` Peter Senna Tschudin [this message]
2024-12-17 13:58     ` Ravali, JupallyX
2024-12-17  0:00 ` ✓ Xe.CI.BAT: success " Patchwork
2024-12-17  4:17 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-17  5:14   ` Peter Senna Tschudin
2024-12-17  9:33 ` ✓ i915.CI.BAT: success " Patchwork
2024-12-17 14:25 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-18  5:18   ` Peter Senna Tschudin
2024-12-19  4:56     ` Peter Senna Tschudin
2024-12-19  7:28     ` Ravali, JupallyX
2024-12-19  7:18 ` ✓ 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=d48d2b4a-c16d-4cbe-b5ec-7d8cc03e167d@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