public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx]  ✗ Fi.CI.IGT: failure for drm/i915/tgl/psr: Fix glitches when doing frontbuffer modifications (rev2)
Date: Fri, 23 Oct 2020 21:31:54 +0000	[thread overview]
Message-ID: <c9e11469a7cb95d7db33b67198afb5668ffe934c.camel@intel.com> (raw)
In-Reply-To: <160193449434.25152.18206159907876729195@emeril.freedesktop.org>

On Mon, 2020-10-05 at 21:48 +0000, Patchwork wrote:
> Patch Details
> Series: drm/i915/tgl/psr: Fix glitches when doing frontbuffer modifications (rev2) URL: https://patchwork.freedesktop.org/series/82351/ State:
> failure Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18625/index.html 
> CI Bug Log - changes from CI_DRM_9097_full -> Patchwork_18625_fullSummaryFAILURE
> Serious unknown changes coming with Patchwork_18625_full absolutely need to be
>  verified manually.
> If you think the reported changes have nothing to do with the changes
>  introduced in Patchwork_18625_full, please notify your bug team to allow them
>  to document this new failure mode, which will reduce false positives in CI.
> Possible new issuesHere are the unknown changes that may have been introduced in Patchwork_18625_full:
> IGT changesPossible regressions * igt@kms_cursor_legacy@all-pipes-forked-move:shard-tglb: PASS -> INCOMPLETE

The failure above it not related.

>  * igt@kms_psr2_su@frontbuffer:shard-tglb: PASS -> FAIL +1 similar issue

The failure above is expected by this patch, will follow up with the IGT change to skip this test in TGL.

Patch pushed to dinq, thanks for the review GG.

> Known issuesHere are the changes found in Patchwork_18625_full that come from known issues:
> IGT changesIssues hit * igt@gem_exec_reloc@basic-many-active@rcs0:shard-hsw: PASS -> FAIL (i915#2389)
>  * igt@i915_pm_rc6_residency@rc6-fence:shard-hsw: PASS -> WARN (i915#1519)
>  * igt@kms_cursor_crc@pipe-a-cursor-suspend:shard-kbl: PASS -> DMESG-WARN (i915#180) +5 similar issues
>  * igt@kms_cursor_edge_walk@pipe-c-128x128-right-edge:shard-glk: PASS -> DMESG-WARN (i915#1982)
>  * igt@kms_cursor_legacy@flip-vs-cursor-atomic:shard-tglb: PASS -> FAIL (i915#2346) +3 similar issues
>  * igt@kms_cursor_legacy@pipe-c-torture-bo:shard-tglb: PASS -> DMESG-WARN (i915#128)
>  * igt@kms_hdr@bpc-switch-dpms:shard-skl: PASS -> FAIL (i915#1188)
>  * igt@kms_plane@plane-panning-bottom-right-pipe-b-planes:shard-skl: PASS -> DMESG-WARN (i915#1982) +9 similar issues
>  * igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes:shard-skl: PASS -> INCOMPLETE (i915#648)
>  * igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:shard-skl: PASS -> FAIL (fdo#108145 / i915#265) +1 similar issue
>  * igt@kms_psr@psr2_sprite_plane_move:shard-iclb: PASS -> SKIP (fdo#109441) +2 similar issues
> Possible fixes * igt@gem_exec_reloc@basic-many-active@bcs0:shard-glk: FAIL (i915#2389) -> PASS
>  * igt@gem_mmap_gtt@medium-copy-xy:shard-iclb: DMESG-WARN (i915#1982) -> PASS
>  * igt@gem_mmap_offset@blt-coherency:shard-glk: FAIL (i915#2328) -> PASS
>  * igt@gem_userptr_blits@sync-unmap-cycles:shard-skl: TIMEOUT (i915#2424) -> PASS
>  * {igt@kms_async_flips@async-flip-with-page-flip-events}:shard-kbl: FAIL (i915#2521) -> PASS
>  * igt@kms_atomic_transition@plane-all-modeset-transition-fencing-internal-panels@edp-1-pipe-a:shard-skl: DMESG-WARN (i915#1982) -> PASS +4 similar
> issues
>  * igt@kms_flip@flip-vs-blocking-wf-vblank@b-edp1:shard-tglb: DMESG-WARN (i915#1982) -> PASS +3 similar issues
>  * igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1:shard-skl: FAIL (i915#2122) -> PASS +1 similar issue
>  * igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:shard-kbl: DMESG-WARN (i915#180) -> PASS +6 similar issues
>  * igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw:shard-kbl: DMESG-WARN (i915#1982) -> PASS
>  * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:shard-skl: INCOMPLETE (i915#198) -> PASS +1 similar issue
>  * igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:shard-skl: FAIL (fdo#108145 / i915#265) -> PASS
>  * igt@kms_psr@psr2_cursor_render:shard-iclb: SKIP (fdo#109441) -> PASS +1 similar issue
>  * igt@kms_setmode@basic:shard-apl: FAIL (i915#1635 / i915#31) -> PASS
>  * igt@sysfs_timeslice_duration@timeout@vecs0:shard-glk: FAIL (i915#1755) -> PASS
> {name}: This element is suppressed. This means it is ignored when computing
>  the status of the difference (SUCCESS, WARNING, or FAILURE).
> Participating hosts (11 -> 12)Additional (1): pig-snb-2600 
> Build changes * Linux: CI_DRM_9097 -> Patchwork_18625
> CI-20190529: 20190529
>  CI_DRM_9097: 5f854df6a9500c0888864bb0be25995ccb696e41 @ git://anongit.freedesktop.org/gfx-ci/linux
>  IGT_5800: 982ca4122fd4f04ad3dfa80c6246f190b36e0c72 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
>  Patchwork_18625: 68870e5d103dec6a4a8c09849a771dee2dbd4ecb @ git://anongit.freedesktop.org/gfx-ci/linux
>  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-10-23 21:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 23:16 [Intel-gfx] [PATCH] drm/i915/tgl/psr: Fix glitches when doing frontbuffer modifications José Roberto de Souza
2020-10-02 23:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-10-03  1:26 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-10-05 18:55   ` Souza, Jose
2020-10-05 19:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/tgl/psr: Fix glitches when doing frontbuffer modifications (rev2) Patchwork
2020-10-05 21:48 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-10-23 21:31   ` Souza, Jose [this message]
2020-10-12 18:12 ` [Intel-gfx] [PATCH] drm/i915/tgl/psr: Fix glitches when doing frontbuffer modifications Mun, Gwan-gyeong
2020-10-12 18:15   ` Souza, Jose
2020-10-12 19:04     ` Mun, Gwan-gyeong
2020-10-22 12:43 ` Mun, Gwan-gyeong
2020-10-22 12:48   ` Mun, Gwan-gyeong
2020-10-23 21:27     ` Souza, Jose

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=c9e11469a7cb95d7db33b67198afb5668ffe934c.camel@intel.com \
    --to=jose.souza@intel.com \
    --cc=intel-gfx@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