From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: <igt-dev@lists.freedesktop.org>,
Lakshminarayana Vudum <lakshminarayana.vudum@intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_cursor_legacy: Avoid usage of same pipe on multiple outputs
Date: Mon, 11 Jul 2022 21:16:29 +0530 [thread overview]
Message-ID: <bcff0bdd-1b8a-3720-52dd-4ba3bf5d144f@intel.com> (raw)
In-Reply-To: <165755318862.5767.3371105841083001752@emeril.freedesktop.org>
Hi Lakshmi,
On Mon-11-07-2022 08:56 pm, Patchwork wrote:
> *Patch Details*
> *Series:* tests/kms_cursor_legacy: Avoid usage of same pipe on multiple
> outputs
> *URL:* https://patchwork.freedesktop.org/series/106201/
> <https://patchwork.freedesktop.org/series/106201/>
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7498/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7498/index.html>
>
>
> CI Bug Log - changes from CI_DRM_11870 -> IGTPW_7498
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with IGTPW_7498 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_7498, please notify your bug team 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_7498/index.html
>
>
> Participating hosts (33 -> 36)
>
> Additional (6): fi-kbl-soraka bat-dg1-5 bat-dg2-9 bat-adlp-6 fi-hsw-4770
> bat-rpls-2
> Missing (3): fi-ctg-p8600 fi-rkl-11600 fi-hsw-4200u
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in IGTPW_7498:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@runner@aborted:
> o fi-kbl-8809g: NOTRUN -> FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7498/fi-kbl-8809g/igt@runner@aborted.html>
This failure is not related my patch, can you please help to re-report?
- Bhanu
next prev parent reply other threads:[~2022-07-11 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 14:19 [igt-dev] [i-g-t] tests/kms_cursor_legacy: Avoid usage of same pipe on multiple outputs Bhanuprakash Modem
2022-07-11 15:26 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2022-07-11 15:46 ` Modem, Bhanuprakash [this message]
2022-07-11 15:55 ` Vudum, Lakshminarayana
2022-07-11 15:54 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2022-07-11 20:03 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2022-07-13 7:44 ` [igt-dev] [i-g-t] " Sharma, Swati2
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=bcff0bdd-1b8a-3720-52dd-4ba3bf5d144f@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lakshminarayana.vudum@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