Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
To: I915-ci-infra@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ i915.CI.Full: failure for drm/i915/selftests: Wait longer for request to start
Date: Tue, 01 Sep 2026 12:43:31 +0200	[thread overview]
Message-ID: <2bfacf4518d0a914ef984dbf7dc2c6f6114100b3.camel@linux.intel.com> (raw)
In-Reply-To: <178820767489.104222.16189714489178134155@61270ab9df2a>

[-- Attachment #1: Type: text/plain, Size: 2151 bytes --]

Hi I915-ci-infra@lists.freedesktop.org,

On Mon, 2026-08-31 at 20:21 +0000, Patchwork wrote:
> Patch Details
> 
> Series:drm/i915/selftests: Wait longer for request to start
> 
> URL:https://patchwork.freedesktop.org/series/173048/
> 
> State:failure
> Details:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_173048v1/index.html
> CI Bug Log - changes from CI_DRM_19062_full -> Patchwork_173048v1_fullSummaryFAILURE
> Serious unknown changes coming with Patchwork_173048v1_full absolutely
> need to be
> verified manually.
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_173048v1_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 (10 -> 10)No changes in participating hosts
> Possible new issuesHere are the unknown changes that may have been introduced in
> Patchwork_173048v1_full:
> IGT changesPossible regressions * 
>    igt@gem_linear_blits@normal:shard-dg1: PASS [5] -> FAIL [4]
>  * 
>    igt@i915_pm_rpm@sysfs-read:shard-dg2: PASS [3] -> SKIP [2]
>  * 
>    igt@runner@aborted:
>     - shard-mtlp:         NOTRUN -> (FAIL [1], FAIL [1])

The patch under this pre-merge testing only touches one specific selftest,
then the above failures are not related.  Please update CBL filters and re-
report.

Thanks,
Janusz

> Known issuesHere are the changes found in Patchwork_173048v1_full that come from
> known issues:
...


[1] FAIL
    https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_173048v1/shard-mtlp-6/igt@runner@aborted.html
[2] SKIP
    https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_173048v1/shard-dg2-1/igt@i915_pm_rpm@sysfs-read.html
[3] PASS
    https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_19062/shard-dg2-5/igt@i915_pm_rpm@sysfs-read.html
[4] FAIL
    https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_173048v1/shard-dg1-14/igt@gem_linear_blits@normal.html
[5] PASS
    https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_19062/shard-dg1-17/igt@gem_linear_blits@normal.html

[-- Attachment #2: Type: text/html, Size: 3654 bytes --]

  reply	other threads:[~2026-09-01 10:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  9:33 [PATCH] drm/i915/selftests: Wait longer for request to start Janusz Krzysztofik
2026-08-31 15:23 ` ✓ i915.CI.BAT: success for " Patchwork
2026-08-31 20:21 ` ✗ i915.CI.Full: failure " Patchwork
2026-09-01 10:43   ` Janusz Krzysztofik [this message]
2026-09-01 14:24     ` Ravali, JupallyX
2026-09-01  6:19 ` [PATCH] " Krzysztof Karas
2026-09-01  8:07   ` Janusz Krzysztofik
2026-09-01 12:57 ` ✓ i915.CI.Full: success for " Patchwork
2026-09-02  9:54 ` [PATCH] " Krzysztof Niemiec

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=2bfacf4518d0a914ef984dbf7dc2c6f6114100b3.camel@linux.intel.com \
    --to=janusz.krzysztofik@linux.intel.com \
    --cc=I915-ci-infra@lists.freedesktop.org \
    --cc=intel-gfx@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