From: "Souza, Jose" <jose.souza@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"tianjia.zhang@linux.alibaba.com"
<tianjia.zhang@linux.alibaba.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Fix wrong return value in intel_atomic_check()
Date: Mon, 3 Aug 2020 19:38:32 +0000 [thread overview]
Message-ID: <67663123e2974bd238b0e84c6faaa50ee7237cfd.camel@intel.com> (raw)
In-Reply-To: <159647273843.19294.14246855210418932506@emeril.freedesktop.org>
On Mon, 2020-08-03 at 16:38 +0000, Patchwork wrote:
> Patch Details
> Series: drm/i915: Fix wrong return value in intel_atomic_check()
> URL: https://patchwork.freedesktop.org/series/80208/
> State: failure
> Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18299/index.html
> CI Bug Log - changes from CI_DRM_8834_full -> Patchwork_18299_full
> Summary
> FAILURE
>
> Serious unknown changes coming with Patchwork_18299_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_18299_full, please notify your bug team to allow them
> to document this new failure mode, which will reduce false positives in CI.
>
> Possible new issues
> Here are the unknown changes that may have been introduced in Patchwork_18299_full:
>
> IGT changes
> Possible regressions
> igt@gem_mmap_gtt@fault-concurrent:
>
This regression is not related with this changes.Pushed to dinq, thanks for the patch.
> shard-snb: PASS -> DMESG-WARN
> igt@runner@aborted:
>
> shard-snb: NOTRUN -> FAIL
> Known issues
> Here are the changes found in Patchwork_18299_full that come from known issues:
>
> IGT changes
> Issues hit
> igt@gen9_exec_parse@allowed-all:
>
> shard-apl: PASS -> DMESG-WARN (i915#1436 / i915#1635 / i915#716)
> igt@gen9_exec_parse@allowed-single:
>
> shard-skl: PASS -> INCOMPLETE (i915#1436 / i915#716)
> igt@i915_selftest@mock@contexts:
>
> shard-apl: PASS -> INCOMPLETE (i915#1635)
> igt@kms_big_fb@y-tiled-64bpp-rotate-0:
>
> shard-glk: PASS -> DMESG-FAIL (i915#118 / i915#95)
> igt@kms_cursor_edge_walk@pipe-c-256x256-bottom-edge:
>
> shard-skl: PASS -> DMESG-WARN (i915#1982) +14 similar issues
> igt@kms_flip@2x-plain-flip-ts-check@ab-hdmi-a1-hdmi-a2:
>
> shard-glk: PASS -> FAIL (i915#2122)
> igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@a-dp1:
>
> shard-kbl: PASS -> DMESG-WARN (i915#1982)
> igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1:
>
> shard-skl: PASS -> FAIL (i915#2122)
> igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
>
> shard-kbl: PASS -> DMESG-WARN (i915#180) +5 similar issues
> igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-pwrite:
>
> shard-tglb: PASS -> DMESG-WARN (i915#1982) +4 similar issues
> igt@kms_hdr@bpc-switch:
>
> shard-skl: PASS -> FAIL (i915#1188)
> igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
>
> shard-iclb: PASS -> INCOMPLETE (i915#1185)
> igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
>
> shard-skl: PASS -> FAIL (fdo#108145 / i915#265) +1 similar issue
> igt@kms_psr2_su@frontbuffer:
>
> shard-iclb: PASS -> SKIP (fdo#109642 / fdo#111068) +1 similar issue
> igt@kms_psr@psr2_cursor_render:
>
> shard-iclb: PASS -> SKIP (fdo#109441) +3 similar issues
> igt@perf_pmu@module-unload:
>
> shard-iclb: PASS -> DMESG-WARN (i915#1982)
> Possible fixes
> {igt@feature_discovery@psr2}:
>
> shard-iclb: SKIP (i915#658) -> PASS
> igt@gem_exec_suspend@basic-s3:
>
> shard-skl: INCOMPLETE -> PASS
> igt@gem_mmap_gtt@fault-concurrent:
>
> shard-glk: DMESG-WARN (i915#2165) -> PASS
> igt@gem_partial_pwrite_pread@writes-after-reads-uncached:
>
> shard-apl: FAIL (i915#1635) -> PASS
> igt@gen9_exec_parse@allowed-all:
>
> shard-kbl: DMESG-WARN (i915#1436 / i915#716) -> PASS
> igt@i915_selftest@mock@requests:
>
> shard-skl: INCOMPLETE (i915#198) -> PASS
> igt@kms_big_fb@y-tiled-64bpp-rotate-180:
>
> shard-glk: DMESG-FAIL (i915#118 / i915#95) -> PASS
> igt@kms_big_fb@y-tiled-8bpp-rotate-180:
>
> shard-kbl: DMESG-WARN (i915#1982) -> PASS
> igt@kms_frontbuffer_tracking@fbc-suspend:
>
> shard-kbl: DMESG-WARN (i915#180) -> PASS +3 similar issues
> igt@kms_hdr@bpc-switch-suspend:
>
> shard-skl: FAIL (i915#1188) -> PASS
> igt@kms_plane@plane-panning-bottom-right-pipe-c-planes:
>
> shard-skl: DMESG-WARN (i915#1982) -> PASS +6 similar issues
> igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes:
>
> shard-glk: DMESG-WARN (i915#1982) -> PASS
> igt@kms_psr@psr2_primary_mmap_gtt:
>
> shard-iclb: SKIP (fdo#109441) -> PASS +1 similar issue
> igt@kms_setmode@basic:
>
> shard-kbl: FAIL (i915#31) -> PASS
> Warnings
> igt@gem_exec_reloc@basic-concurrent0:
>
> shard-apl: INCOMPLETE (i915#1635) -> FAIL (i915#1635 / i915#1930)
> igt@gem_exec_reloc@basic-spin-others@vcs0:
>
> shard-snb: WARN (i915#2021) -> WARN (i915#2036)
> igt@kms_content_protection@lic:
>
> shard-kbl: TIMEOUT (i915#1319) -> TIMEOUT (i915#1319 / i915#1958)
> igt@kms_content_protection@srm:
>
> shard-kbl: TIMEOUT (i915#1319 / i915#1958) -> TIMEOUT (i915#1319)
> igt@kms_dp_dsc@basic-dsc-enable-edp:
>
> shard-iclb: DMESG-WARN (i915#1226) -> SKIP (fdo#109349)
> igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1:
>
> shard-skl: DMESG-WARN (i915#1982) -> DMESG-FAIL (i915#1982)
> igt@runner@aborted:
>
> shard-apl: FAIL (i915#1611 / i915#1635) -> (FAIL, FAIL) (fdo#109271 / i915#1635 / i915#2110 / i915#716)
> {name}: This element is suppressed. This means it is ignored when computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
> Participating hosts (11 -> 11)
> No changes in participating hosts
>
> Build changes
> Linux: CI_DRM_8834 -> Patchwork_18299
> CI-20190529: 20190529
> CI_DRM_8834: ac25ad7789fe4cc689a854d823a226ce24bb0a62 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_5757: d78c7fd293cb228fe03ccff730202b033e25ff18 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_18299: c424984659634a354c06464d0590a6fd66a6ad3e @ 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
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-08-03 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 11:15 [Intel-gfx] [PATCH] drm/i915: Fix wrong return value in intel_atomic_check() Tianjia Zhang
2020-08-03 13:11 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2020-08-03 13:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-08-03 16:38 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-08-03 19:38 ` Souza, Jose [this message]
2020-08-03 19:35 ` [Intel-gfx] [PATCH] " 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=67663123e2974bd238b0e84c6faaa50ee7237cfd.camel@intel.com \
--to=jose.souza@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tianjia.zhang@linux.alibaba.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