From: Raag Jadav <raag.jadav@intel.com>
To: igt-dev@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.BAT: failure for tests/intel/xe_pm: Introduce i2c subtests (rev2)
Date: Tue, 22 Jul 2025 14:59:57 +0300 [thread overview]
Message-ID: <aH99Papp_cjO-UYg@black.fi.intel.com> (raw)
In-Reply-To: <aH9MWwlXdS2DnrbU@black.fi.intel.com>
Cc: ci-infra
On Tue, Jul 22, 2025 at 11:31:26AM +0300, Raag Jadav wrote:
> On Sat, Jul 19, 2025 at 05:43:14PM +0000, Patchwork wrote:
> > == Series Details ==
> >
> > Series: tests/intel/xe_pm: Introduce i2c subtests (rev2)
> > URL : https://patchwork.freedesktop.org/series/146610/
> > State : failure
> >
> > == Summary ==
> >
> > CI Bug Log - changes from XEIGT_8468_BAT -> XEIGTPW_13497_BAT
> > ====================================================
> >
> > Summary
> > -------
> >
> > **SUCCESS**
>
> Is success considered a failure? Or am I missing anything here?
> Please re-report with correct results.
>
> Raag
>
> >
> > No regressions found.
> >
> >
> >
> > Participating hosts (7 -> 7)
> > ------------------------------
> >
> > No changes in participating hosts
> >
> > Known issues
> > ------------
> >
> > Here are the changes found in XEIGTPW_13497_BAT that come from known issues:
> >
> > ### IGT changes ###
> >
> > #### Possible fixes ####
> >
> > * igt@kms_flip@basic-plain-flip:
> > - bat-adlp-7: [DMESG-WARN][1] ([Intel XE#4543]) -> [PASS][2] +1 other test pass
> > [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8468/bat-adlp-7/igt@kms_flip@basic-plain-flip.html
> > [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13497/bat-adlp-7/igt@kms_flip@basic-plain-flip.html
> >
> >
> > [Intel XE#4543]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4543
> >
> >
> > Build changes
> > -------------
> >
> > * IGT: IGT_8468 -> IGTPW_13497
> > * Linux: xe-3440-338efc39ef3f17f6759817c857a95054334eae09 -> xe-3441-a8e61e615995f6bc93361cf1752563140349517a
> >
> > IGTPW_13497: 13497
> > IGT_8468: 8468
> > xe-3440-338efc39ef3f17f6759817c857a95054334eae09: 338efc39ef3f17f6759817c857a95054334eae09
> > xe-3441-a8e61e615995f6bc93361cf1752563140349517a: a8e61e615995f6bc93361cf1752563140349517a
> >
> > == Logs ==
> >
> > For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13499/index.html
next prev parent reply other threads:[~2025-07-22 12:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-19 16:31 [PATCH i-g-t v2] tests/intel/xe_pm: Introduce i2c subtests Raag Jadav
2025-07-19 17:33 ` ✗ i915.CI.BAT: failure for tests/intel/xe_pm: Introduce i2c subtests (rev2) Patchwork
2025-07-19 17:43 ` ✗ Xe.CI.BAT: " Patchwork
2025-07-22 8:31 ` Raag Jadav
2025-07-22 11:59 ` Raag Jadav [this message]
2025-07-21 10:36 ` [PATCH i-g-t v2] tests/intel/xe_pm: Introduce i2c subtests Heikki Krogerus
2025-07-22 4:05 ` Raag Jadav
2025-07-22 11:41 ` Kamil Konieczny
2025-07-22 11:57 ` Gupta, Anshuman
2025-07-22 12:12 ` Raag Jadav
2025-07-22 13:03 ` Gupta, Anshuman
2025-07-22 15:57 ` Raag Jadav
2025-07-23 9:41 ` Riana Tauro
2025-07-23 9:54 ` Gupta, Anshuman
2025-07-21 14:15 ` ✗ Xe.CI.Full: failure for tests/intel/xe_pm: Introduce i2c subtests (rev2) Patchwork
2025-07-22 13:50 ` ✓ Xe.CI.BAT: success " Patchwork
2025-07-22 16:40 ` ✗ Xe.CI.Full: failure " 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=aH99Papp_cjO-UYg@black.fi.intel.com \
--to=raag.jadav@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