From: "C, Ramalingam" <ramalingam.c@intel.com>
To: Martin Peres <martin.peres@linux.intel.com>,
intel-gfx@lists.freedesktop.org,
Patchwork <patchwork@emeril.freedesktop.org>
Subject: Re: ✗ Fi.CI.IGT: failure for Implement HDCP2.2: PART-I (rev2)
Date: Mon, 29 Oct 2018 20:37:39 +0530 [thread overview]
Message-ID: <90de6f40-6e4b-3c2f-255e-9646fa43b2cb@intel.com> (raw)
In-Reply-To: <9380be29-a91b-df29-0f30-a9c431121931@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 9247 bytes --]
On 10/29/2018 8:16 PM, Martin Peres wrote:
>
> On 29/10/2018 13:55, Patchwork wrote:
>> == Series Details ==
>>
>> Series: Implement HDCP2.2: PART-I (rev2)
>> URL : https://patchwork.freedesktop.org/series/51495/
>> State : failure
>>
>> == Summary ==
>>
>> = CI Bug Log - changes from CI_DRM_5044_full -> Patchwork_10620_full =
>>
>> == Summary - FAILURE ==
>>
>> Serious unknown changes coming with Patchwork_10620_full absolutely need to be
>> verified manually.
>>
>> If you think the reported changes have nothing to do with the changes
>> introduced in Patchwork_10620_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_10620_full:
>>
>> === IGT changes ===
>>
>> ==== Possible regressions ====
>>
>> igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
>> shard-apl: PASS -> FAIL
> https://bugs.freedesktop.org/show_bug.cgi?id=104894
>
>>
>> ==== Warnings ====
>>
>> igt@kms_atomic_transition@1x-modeset-transitions-nonblocking-fencing:
>> shard-apl: DMESG-FAIL (fdo#108549) -> FAIL +2
> This part is not noise. The test was not failing before and it still
> does now. Please fix!
So igt@kms_atomic_transition@1x-modeset-transitions-nonblocking-fencing failed atCI_DRM_5044 <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5044/> andPatchwork_10620. <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10620/>
This series improves the result removes the DRM WARNINGS( by making them as debug logs.)
But the HDCP attempts(because of known bug at IGT) will be avoided as soon as https://patchwork.freedesktop.org/patch/258692/ is merged.
So I dont see anything to be fixed here.
--Ram
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10620/>
>>
>> == Known issues ==
>>
>> Here are the changes found in Patchwork_10620_full that come from known issues:
>>
>> === IGT changes ===
>>
>> ==== Issues hit ====
>>
>> igt@drv_suspend@shrink:
>> shard-skl: NOTRUN -> INCOMPLETE (fdo#106886)
>> shard-glk: PASS -> INCOMPLETE (fdo#103359, fdo#106886, k.org#198133)
>>
>> igt@gem_cpu_reloc@full:
>> shard-skl: NOTRUN -> INCOMPLETE (fdo#108073)
>>
>> igt@gem_exec_schedule@pi-ringfull-bsd:
>> shard-skl: NOTRUN -> FAIL (fdo#103158) +2
>>
>> igt@gem_ppgtt@blt-vs-render-ctxn:
>> shard-skl: NOTRUN -> TIMEOUT (fdo#108039)
>>
>> igt@kms_busy@extended-modeset-hang-newfb-render-a:
>> shard-skl: NOTRUN -> DMESG-WARN (fdo#107956) +4
>>
>> igt@kms_cursor_crc@cursor-128x42-onscreen:
>> shard-apl: PASS -> FAIL (fdo#103232) +2
>>
>> igt@kms_cursor_crc@cursor-64x21-offscreen:
>> shard-skl: NOTRUN -> FAIL (fdo#103232)
>>
>> igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy:
>> shard-glk: PASS -> FAIL (fdo#104873)
>>
>> igt@kms_fbcon_fbt@psr-suspend:
>> shard-skl: NOTRUN -> FAIL (fdo#107882) +1
>>
>> igt@kms_flip@2x-flip-vs-expired-vblank-interruptible:
>> shard-glk: PASS -> FAIL (fdo#105363)
>>
>> igt@kms_frontbuffer_tracking@fbcpsr-rgb565-draw-pwrite:
>> shard-snb: SKIP -> INCOMPLETE (fdo#105411)
>>
>> igt@kms_plane@pixel-format-pipe-c-planes:
>> shard-skl: NOTRUN -> DMESG-FAIL (fdo#103166, fdo#106885)
>>
>> igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
>> shard-skl: NOTRUN -> INCOMPLETE (fdo#104108)
>>
>> igt@kms_plane_alpha_blend@pipe-a-alpha-7efc:
>> shard-skl: NOTRUN -> FAIL (fdo#108145, fdo#107815) +2
>>
>> igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
>> shard-skl: NOTRUN -> FAIL (fdo#108145) +8
>>
>> igt@kms_plane_multiple@atomic-pipe-c-tiling-y:
>> shard-skl: NOTRUN -> FAIL (fdo#103166, fdo#107815)
>>
>> igt@kms_universal_plane@universal-plane-pipe-a-functional:
>> shard-apl: PASS -> FAIL (fdo#103166) +1
>>
>>
>> ==== Possible fixes ====
>>
>> igt@drv_suspend@debugfs-reader:
>> shard-skl: INCOMPLETE (fdo#104108) -> PASS
>>
>> igt@kms_busy@extended-modeset-hang-newfb-render-a:
>> shard-kbl: DMESG-WARN (fdo#107956) -> PASS
>>
>> igt@kms_chv_cursor_fail@pipe-b-128x128-bottom-edge:
>> shard-skl: FAIL (fdo#104671) -> PASS +1
>>
>> igt@kms_color@pipe-b-ctm-max:
>> shard-apl: DMESG-WARN (fdo#108549) -> PASS +22
>>
>> igt@kms_cursor_crc@cursor-64x21-sliding:
>> shard-apl: FAIL (fdo#103232) -> PASS +2
>>
>> igt@kms_cursor_crc@cursor-64x64-sliding:
>> shard-apl: DMESG-FAIL (fdo#108549, fdo#103232) -> PASS
>>
>> igt@kms_cursor_crc@cursor-64x64-suspend:
>> shard-apl: FAIL (fdo#103232, fdo#103191) -> PASS
>>
>> igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-cpu:
>> shard-glk: DMESG-WARN (fdo#105763, fdo#106538) -> PASS +1
>>
>> igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite:
>> shard-apl: FAIL (fdo#103167) -> PASS
>>
>> igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
>> shard-apl: FAIL (fdo#103375) -> PASS
>>
>> igt@kms_plane@plane-panning-top-left-pipe-b-planes:
>> shard-apl: INCOMPLETE (fdo#103927) -> PASS
>>
>> igt@kms_plane@plane-position-covered-pipe-a-planes:
>> shard-glk: FAIL (fdo#103166) -> PASS
>>
>> igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
>> shard-skl: FAIL (fdo#107815) -> PASS
>>
>> igt@kms_plane_multiple@atomic-pipe-a-tiling-x:
>> shard-apl: FAIL (fdo#103166) -> PASS
>>
>> igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend:
>> shard-snb: DMESG-WARN (fdo#102365) -> PASS
>>
>> igt@kms_vblank@pipe-c-ts-continuation-dpms-rpm:
>> shard-apl: DMESG-FAIL (fdo#108549) -> PASS
>>
>> igt@pm_rpm@dpms-lpsp:
>> shard-skl: INCOMPLETE (fdo#107807) -> PASS
>>
>>
>> {name}: This element is suppressed. This means it is ignored when computing
>> the status of the difference (SUCCESS, WARNING, or FAILURE).
>>
>> fdo#102365 https://bugs.freedesktop.org/show_bug.cgi?id=102365
>> fdo#103158 https://bugs.freedesktop.org/show_bug.cgi?id=103158
>> fdo#103166 https://bugs.freedesktop.org/show_bug.cgi?id=103166
>> fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
>> fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
>> fdo#103232 https://bugs.freedesktop.org/show_bug.cgi?id=103232
>> fdo#103359 https://bugs.freedesktop.org/show_bug.cgi?id=103359
>> fdo#103375 https://bugs.freedesktop.org/show_bug.cgi?id=103375
>> fdo#103927 https://bugs.freedesktop.org/show_bug.cgi?id=103927
>> fdo#104108 https://bugs.freedesktop.org/show_bug.cgi?id=104108
>> fdo#104671 https://bugs.freedesktop.org/show_bug.cgi?id=104671
>> fdo#104873 https://bugs.freedesktop.org/show_bug.cgi?id=104873
>> fdo#105363 https://bugs.freedesktop.org/show_bug.cgi?id=105363
>> fdo#105411 https://bugs.freedesktop.org/show_bug.cgi?id=105411
>> fdo#105763 https://bugs.freedesktop.org/show_bug.cgi?id=105763
>> fdo#106538 https://bugs.freedesktop.org/show_bug.cgi?id=106538
>> fdo#106885 https://bugs.freedesktop.org/show_bug.cgi?id=106885
>> fdo#106886 https://bugs.freedesktop.org/show_bug.cgi?id=106886
>> fdo#107807 https://bugs.freedesktop.org/show_bug.cgi?id=107807
>> fdo#107815 https://bugs.freedesktop.org/show_bug.cgi?id=107815
>> fdo#107882 https://bugs.freedesktop.org/show_bug.cgi?id=107882
>> fdo#107956 https://bugs.freedesktop.org/show_bug.cgi?id=107956
>> fdo#108039 https://bugs.freedesktop.org/show_bug.cgi?id=108039
>> fdo#108073 https://bugs.freedesktop.org/show_bug.cgi?id=108073
>> fdo#108145 https://bugs.freedesktop.org/show_bug.cgi?id=108145
>> fdo#108549 https://bugs.freedesktop.org/show_bug.cgi?id=108549
>> k.org#198133 https://bugzilla.kernel.org/show_bug.cgi?id=198133
>>
>>
>> == Participating hosts (6 -> 6) ==
>>
>> No changes in participating hosts
>>
>>
>> == Build changes ==
>>
>> * Linux: CI_DRM_5044 -> Patchwork_10620
>>
>> CI_DRM_5044: c4487dca27970879bf67f331614142c749984d65 @ git://anongit.freedesktop.org/gfx-ci/linux
>> IGT_4698: af57164fcb16950187ad402ed31f565e88c42a78 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
>> Patchwork_10620: eb45139dab6aaa52b467d2ec73ddfc9c8d55ae72 @ git://anongit.freedesktop.org/gfx-ci/linux
>> piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
>>
>> == Logs ==
>>
>> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10620/shards.html
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>>
[-- Attachment #1.2: Type: text/html, Size: 14164 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-10-29 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 9:45 [PATCH v2 0/6] Implement HDCP2.2: PART-I Ramalingam C
2018-10-29 9:45 ` [PATCH v2 1/6] drm/i915: wrapping all hdcp var into intel_hdcp Ramalingam C
2018-10-29 9:45 ` [PATCH v2 2/6] drm/i915: Reassigning log level for HDCP failures Ramalingam C
2018-10-29 9:45 ` [PATCH v2 3/6] drm/i915: Cancel the Link check before disable Ramalingam C
2018-10-29 15:18 ` Daniel Vetter
2018-10-29 9:45 ` [PATCH v2 4/6] drm: hdcp2.2 authentication msg definitions Ramalingam C
2018-10-29 9:45 ` [PATCH v2 5/6] drm: HDMI and DP specific HDCP2.2 defines Ramalingam C
2018-10-29 9:45 ` [PATCH v2 6/6] drm/i915: Define Intel HDCP2.2 registers Ramalingam C
2018-10-29 15:31 ` Daniel Vetter
2018-10-29 10:40 ` ✓ Fi.CI.BAT: success for Implement HDCP2.2: PART-I (rev2) Patchwork
2018-10-29 11:55 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-10-29 14:46 ` Martin Peres
2018-10-29 15:07 ` C, Ramalingam [this message]
2018-10-30 10:27 ` ✗ Fi.CI.BAT: " Patchwork
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=90de6f40-6e4b-3c2f-255e-9646fa43b2cb@intel.com \
--to=ramalingam.c@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=martin.peres@linux.intel.com \
--cc=patchwork@emeril.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