From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: <igt-dev@lists.freedesktop.org>
Subject: Re: ✗ CI.xeFULL: failure for i915/drm_fdinfo: Quiesce GPU prior to running some tests
Date: Mon, 14 Oct 2024 14:48:14 -0700 [thread overview]
Message-ID: <Zw2Rng1c7myy0G3+@orsosgc001> (raw)
In-Reply-To: <172791341636.1165733.2070994288194346438@2413ebb6fbb6>
On Wed, Oct 02, 2024 at 11:56:56PM +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/intel-xe/IGTPW_11859/index.html
>
> CI Bug Log - changes from XEIGT_8050_full -> XEIGTPW_11859_full
>
>Summary
>
> FAILURE
>
> Serious unknown changes coming with XEIGTPW_11859_full absolutely need to
> be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in XEIGTPW_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.
>
>Participating hosts (4 -> 4)
>
> No changes in participating hosts
>
>Possible new issues
>
> Here are the unknown changes that may have been introduced in
> XEIGTPW_11859_full:
>
> IGT changes
>
> Possible regressions
>
> * igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc:
>
> * shard-dg2-set2: NOTRUN -> [3]INCOMPLETE +1 other test incomplete
>
> * igt@kms_color@ctm-signed:
>
> * shard-lnl: [4]PASS -> [5]DMESG-WARN +3 other tests dmesg-warn
>
> * igt@kms_joiner@invalid-modeset-ultra-joiner:
>
> * shard-dg2-set2: NOTRUN -> [6]SKIP +1 other test skip
>
> * igt@kms_pm_rpm@legacy-planes-dpms@plane-68:
>
> * shard-lnl: [7]PASS -> [8]DMESG-FAIL
>
> * igt@kms_psr@fbc-psr2-cursor-render@edp-1:
>
> * shard-lnl: [9]PASS -> [10]FAIL +8 other tests fail
>
> * igt@xe_live_ktest@xe_bo:
>
> * shard-dg2-set2: NOTRUN -> [11]TIMEOUT +1 other test timeout
>
> * igt@xe_vm@munmap-style-unbind-either-side-full:
>
> * shard-lnl: [12]PASS -> [13]INCOMPLETE +2 other tests incomplete
Unrelated to this patch since the patch only modifies a specific test.
Umesh
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_pm_backlight@brightness-with-dpms:
>
> * {shard-bmg}: NOTRUN -> [14]SKIP +2 other tests skip
>
> * igt@kms_vblank@ts-continuation-suspend:
>
> * {shard-bmg}: NOTRUN -> [15]INCOMPLETE +3 other tests incomplete
>
>Known issues
next prev parent reply other threads:[~2024-10-14 21:48 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 [this message]
2024-10-04 4:54 ` ✗ Fi.CI.IGT: " Patchwork
2024-10-14 21:47 ` Umesh Nerlige Ramappa
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=Zw2Rng1c7myy0G3+@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