From: "Anirban, Sk" <sk.anirban@intel.com>
To: <igt-dev@lists.freedesktop.org>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Subject: Re: ✗ Xe.CI.FULL: failure for tests/intel: Avoid stale errno
Date: Mon, 7 Sep 2026 16:00:41 +0530 [thread overview]
Message-ID: <5e565343-8871-4006-b0b8-a490f2912b29@intel.com> (raw)
In-Reply-To: <178855720059.125641.3087920712210357187@61270ab9df2a>
[-- Attachment #1: Type: text/plain, Size: 2543 bytes --]
Hi
These failures are not related to my changes, please re-report.
Thanks,
Anirban
On 05-09-2026 02:56 am, Patchwork wrote:
> Project List - Patchwork *Patch Details*
> *Series:* tests/intel: Avoid stale errno
> *URL:* https://patchwork.freedesktop.org/series/173370/
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15789/index.html
>
>
> CI Bug Log - changes from XEIGT_9084_FULL -> XEIGTPW_15789_FULL
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with XEIGTPW_15789_FULL absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in XEIGTPW_15789_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 (2 -> 2)
>
> No changes in participating hosts
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> XEIGTPW_15789_FULL:
>
>
> IGT changes
>
>
> Possible regressions
>
> *
>
> igt@kms_cursor_legacy@cursora-vs-flipb-atomic-transitions-varying-size:
>
> o shard-bmg: PASS
> <https://intel-gfx-ci.01.org/tree/intel-xe/IGT_9084/shard-bmg-7/igt@kms_cursor_legacy@cursora-vs-flipb-atomic-transitions-varying-size.html>
> -> DMESG-WARN
> <https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15789/shard-bmg-1/igt@kms_cursor_legacy@cursora-vs-flipb-atomic-transitions-varying-size.html>
> *
>
> igt@kms_fb_coherency@memset-crc:
>
> o shard-lnl: PASS
> <https://intel-gfx-ci.01.org/tree/intel-xe/IGT_9084/shard-lnl-3/igt@kms_fb_coherency@memset-crc.html>
> -> SKIP
> <https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15789/shard-lnl-6/igt@kms_fb_coherency@memset-crc.html>
> *
>
> igt@xe_compute_preempt@compute-preempt-many-vram:
>
> o shard-bmg: PASS
> <https://intel-gfx-ci.01.org/tree/intel-xe/IGT_9084/shard-bmg-3/igt@xe_compute_preempt@compute-preempt-many-vram.html>
> -> ABORT
> <https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15789/shard-bmg-3/igt@xe_compute_preempt@compute-preempt-many-vram.html>
> +1 other test abort
>
>
> New tests
>
> New tests have been introduced between XEIGT_9084_FULL and
> XEIGTPW_15789_FULL:
>
>
> New IGT tests (1)
>
> * igt@kms_flip@basic-flip-vs-dpms@d-dp2:
> o Statuses : 1 pass(s)
> o Exec time: [0.75] s
>
>
> Known issues
>
[-- Attachment #2: Type: text/html, Size: 4358 bytes --]
next prev parent reply other threads:[~2026-09-07 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 10:00 [PATCH v2] tests/intel: Avoid stale errno Sk Anirban
2026-09-04 10:58 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-09-04 11:15 ` ✓ i915.CI.BAT: " Patchwork
2026-09-04 21:26 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-09-07 10:30 ` Anirban, Sk [this message]
2026-09-04 23:04 ` ✗ i915.CI.Full: " Patchwork
2026-09-07 9:42 ` [PATCH v2] " Kamil Konieczny
2026-09-07 10:33 ` Anirban, Sk
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=5e565343-8871-4006-b0b8-a490f2912b29@intel.com \
--to=sk.anirban@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
/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