From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: <igt-dev@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.IGT: failure for i915/drm_fdinfo: Quiesce GPU prior to running some tests
Date: Mon, 14 Oct 2024 14:47:09 -0700 [thread overview]
Message-ID: <Zw2RXdyJH2av8ONC@orsosgc001> (raw)
In-Reply-To: <172801766374.1172277.11953781463943816824@2413ebb6fbb6>
On Fri, Oct 04, 2024 at 04:54:23AM +0000, Patchwork wrote:
> Patch Details
>
> Series: i915/drm_fdinfo: Quiesce GPU prior to running some tests
> URL: [1]https://patchwork.freedesktop.org/series/139451/
> State: failure
> Details: [2]https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_11859/index.html
>
> CI Bug Log - changes from IGT_8050_full -> IGTPW_11859_full
>
>Summary
>
> FAILURE
>
> Serious unknown changes coming with IGTPW_11859_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_11859_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_11859/index.html
>
>Participating hosts (8 -> 8)
>
> No changes in participating hosts
>
>Possible new issues
>
> Here are the unknown changes that may have been introduced in
> IGTPW_11859_full:
>
> IGT changes
>
> Possible regressions
>
> * igt@gem_exec_balancer@nop:
>
> * shard-mtlp: [3]PASS -> [4]DMESG-WARN
>
> * igt@kms_async_flips@alternate-sync-async-flip:
>
> * shard-dg1: [5]PASS -> [6]FAIL +1 other test fail
>
> * igt@kms_cursor_crc@cursor-offscreen-512x512:
>
> * shard-mtlp: NOTRUN -> [7]SKIP
> * shard-dg1: NOTRUN -> [8]SKIP
>
> * igt@kms_cursor_crc@cursor-sliding-512x512:
>
> * shard-tglu: NOTRUN -> [9]SKIP +1 other test skip
>
> * igt@kms_joiner@basic-force-big-joiner:
>
> * shard-dg2: NOTRUN -> [10]SKIP
>
> Warnings
>
> * igt@kms_cursor_crc@cursor-offscreen-512x512:
>
> * shard-dg2: [11]SKIP ([i915#9197]) -> [12]SKIP
The failures here are unrelated since the patch only touches drmfdinfo
tests.
Umesh
>
>New tests
>
prev parent reply other threads:[~2024-10-14 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 21:20 [PATCH i-g-t] i915/drm_fdinfo: Quiesce GPU prior to running some tests Umesh Nerlige Ramappa
2024-10-02 22:32 ` ✓ CI.xeBAT: success for " Patchwork
2024-10-02 22:39 ` ✓ Fi.CI.BAT: " Patchwork
2024-10-02 23:19 ` [PATCH i-g-t] " Dixit, Ashutosh
2024-10-03 22:04 ` Umesh Nerlige Ramappa
2024-10-14 14:47 ` Kamil Konieczny
2024-10-02 23:56 ` ✗ CI.xeFULL: failure for " Patchwork
2024-10-14 21:48 ` Umesh Nerlige Ramappa
2024-10-04 4:54 ` ✗ Fi.CI.IGT: " Patchwork
2024-10-14 21:47 ` Umesh Nerlige Ramappa [this message]
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=Zw2RXdyJH2av8ONC@orsosgc001 \
--to=umesh.nerlige.ramappa@intel.com \
--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