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: success for drm/i915: Implement WA 14011294188 (rev2)
Date: Tue, 28 Jul 2020 01:45:31 +0000 [thread overview]
Message-ID: <6483bedeab1e92c02a31d45df9f83eea4d29abcc.camel@intel.com> (raw)
In-Reply-To: <159588311411.26746.7787315533182984275@emeril.freedesktop.org>
On Mon, 2020-07-27 at 20:51 +0000, Patchwork wrote:
> Patch Details
> Series: drm/i915: Implement WA 14011294188 (rev2)
> URL: https://patchwork.freedesktop.org/series/79825/
> State: success
> Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18245/index.html
> CI Bug Log - changes from CI_DRM_8797_full -> Patchwork_18245_full
> Summary
> SUCCESS
>
> No regressions found.
Thanks for the review Matt.Pushed to dinq.
>
> Possible new issues
> Here are the unknown changes that may have been introduced in Patchwork_18245_full:
>
> Piglit changes
> Possible regressions
> spec@glsl-4.20@execution@vs_in@vs-input-double_dvec3-position-float_mat4x2_array3 (NEW):
>
> {pig-icl-1065g7}: NOTRUN -> INCOMPLETE +5 similar issues
> spec@glsl-4.20@execution@vs_in@vs-input-position-int_int-double_dmat3x4_array2 (NEW):
>
> {pig-icl-1065g7}: NOTRUN -> CRASH +1 similar issue
> New tests
> New tests have been introduced between CI_DRM_8797_full and Patchwork_18245_full:
>
> New Piglit tests (8)
> spec@glsl-4.20@execution@vs_in@vs-input-double_dmat3-position-double_dmat2x4_array2:
>
> Statuses : 1 crash(s)
> Exec time: [0.86] s
> spec@glsl-4.20@execution@vs_in@vs-input-double_dmat3x2-position-float_vec4_array3:
>
> Statuses : 1 incomplete(s)
> Exec time: [0.0] s
> spec@glsl-4.20@execution@vs_in@vs-input-double_dvec3-position-float_mat4x2_array3:
>
> Statuses : 1 incomplete(s)
> Exec time: [0.0] s
> spec@glsl-4.20@execution@vs_in@vs-input-float_mat2x3_array3-position-double_dmat4x3_array2:
>
> Statuses : 1 incomplete(s)
> Exec time: [0.0] s
> spec@glsl-4.20@execution@vs_in@vs-input-float_mat2x4_array3-position-double_dvec4_array2:
>
> Statuses : 1 incomplete(s)
> Exec time: [0.0] s
> spec@glsl-4.20@execution@vs_in@vs-input-float_vec2-double_dmat4_array2-position:
>
> Statuses : 1 incomplete(s)
> Exec time: [0.0] s
> spec@glsl-4.20@execution@vs_in@vs-input-position-double_dmat2x4_array5-float_vec3_array3:
>
> Statuses : 1 incomplete(s)
> Exec time: [0.0] s
> spec@glsl-4.20@execution@vs_in@vs-input-position-int_int-double_dmat3x4_array2:
>
> Statuses : 1 crash(s)
> Exec time: [0.87] s
> Known issues
> Here are the changes found in Patchwork_18245_full that come from known issues:
>
> IGT changes
> Issues hit
> igt@gem_exec_whisper@basic-queues:
>
> shard-iclb: PASS -> DMESG-WARN (i915#1982)
> igt@kms_busy@basic-flip-pipe-c:
>
> shard-skl: PASS -> DMESG-WARN (i915#1982) +11 similar issues
> igt@kms_cursor_crc@pipe-b-cursor-64x64-offscreen:
>
> shard-skl: PASS -> FAIL (i915#54)
> igt@kms_cursor_legacy@pipe-b-torture-bo:
>
> shard-iclb: PASS -> DMESG-WARN (i915#128)
> igt@kms_draw_crc@draw-method-rgb565-blt-untiled:
>
> shard-skl: PASS -> FAIL (i915#52 / i915#54)
> igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
>
> shard-kbl: PASS -> DMESG-WARN (i915#180) +12 similar issues
> igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1:
>
> shard-skl: PASS -> DMESG-FAIL (i915#1982)
> igt@kms_frontbuffer_tracking@fbc-badstride:
>
> shard-glk: PASS -> DMESG-WARN (i915#1982)
> igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-mmap-gtt:
>
> shard-tglb: PASS -> DMESG-WARN (i915#1982) +2 similar issues
> igt@kms_hdr@bpc-switch-suspend:
>
> shard-skl: PASS -> FAIL (i915#1188)
> igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes:
>
> shard-tglb: PASS -> INCOMPLETE (i915#456)
> igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
>
> shard-skl: PASS -> FAIL (fdo#108145 / i915#265)
> igt@kms_psr@psr2_sprite_mmap_cpu:
>
> shard-iclb: PASS -> SKIP (fdo#109441) +1 similar issue
> igt@kms_setmode@basic:
>
> shard-apl: PASS -> FAIL (i915#1635 / i915#31)
>
> shard-hsw: PASS -> FAIL (i915#31)
>
> Possible fixes
> igt@gem_ctx_isolation@preservation-s3@rcs0:
>
> shard-skl: INCOMPLETE (i915#198) -> PASS
> igt@gem_eio@in-flight-suspend:
>
> shard-skl: DMESG-WARN (i915#1982) -> PASS +5 similar issues
> igt@gem_exec_whisper@basic-forked:
>
> shard-glk: DMESG-WARN (i915#118 / i915#95) -> PASS
> igt@gem_huc_copy@huc-copy:
>
> shard-tglb: SKIP (i915#2190) -> PASS
> igt@gem_linear_blits@normal:
>
> shard-tglb: DMESG-WARN (i915#402) -> PASS
> igt@kms_atomic_interruptible@universal-setplane-primary:
>
> shard-apl: DMESG-WARN (i915#1635 / i915#62) -> PASS +7 similar issues
> igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy:
>
> shard-glk: FAIL (i915#72) -> PASS
> igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-pwrite:
>
> shard-tglb: DMESG-WARN (i915#1982) -> PASS
> igt@kms_hdr@bpc-switch:
>
> shard-skl: FAIL (i915#1188) -> PASS
> igt@kms_hdr@bpc-switch-suspend:
>
> shard-kbl: DMESG-WARN (i915#180) -> PASS +6 similar issues
> igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
>
> shard-skl: FAIL (fdo#108145 / i915#265) -> PASS +1 similar issue
> igt@kms_psr@psr2_cursor_plane_move:
>
> shard-iclb: SKIP (fdo#109441) -> PASS +1 similar issue
> igt@kms_vblank@pipe-c-wait-busy-hang:
>
> shard-apl: DMESG-WARN (i915#1635 / i915#1982) -> PASS +1 similar issue
> Warnings
> igt@kms_plane_alpha_blend@pipe-a-alpha-basic:
>
> shard-apl: DMESG-FAIL (fdo#108145 / i915#1635 / i915#62) -> FAIL (fdo#108145 / i915#1635 / i915#265)
>
> shard-skl: FAIL (fdo#108145 / i915#265) -> DMESG-FAIL (fdo#108145 / i915#1982) +1 similar issue
>
> igt@runner@aborted:
>
> shard-apl: (FAIL, FAIL, FAIL, FAIL, FAIL, FAIL, FAIL, FAIL, FAIL, FAIL, FAIL, FAIL, FAIL, FAIL) (i915#1610 / i915#1635 / i915#2110 / i915#637) -> FAIL (i915#1635 / i915#2110)
> {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_8797 -> Patchwork_18245
> CI-20190529: 20190529
> CI_DRM_8797: 37345f3896e61d4ba2e877ce5098c850e3bf03fd @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_5749: 2fef871e791ceab7841b899691c443167550173d @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_18245: 2c56ac274090f4372a4e348ca6eeae94be21d198 @ 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
prev parent reply other threads:[~2020-07-28 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 16:47 [Intel-gfx] [PATCH CI] drm/i915: Implement WA 14011294188 José Roberto de Souza
2020-07-27 18:05 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Implement WA 14011294188 (rev2) Patchwork
2020-07-27 18:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-07-27 20:51 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-07-28 1:45 ` Souza, Jose [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=6483bedeab1e92c02a31d45df9f83eea4d29abcc.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;
as well as URLs for NNTP newsgroup(s).