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.Full: failure for igt_facts for fact tracking (rev2)
Date: Thu, 19 Dec 2024 05:56:39 +0100	[thread overview]
Message-ID: <35c82d13-1c04-46ae-b674-bd287bf5b958@linux.intel.com> (raw)
In-Reply-To: <472d9a63-8ab9-435c-9a7b-48865ca617d0@linux.intel.com>

Dear I915,

Did you receive my previous email?

Thank you.

On 18.12.2024 06:18, Peter Senna Tschudin wrote:
> Dear I915,
> 
> 
> On 17.12.2024 15:25, 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 CI_DRM_15854_full -> IGTPW_12325_full
>> ====================================================
>>
>> Summary
>> -------
>>
>>   **FAILURE**
>>
>>   Serious unknown changes coming with IGTPW_12325_full absolutely need to be
>>   verified manually.
>>   
>>   If you think the reported changes have nothing to do with the changes
>>   introduced in IGTPW_12325_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.
>>
>>   External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12325/index.html
>>
>> Participating hosts (11 -> 12)
>> ------------------------------
>>
>>   Additional (1): shard-dg2-set2 
>>
>> Possible new issues
>> -------------------
>>
>>   Here are the unknown changes that may have been introduced in IGTPW_12325_full:
>>
>> ### IGT changes ###
>>
>> #### Possible regressions ####
>>
>>   * igt@gem_eio@in-flight-contexts-10ms:
>>     - shard-snb:          NOTRUN -> [FAIL][1]
>>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12325/shard-snb7/igt@gem_eio@in-flight-contexts-10ms.html
>>
>>   * igt@gem_eio@in-flight-suspend:
>>     - shard-glk:          NOTRUN -> [INCOMPLETE][2]
>>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12325/shard-glk7/igt@gem_eio@in-flight-suspend.html
>>
>>   * igt@kms_color@invalid-degamma-lut-sizes:
>>     - shard-snb:          NOTRUN -> [INCOMPLETE][3]
>>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12325/shard-snb1/igt@kms_color@invalid-degamma-lut-sizes.html
>>
>>   * igt@perf_pmu@busy-accuracy-98@vcs1:
>>     - shard-mtlp:         [PASS][4] -> [FAIL][5]
>>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15854/shard-mtlp-8/igt@perf_pmu@busy-accuracy-98@vcs1.html
>>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12325/shard-mtlp-5/igt@perf_pmu@busy-accuracy-98@vcs1.html
>>
>>   * igt@perf_pmu@busy-accuracy-98@vecs1:
>>     - shard-dg2:          [PASS][6] -> [FAIL][7] +1 other test fail
>>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15854/shard-dg2-7/igt@perf_pmu@busy-accuracy-98@vecs1.html
>>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12325/shard-dg2-10/igt@perf_pmu@busy-accuracy-98@vecs1.html
> 
> These are not related to my change.
> 
>>
>>   
>> #### Warnings ####
>>
>>   * igt@gem_tiled_swapping@non-threaded:
>>     - shard-tglu:         [FAIL][8] ([i915#12941]) -> [FAIL][9]
>>    [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15854/shard-tglu-3/igt@gem_tiled_swapping@non-threaded.html
>>    [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12325/shard-tglu-6/igt@gem_tiled_swapping@non-threaded.html
>>
>>   * igt@kms_async_flips@crc-atomic:
>>     - shard-glk:          [INCOMPLETE][10] ([i915#13287]) -> [INCOMPLETE][11] +1 other test incomplete
>>    [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15854/shard-glk1/igt@kms_async_flips@crc-atomic.html
>>    [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12325/shard-glk6/igt@kms_async_flips@crc-atomic.html
> 
> These are not related to my change.
> 
> Please fix and re-run.
> 
> Thank you,
> 
> Peter
> 
> [...]


  reply	other threads:[~2024-12-19  4:56 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
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 [this message]
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=35c82d13-1c04-46ae-b674-bd287bf5b958@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