* [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps @ 2019-09-23 18:23 ` Bhawanpreet Lakha 0 siblings, 0 replies; 22+ messages in thread From: Bhawanpreet Lakha @ 2019-09-23 18:23 UTC (permalink / raw) To: igt-dev, intel-gfx; +Cc: Bhawanpreet Lakha Rename "i915_hdcp_sink_capability" to "hdcp_sink_capability" The content protection tests only start if this debugfs entry exists. Since the name is specific to intel driver these tests cannot be used with other drivers. Remove "i915" so the debugfs name is generic. Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> --- tests/kms_content_protection.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c index e676b60b..a105c5de 100644 --- a/tests/kms_content_protection.c +++ b/tests/kms_content_protection.c @@ -554,7 +554,7 @@ static bool sink_hdcp_capable(igt_output_t *output) if (fd < 0) return false; - debugfs_read(fd, "i915_hdcp_sink_capability", buf); + debugfs_read(fd, "hdcp_sink_capability", buf); close(fd); igt_debug("Sink capability: %s\n", buf); @@ -571,7 +571,7 @@ static bool sink_hdcp2_capable(igt_output_t *output) if (fd < 0) return false; - debugfs_read(fd, "i915_hdcp_sink_capability", buf); + debugfs_read(fd, "hdcp_sink_capability", buf); close(fd); igt_debug("Sink capability: %s\n", buf); -- 2.17.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 22+ messages in thread
* [Intel-gfx] [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps @ 2019-09-23 18:23 ` Bhawanpreet Lakha 0 siblings, 0 replies; 22+ messages in thread From: Bhawanpreet Lakha @ 2019-09-23 18:23 UTC (permalink / raw) To: igt-dev, intel-gfx; +Cc: Bhawanpreet Lakha Rename "i915_hdcp_sink_capability" to "hdcp_sink_capability" The content protection tests only start if this debugfs entry exists. Since the name is specific to intel driver these tests cannot be used with other drivers. Remove "i915" so the debugfs name is generic. Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> --- tests/kms_content_protection.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c index e676b60b..a105c5de 100644 --- a/tests/kms_content_protection.c +++ b/tests/kms_content_protection.c @@ -554,7 +554,7 @@ static bool sink_hdcp_capable(igt_output_t *output) if (fd < 0) return false; - debugfs_read(fd, "i915_hdcp_sink_capability", buf); + debugfs_read(fd, "hdcp_sink_capability", buf); close(fd); igt_debug("Sink capability: %s\n", buf); @@ -571,7 +571,7 @@ static bool sink_hdcp2_capable(igt_output_t *output) if (fd < 0) return false; - debugfs_read(fd, "i915_hdcp_sink_capability", buf); + debugfs_read(fd, "hdcp_sink_capability", buf); close(fd); igt_debug("Sink capability: %s\n", buf); -- 2.17.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 22+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for test/kms_content_protection: Use generic debugfs name for HDCP caps 2019-09-23 18:23 ` [Intel-gfx] " Bhawanpreet Lakha (?) @ 2019-09-23 19:09 ` Patchwork -1 siblings, 0 replies; 22+ messages in thread From: Patchwork @ 2019-09-23 19:09 UTC (permalink / raw) To: Bhawanpreet Lakha; +Cc: igt-dev == Series Details == Series: test/kms_content_protection: Use generic debugfs name for HDCP caps URL : https://patchwork.freedesktop.org/series/67125/ State : success == Summary == CI Bug Log - changes from CI_DRM_6944 -> IGTPW_3492 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://patchwork.freedesktop.org/api/1.0/series/67125/revisions/1/mbox/ Known issues ------------ Here are the changes found in IGTPW_3492 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_exec_fence@nb-await-default: - fi-icl-u3: [PASS][1] -> [DMESG-WARN][2] ([fdo#107724]) +2 similar issues [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/fi-icl-u3/igt@gem_exec_fence@nb-await-default.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/fi-icl-u3/igt@gem_exec_fence@nb-await-default.html #### Possible fixes #### * igt@gem_cpu_reloc@basic: - {fi-tgl-u}: [INCOMPLETE][3] -> [PASS][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/fi-tgl-u/igt@gem_cpu_reloc@basic.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/fi-tgl-u/igt@gem_cpu_reloc@basic.html * igt@gem_exec_suspend@basic-s3: - fi-blb-e6850: [INCOMPLETE][5] ([fdo#107718]) -> [PASS][6] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html * igt@gem_mmap_gtt@basic-write: - fi-icl-u3: [DMESG-WARN][7] ([fdo#107724]) -> [PASS][8] [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/fi-icl-u3/igt@gem_mmap_gtt@basic-write.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/fi-icl-u3/igt@gem_mmap_gtt@basic-write.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718 [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724 [fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045 [fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096 [fdo#111381]: https://bugs.freedesktop.org/show_bug.cgi?id=111381 [fdo#111600]: https://bugs.freedesktop.org/show_bug.cgi?id=111600 Participating hosts (54 -> 47) ------------------------------ Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus Build changes ------------- * CI: CI-20190529 -> None * IGT: IGT_5197 -> IGTPW_3492 CI-20190529: 20190529 CI_DRM_6944: 2c9a75480b3c8a78ed86404c8c0afea389622df6 @ git://anongit.freedesktop.org/gfx-ci/linux IGTPW_3492: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/ IGT_5197: aa534ff47fd2f455c8be9e59eae807695b87fcdd @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/ _______________________________________________ igt-dev mailing list igt-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/igt-dev ^ permalink raw reply [flat|nested] 22+ messages in thread
* [igt-dev] ✓ Fi.CI.IGT: success for test/kms_content_protection: Use generic debugfs name for HDCP caps 2019-09-23 18:23 ` [Intel-gfx] " Bhawanpreet Lakha (?) (?) @ 2019-09-24 6:53 ` Patchwork -1 siblings, 0 replies; 22+ messages in thread From: Patchwork @ 2019-09-24 6:53 UTC (permalink / raw) To: Bhawanpreet Lakha; +Cc: igt-dev == Series Details == Series: test/kms_content_protection: Use generic debugfs name for HDCP caps URL : https://patchwork.freedesktop.org/series/67125/ State : success == Summary == CI Bug Log - changes from CI_DRM_6944_full -> IGTPW_3492_full ==================================================== Summary ------- **WARNING** Minor unknown changes coming with IGTPW_3492_full need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in IGTPW_3492_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. External URL: https://patchwork.freedesktop.org/api/1.0/series/67125/revisions/1/mbox/ Possible new issues ------------------- Here are the unknown changes that may have been introduced in IGTPW_3492_full: ### IGT changes ### #### Warnings #### * igt@kms_content_protection@atomic: - shard-kbl: [FAIL][1] ([fdo#110321] / [fdo#110336]) -> [FAIL][2] +2 similar issues [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-kbl7/igt@kms_content_protection@atomic.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-kbl3/igt@kms_content_protection@atomic.html * igt@kms_content_protection@atomic-dpms: - shard-apl: [FAIL][3] ([fdo#110321] / [fdo#110336]) -> [FAIL][4] +2 similar issues [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-apl8/igt@kms_content_protection@atomic-dpms.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-apl4/igt@kms_content_protection@atomic-dpms.html * igt@kms_content_protection@lic: - shard-apl: [FAIL][5] ([fdo#110321]) -> [FAIL][6] +1 similar issue [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-apl2/igt@kms_content_protection@lic.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-apl6/igt@kms_content_protection@lic.html * igt@kms_content_protection@srm: - shard-glk: [SKIP][7] ([fdo#109271]) -> [FAIL][8] +8 similar issues [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-glk2/igt@kms_content_protection@srm.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-glk1/igt@kms_content_protection@srm.html - shard-kbl: [FAIL][9] ([fdo#110321]) -> [FAIL][10] +1 similar issue [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-kbl3/igt@kms_content_protection@srm.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-kbl1/igt@kms_content_protection@srm.html * igt@kms_content_protection@type1: - shard-kbl: [SKIP][11] ([fdo#109271]) -> [FAIL][12] +2 similar issues [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-kbl3/igt@kms_content_protection@type1.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-kbl3/igt@kms_content_protection@type1.html * igt@kms_content_protection@uevent: - shard-kbl: [FAIL][13] ([fdo#111313]) -> [FAIL][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-kbl7/igt@kms_content_protection@uevent.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-kbl7/igt@kms_content_protection@uevent.html - shard-apl: [FAIL][15] ([fdo#111313]) -> [FAIL][16] [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-apl7/igt@kms_content_protection@uevent.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-apl7/igt@kms_content_protection@uevent.html Known issues ------------ Here are the changes found in IGTPW_3492_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_bad_reloc@negative-reloc-bsd2: - shard-iclb: [PASS][17] -> [SKIP][18] ([fdo#109276]) +14 similar issues [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb1/igt@gem_bad_reloc@negative-reloc-bsd2.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb8/igt@gem_bad_reloc@negative-reloc-bsd2.html * igt@gem_exec_schedule@deep-bsd: - shard-iclb: [PASS][19] -> [SKIP][20] ([fdo#111325]) +5 similar issues [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb8/igt@gem_exec_schedule@deep-bsd.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb1/igt@gem_exec_schedule@deep-bsd.html * igt@i915_suspend@debugfs-reader: - shard-apl: [PASS][21] -> [DMESG-WARN][22] ([fdo#108566]) +5 similar issues [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-apl8/igt@i915_suspend@debugfs-reader.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-apl8/igt@i915_suspend@debugfs-reader.html * igt@kms_cursor_legacy@pipe-b-forked-move: - shard-iclb: [PASS][23] -> [INCOMPLETE][24] ([fdo#107713]) [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb6/igt@kms_cursor_legacy@pipe-b-forked-move.html [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb7/igt@kms_cursor_legacy@pipe-b-forked-move.html * igt@kms_flip@dpms-vs-vblank-race-interruptible: - shard-apl: [PASS][25] -> [FAIL][26] ([fdo#111609]) [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-apl3/igt@kms_flip@dpms-vs-vblank-race-interruptible.html [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-apl6/igt@kms_flip@dpms-vs-vblank-race-interruptible.html * igt@kms_flip@flip-vs-expired-vblank-interruptible: - shard-glk: [PASS][27] -> [FAIL][28] ([fdo#105363]) [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-glk2/igt@kms_flip@flip-vs-expired-vblank-interruptible.html [28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-glk2/igt@kms_flip@flip-vs-expired-vblank-interruptible.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-wc: - shard-glk: [PASS][29] -> [FAIL][30] ([fdo#103167]) +1 similar issue [29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-glk5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-wc.html [30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-glk6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-wc.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt: - shard-apl: [PASS][31] -> [FAIL][32] ([fdo#103167]) +1 similar issue [31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-apl2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt.html [32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-apl2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt.html - shard-kbl: [PASS][33] -> [FAIL][34] ([fdo#103167]) +1 similar issue [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-kbl4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt.html [34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-kbl2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt: - shard-iclb: [PASS][35] -> [FAIL][36] ([fdo#103167]) [35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb7/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt.html [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt.html * igt@kms_psr@psr2_sprite_blt: - shard-iclb: [PASS][37] -> [SKIP][38] ([fdo#109441]) +1 similar issue [37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb2/igt@kms_psr@psr2_sprite_blt.html [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb3/igt@kms_psr@psr2_sprite_blt.html #### Possible fixes #### * igt@gem_ctx_shared@exec-single-timeline-bsd: - shard-iclb: [SKIP][39] ([fdo#110841]) -> [PASS][40] [39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb2/igt@gem_ctx_shared@exec-single-timeline-bsd.html [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb7/igt@gem_ctx_shared@exec-single-timeline-bsd.html * igt@gem_exec_balancer@smoke: - shard-iclb: [SKIP][41] ([fdo#110854]) -> [PASS][42] [41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb3/igt@gem_exec_balancer@smoke.html [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb2/igt@gem_exec_balancer@smoke.html * igt@gem_exec_schedule@preempt-other-bsd: - shard-iclb: [SKIP][43] ([fdo#111325]) -> [PASS][44] +1 similar issue [43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb1/igt@gem_exec_schedule@preempt-other-bsd.html [44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb3/igt@gem_exec_schedule@preempt-other-bsd.html * igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd2: - shard-iclb: [SKIP][45] ([fdo#109276]) -> [PASS][46] +11 similar issues [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb6/igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd2.html [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb1/igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd2.html * igt@i915_suspend@fence-restore-tiled2untiled: - shard-apl: [DMESG-WARN][47] ([fdo#108566]) -> [PASS][48] +7 similar issues [47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-apl3/igt@i915_suspend@fence-restore-tiled2untiled.html [48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-apl1/igt@i915_suspend@fence-restore-tiled2untiled.html * igt@kms_cursor_crc@pipe-a-cursor-256x256-random: - shard-snb: [SKIP][49] ([fdo#109271]) -> [PASS][50] +3 similar issues [49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-snb6/igt@kms_cursor_crc@pipe-a-cursor-256x256-random.html [50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-snb7/igt@kms_cursor_crc@pipe-a-cursor-256x256-random.html * igt@kms_flip@dpms-vs-vblank-race: - shard-apl: [FAIL][51] ([fdo#111609]) -> [PASS][52] [51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-apl2/igt@kms_flip@dpms-vs-vblank-race.html [52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-apl3/igt@kms_flip@dpms-vs-vblank-race.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt: - shard-iclb: [FAIL][53] ([fdo#103167]) -> [PASS][54] +5 similar issues [53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt.html [54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite: - shard-apl: [FAIL][55] ([fdo#103167]) -> [PASS][56] [55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-apl7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite.html [56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-apl6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite.html - shard-kbl: [FAIL][57] ([fdo#103167]) -> [PASS][58] [57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-kbl7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite.html [58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-kbl7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite.html * igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-mmap-cpu: - shard-glk: [FAIL][59] ([fdo#103167]) -> [PASS][60] +1 similar issue [59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-glk9/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-mmap-cpu.html [60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-glk6/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-mmap-cpu.html * igt@kms_psr@psr2_cursor_plane_onoff: - shard-iclb: [SKIP][61] ([fdo#109441]) -> [PASS][62] +1 similar issue [61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb3/igt@kms_psr@psr2_cursor_plane_onoff.html [62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html * igt@kms_rotation_crc@primary-rotation-180: - shard-iclb: [INCOMPLETE][63] ([fdo#107713] / [fdo#110026]) -> [PASS][64] [63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb7/igt@kms_rotation_crc@primary-rotation-180.html [64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb4/igt@kms_rotation_crc@primary-rotation-180.html * igt@kms_setmode@basic: - shard-apl: [FAIL][65] ([fdo#99912]) -> [PASS][66] [65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-apl7/igt@kms_setmode@basic.html [66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-apl6/igt@kms_setmode@basic.html #### Warnings #### * igt@gem_mocs_settings@mocs-isolation-bsd2: - shard-iclb: [FAIL][67] ([fdo#111330]) -> [SKIP][68] ([fdo#109276]) [67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb2/igt@gem_mocs_settings@mocs-isolation-bsd2.html [68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb6/igt@gem_mocs_settings@mocs-isolation-bsd2.html * igt@kms_dp_dsc@basic-dsc-enable-edp: - shard-iclb: [SKIP][69] ([fdo#109349]) -> [DMESG-WARN][70] ([fdo#107724]) [69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-iclb8/igt@kms_dp_dsc@basic-dsc-enable-edp.html [70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-iclb2/igt@kms_dp_dsc@basic-dsc-enable-edp.html * igt@kms_vblank@pipe-c-query-busy: - shard-snb: [SKIP][71] ([fdo#109271]) -> [SKIP][72] ([fdo#109271] / [fdo#109278]) [71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6944/shard-snb6/igt@kms_vblank@pipe-c-query-busy.html [72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/shard-snb5/igt@kms_vblank@pipe-c-query-busy.html [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167 [fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724 [fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566 [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276 [fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278 [fdo#109349]: https://bugs.freedesktop.org/show_bug.cgi?id=109349 [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441 [fdo#110026]: https://bugs.freedesktop.org/show_bug.cgi?id=110026 [fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321 [fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336 [fdo#110841]: https://bugs.freedesktop.org/show_bug.cgi?id=110841 [fdo#110854]: https://bugs.freedesktop.org/show_bug.cgi?id=110854 [fdo#111313]: https://bugs.freedesktop.org/show_bug.cgi?id=111313 [fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325 [fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330 [fdo#111609]: https://bugs.freedesktop.org/show_bug.cgi?id=111609 [fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912 Participating hosts (8 -> 6) ------------------------------ Missing (2): pig-skl-6260u shard-skl Build changes ------------- * CI: CI-20190529 -> None * IGT: IGT_5197 -> IGTPW_3492 * Piglit: piglit_4509 -> None CI-20190529: 20190529 CI_DRM_6944: 2c9a75480b3c8a78ed86404c8c0afea389622df6 @ git://anongit.freedesktop.org/gfx-ci/linux IGTPW_3492: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/ IGT_5197: aa534ff47fd2f455c8be9e59eae807695b87fcdd @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3492/ _______________________________________________ igt-dev mailing list igt-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/igt-dev ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps 2019-09-23 18:23 ` [Intel-gfx] " Bhawanpreet Lakha @ 2019-09-24 9:54 ` Petri Latvala -1 siblings, 0 replies; 22+ messages in thread From: Petri Latvala @ 2019-09-24 9:54 UTC (permalink / raw) To: Bhawanpreet Lakha, Ramalingam C; +Cc: igt-dev, intel-gfx On Mon, Sep 23, 2019 at 02:23:25PM -0400, Bhawanpreet Lakha wrote: > Rename "i915_hdcp_sink_capability" to "hdcp_sink_capability" > > The content protection tests only start if this debugfs entry exists. > Since the name is specific to intel driver these tests cannot be used with > other drivers. > > Remove "i915" so the debugfs name is generic. I don't see any drivers currently using the name "hdcp_sink_capability". Is the content of the file in other drivers the same as i915's? And is there a plan to rename i915's debugfs filename to hdcp_sink_capability? Ram? Agreed, for a DRIVER_ANY-using test generic names are preferrable, but this needs some kind of a transition plan. If i915's filename is staying as is, both names need to be tried. -- Petri Latvala _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps @ 2019-09-24 9:54 ` Petri Latvala 0 siblings, 0 replies; 22+ messages in thread From: Petri Latvala @ 2019-09-24 9:54 UTC (permalink / raw) To: Bhawanpreet Lakha, Ramalingam C; +Cc: igt-dev, intel-gfx On Mon, Sep 23, 2019 at 02:23:25PM -0400, Bhawanpreet Lakha wrote: > Rename "i915_hdcp_sink_capability" to "hdcp_sink_capability" > > The content protection tests only start if this debugfs entry exists. > Since the name is specific to intel driver these tests cannot be used with > other drivers. > > Remove "i915" so the debugfs name is generic. I don't see any drivers currently using the name "hdcp_sink_capability". Is the content of the file in other drivers the same as i915's? And is there a plan to rename i915's debugfs filename to hdcp_sink_capability? Ram? Agreed, for a DRIVER_ANY-using test generic names are preferrable, but this needs some kind of a transition plan. If i915's filename is staying as is, both names need to be tried. -- Petri Latvala _______________________________________________ igt-dev mailing list igt-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/igt-dev ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps 2019-09-24 9:54 ` Petri Latvala @ 2019-09-24 14:41 ` Lakha, Bhawanpreet -1 siblings, 0 replies; 22+ messages in thread From: Lakha, Bhawanpreet @ 2019-09-24 14:41 UTC (permalink / raw) To: Ramalingam C; +Cc: igt-dev, intel-gfx We have used the tests for our hdcp implementation. But because of the name we can't use it as is. Bhawan On 2019-09-24 5:54 a.m., Petri Latvala wrote: > On Mon, Sep 23, 2019 at 02:23:25PM -0400, Bhawanpreet Lakha wrote: >> Rename "i915_hdcp_sink_capability" to "hdcp_sink_capability" >> >> The content protection tests only start if this debugfs entry exists. >> Since the name is specific to intel driver these tests cannot be used with >> other drivers. >> >> Remove "i915" so the debugfs name is generic. > I don't see any drivers currently using the name > "hdcp_sink_capability". Is the content of the file in other drivers > the same as i915's? > > And is there a plan to rename i915's debugfs filename to > hdcp_sink_capability? Ram? > > Agreed, for a DRIVER_ANY-using test generic names are preferrable, but > this needs some kind of a transition plan. If i915's filename is > staying as is, both names need to be tried. > > _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps @ 2019-09-24 14:41 ` Lakha, Bhawanpreet 0 siblings, 0 replies; 22+ messages in thread From: Lakha, Bhawanpreet @ 2019-09-24 14:41 UTC (permalink / raw) To: Ramalingam C; +Cc: igt-dev, intel-gfx We have used the tests for our hdcp implementation. But because of the name we can't use it as is. Bhawan On 2019-09-24 5:54 a.m., Petri Latvala wrote: > On Mon, Sep 23, 2019 at 02:23:25PM -0400, Bhawanpreet Lakha wrote: >> Rename "i915_hdcp_sink_capability" to "hdcp_sink_capability" >> >> The content protection tests only start if this debugfs entry exists. >> Since the name is specific to intel driver these tests cannot be used with >> other drivers. >> >> Remove "i915" so the debugfs name is generic. > I don't see any drivers currently using the name > "hdcp_sink_capability". Is the content of the file in other drivers > the same as i915's? > > And is there a plan to rename i915's debugfs filename to > hdcp_sink_capability? Ram? > > Agreed, for a DRIVER_ANY-using test generic names are preferrable, but > this needs some kind of a transition plan. If i915's filename is > staying as is, both names need to be tried. > > _______________________________________________ igt-dev mailing list igt-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/igt-dev ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps 2019-09-24 9:54 ` Petri Latvala @ 2019-09-24 15:41 ` Ramalingam C -1 siblings, 0 replies; 22+ messages in thread From: Ramalingam C @ 2019-09-24 15:41 UTC (permalink / raw) To: Bhawanpreet Lakha, igt-dev, intel-gfx, Daniel Vetter On 2019-09-24 at 12:54:54 +0300, Petri Latvala wrote: > On Mon, Sep 23, 2019 at 02:23:25PM -0400, Bhawanpreet Lakha wrote: > > Rename "i915_hdcp_sink_capability" to "hdcp_sink_capability" > > > > The content protection tests only start if this debugfs entry exists. > > Since the name is specific to intel driver these tests cannot be used with > > other drivers. > > > > Remove "i915" so the debugfs name is generic. > > I don't see any drivers currently using the name > "hdcp_sink_capability". Is the content of the file in other drivers > the same as i915's? > > And is there a plan to rename i915's debugfs filename to > hdcp_sink_capability? Ram? > > Agreed, for a DRIVER_ANY-using test generic names are preferrable, but > this needs some kind of a transition plan. If i915's filename is > staying as is, both names need to be tried. This IGT test change has to wait untill we have the i915_hdcp_sink_capabilities renamed, if at all we rename. Else based on drm_device we could decide the debugfs file and read it. Daniel, Considering all other debugfs are prefixed with i915, could we rename this debugfs as "hdcp_sink_capabilities" instead? -Ram > > > -- > Petri Latvala _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps @ 2019-09-24 15:41 ` Ramalingam C 0 siblings, 0 replies; 22+ messages in thread From: Ramalingam C @ 2019-09-24 15:41 UTC (permalink / raw) To: Bhawanpreet Lakha, igt-dev, intel-gfx, Daniel Vetter On 2019-09-24 at 12:54:54 +0300, Petri Latvala wrote: > On Mon, Sep 23, 2019 at 02:23:25PM -0400, Bhawanpreet Lakha wrote: > > Rename "i915_hdcp_sink_capability" to "hdcp_sink_capability" > > > > The content protection tests only start if this debugfs entry exists. > > Since the name is specific to intel driver these tests cannot be used with > > other drivers. > > > > Remove "i915" so the debugfs name is generic. > > I don't see any drivers currently using the name > "hdcp_sink_capability". Is the content of the file in other drivers > the same as i915's? > > And is there a plan to rename i915's debugfs filename to > hdcp_sink_capability? Ram? > > Agreed, for a DRIVER_ANY-using test generic names are preferrable, but > this needs some kind of a transition plan. If i915's filename is > staying as is, both names need to be tried. This IGT test change has to wait untill we have the i915_hdcp_sink_capabilities renamed, if at all we rename. Else based on drm_device we could decide the debugfs file and read it. Daniel, Considering all other debugfs are prefixed with i915, could we rename this debugfs as "hdcp_sink_capabilities" instead? -Ram > > > -- > Petri Latvala _______________________________________________ igt-dev mailing list igt-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/igt-dev ^ permalink raw reply [flat|nested] 22+ messages in thread
* [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps 2019-09-23 18:23 ` [Intel-gfx] " Bhawanpreet Lakha ` (3 preceding siblings ...) (?) @ 2019-10-21 19:42 ` Bhawanpreet Lakha 2019-10-23 14:18 ` [Intel-gfx] " Harry Wentland ` (2 more replies) -1 siblings, 3 replies; 22+ messages in thread From: Bhawanpreet Lakha @ 2019-10-21 19:42 UTC (permalink / raw) To: igt-dev; +Cc: Bhawanpreet Lakha, intel-gfx, harry.wentland The content protection tests only start if this debugfs entry exists. Since the name is specific to intel driver these tests cannot be used with other drivers. So we should check generic debugfs name also v2: Check i915_* if device is i915, otherwise check the generic name. Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> --- tests/kms_content_protection.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c index e676b60b..42fdc459 100644 --- a/tests/kms_content_protection.c +++ b/tests/kms_content_protection.c @@ -554,7 +554,11 @@ static bool sink_hdcp_capable(igt_output_t *output) if (fd < 0) return false; - debugfs_read(fd, "i915_hdcp_sink_capability", buf); + if (is_i915_device(data.drm_fd)) + debugfs_read(fd, "i915_hdcp_sink_capability", buf); + else + debugfs_read(fd, "hdcp_sink_capability", buf); + close(fd); igt_debug("Sink capability: %s\n", buf); @@ -571,7 +575,11 @@ static bool sink_hdcp2_capable(igt_output_t *output) if (fd < 0) return false; - debugfs_read(fd, "i915_hdcp_sink_capability", buf); + if (is_i915_device(data.drm_fd)) + debugfs_read(fd, "i915_hdcp_sink_capability", buf); + else + debugfs_read(fd, "hdcp_sink_capability", buf); + close(fd); igt_debug("Sink capability: %s\n", buf); -- 2.17.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 22+ messages in thread
* Re: [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps @ 2019-10-23 14:18 ` Harry Wentland 0 siblings, 0 replies; 22+ messages in thread From: Harry Wentland @ 2019-10-23 14:18 UTC (permalink / raw) To: Lakha, Bhawanpreet, igt-dev; +Cc: intel-gfx, Wentland, Harry On 2019-10-21 3:42 p.m., Bhawanpreet Lakha wrote: > The content protection tests only start if this debugfs entry exists. > Since the name is specific to intel driver these tests cannot be used with > other drivers. So we should check generic debugfs name also > > v2: Check i915_* if device is i915, otherwise check the generic name. > > Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Reviewed-by: Harry Wentland <harry.wentland@amd.com> Harry > --- > tests/kms_content_protection.c | 12 ++++++++++-- > 1 file changed, 10 insertions(+), 2 deletions(-) > > diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c > index e676b60b..42fdc459 100644 > --- a/tests/kms_content_protection.c > +++ b/tests/kms_content_protection.c > @@ -554,7 +554,11 @@ static bool sink_hdcp_capable(igt_output_t *output) > if (fd < 0) > return false; > > - debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + if (is_i915_device(data.drm_fd)) > + debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + else > + debugfs_read(fd, "hdcp_sink_capability", buf); > + > close(fd); > > igt_debug("Sink capability: %s\n", buf); > @@ -571,7 +575,11 @@ static bool sink_hdcp2_capable(igt_output_t *output) > if (fd < 0) > return false; > > - debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + if (is_i915_device(data.drm_fd)) > + debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + else > + debugfs_read(fd, "hdcp_sink_capability", buf); > + > close(fd); > > igt_debug("Sink capability: %s\n", buf); > _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps @ 2019-10-23 14:18 ` Harry Wentland 0 siblings, 0 replies; 22+ messages in thread From: Harry Wentland @ 2019-10-23 14:18 UTC (permalink / raw) To: Lakha, Bhawanpreet, igt-dev; +Cc: intel-gfx On 2019-10-21 3:42 p.m., Bhawanpreet Lakha wrote: > The content protection tests only start if this debugfs entry exists. > Since the name is specific to intel driver these tests cannot be used with > other drivers. So we should check generic debugfs name also > > v2: Check i915_* if device is i915, otherwise check the generic name. > > Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Reviewed-by: Harry Wentland <harry.wentland@amd.com> Harry > --- > tests/kms_content_protection.c | 12 ++++++++++-- > 1 file changed, 10 insertions(+), 2 deletions(-) > > diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c > index e676b60b..42fdc459 100644 > --- a/tests/kms_content_protection.c > +++ b/tests/kms_content_protection.c > @@ -554,7 +554,11 @@ static bool sink_hdcp_capable(igt_output_t *output) > if (fd < 0) > return false; > > - debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + if (is_i915_device(data.drm_fd)) > + debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + else > + debugfs_read(fd, "hdcp_sink_capability", buf); > + > close(fd); > > igt_debug("Sink capability: %s\n", buf); > @@ -571,7 +575,11 @@ static bool sink_hdcp2_capable(igt_output_t *output) > if (fd < 0) > return false; > > - debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + if (is_i915_device(data.drm_fd)) > + debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + else > + debugfs_read(fd, "hdcp_sink_capability", buf); > + > close(fd); > > igt_debug("Sink capability: %s\n", buf); > _______________________________________________ igt-dev mailing list igt-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/igt-dev ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps @ 2019-10-23 14:18 ` Harry Wentland 0 siblings, 0 replies; 22+ messages in thread From: Harry Wentland @ 2019-10-23 14:18 UTC (permalink / raw) To: Lakha, Bhawanpreet, igt-dev; +Cc: intel-gfx, Wentland, Harry On 2019-10-21 3:42 p.m., Bhawanpreet Lakha wrote: > The content protection tests only start if this debugfs entry exists. > Since the name is specific to intel driver these tests cannot be used with > other drivers. So we should check generic debugfs name also > > v2: Check i915_* if device is i915, otherwise check the generic name. > > Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Reviewed-by: Harry Wentland <harry.wentland@amd.com> Harry > --- > tests/kms_content_protection.c | 12 ++++++++++-- > 1 file changed, 10 insertions(+), 2 deletions(-) > > diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c > index e676b60b..42fdc459 100644 > --- a/tests/kms_content_protection.c > +++ b/tests/kms_content_protection.c > @@ -554,7 +554,11 @@ static bool sink_hdcp_capable(igt_output_t *output) > if (fd < 0) > return false; > > - debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + if (is_i915_device(data.drm_fd)) > + debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + else > + debugfs_read(fd, "hdcp_sink_capability", buf); > + > close(fd); > > igt_debug("Sink capability: %s\n", buf); > @@ -571,7 +575,11 @@ static bool sink_hdcp2_capable(igt_output_t *output) > if (fd < 0) > return false; > > - debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + if (is_i915_device(data.drm_fd)) > + debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + else > + debugfs_read(fd, "hdcp_sink_capability", buf); > + > close(fd); > > igt_debug("Sink capability: %s\n", buf); > _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps @ 2019-10-23 15:27 ` Ramalingam C 0 siblings, 0 replies; 22+ messages in thread From: Ramalingam C @ 2019-10-23 15:27 UTC (permalink / raw) To: Bhawanpreet Lakha; +Cc: igt-dev, intel-gfx, harry.wentland On 2019-10-21 at 15:42:59 -0400, Bhawanpreet Lakha wrote: > The content protection tests only start if this debugfs entry exists. > Since the name is specific to intel driver these tests cannot be used with > other drivers. So we should check generic debugfs name also > > v2: Check i915_* if device is i915, otherwise check the generic name. > > Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Looks good to me. Reviewed-by: Ramalingam C <ramalingam.c@intel.com> > --- > tests/kms_content_protection.c | 12 ++++++++++-- > 1 file changed, 10 insertions(+), 2 deletions(-) > > diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c > index e676b60b..42fdc459 100644 > --- a/tests/kms_content_protection.c > +++ b/tests/kms_content_protection.c > @@ -554,7 +554,11 @@ static bool sink_hdcp_capable(igt_output_t *output) > if (fd < 0) > return false; > > - debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + if (is_i915_device(data.drm_fd)) > + debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + else > + debugfs_read(fd, "hdcp_sink_capability", buf); > + > close(fd); > > igt_debug("Sink capability: %s\n", buf); > @@ -571,7 +575,11 @@ static bool sink_hdcp2_capable(igt_output_t *output) > if (fd < 0) > return false; > > - debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + if (is_i915_device(data.drm_fd)) > + debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + else > + debugfs_read(fd, "hdcp_sink_capability", buf); > + > close(fd); > > igt_debug("Sink capability: %s\n", buf); > -- > 2.17.1 > > _______________________________________________ > 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 ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [Intel-gfx] [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps @ 2019-10-23 15:27 ` Ramalingam C 0 siblings, 0 replies; 22+ messages in thread From: Ramalingam C @ 2019-10-23 15:27 UTC (permalink / raw) To: Bhawanpreet Lakha; +Cc: igt-dev, intel-gfx On 2019-10-21 at 15:42:59 -0400, Bhawanpreet Lakha wrote: > The content protection tests only start if this debugfs entry exists. > Since the name is specific to intel driver these tests cannot be used with > other drivers. So we should check generic debugfs name also > > v2: Check i915_* if device is i915, otherwise check the generic name. > > Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Looks good to me. Reviewed-by: Ramalingam C <ramalingam.c@intel.com> > --- > tests/kms_content_protection.c | 12 ++++++++++-- > 1 file changed, 10 insertions(+), 2 deletions(-) > > diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c > index e676b60b..42fdc459 100644 > --- a/tests/kms_content_protection.c > +++ b/tests/kms_content_protection.c > @@ -554,7 +554,11 @@ static bool sink_hdcp_capable(igt_output_t *output) > if (fd < 0) > return false; > > - debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + if (is_i915_device(data.drm_fd)) > + debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + else > + debugfs_read(fd, "hdcp_sink_capability", buf); > + > close(fd); > > igt_debug("Sink capability: %s\n", buf); > @@ -571,7 +575,11 @@ static bool sink_hdcp2_capable(igt_output_t *output) > if (fd < 0) > return false; > > - debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + if (is_i915_device(data.drm_fd)) > + debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + else > + debugfs_read(fd, "hdcp_sink_capability", buf); > + > close(fd); > > igt_debug("Sink capability: %s\n", buf); > -- > 2.17.1 > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx _______________________________________________ igt-dev mailing list igt-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/igt-dev ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps @ 2019-10-23 15:27 ` Ramalingam C 0 siblings, 0 replies; 22+ messages in thread From: Ramalingam C @ 2019-10-23 15:27 UTC (permalink / raw) To: Bhawanpreet Lakha; +Cc: igt-dev, intel-gfx, harry.wentland On 2019-10-21 at 15:42:59 -0400, Bhawanpreet Lakha wrote: > The content protection tests only start if this debugfs entry exists. > Since the name is specific to intel driver these tests cannot be used with > other drivers. So we should check generic debugfs name also > > v2: Check i915_* if device is i915, otherwise check the generic name. > > Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Looks good to me. Reviewed-by: Ramalingam C <ramalingam.c@intel.com> > --- > tests/kms_content_protection.c | 12 ++++++++++-- > 1 file changed, 10 insertions(+), 2 deletions(-) > > diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c > index e676b60b..42fdc459 100644 > --- a/tests/kms_content_protection.c > +++ b/tests/kms_content_protection.c > @@ -554,7 +554,11 @@ static bool sink_hdcp_capable(igt_output_t *output) > if (fd < 0) > return false; > > - debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + if (is_i915_device(data.drm_fd)) > + debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + else > + debugfs_read(fd, "hdcp_sink_capability", buf); > + > close(fd); > > igt_debug("Sink capability: %s\n", buf); > @@ -571,7 +575,11 @@ static bool sink_hdcp2_capable(igt_output_t *output) > if (fd < 0) > return false; > > - debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + if (is_i915_device(data.drm_fd)) > + debugfs_read(fd, "i915_hdcp_sink_capability", buf); > + else > + debugfs_read(fd, "hdcp_sink_capability", buf); > + > close(fd); > > igt_debug("Sink capability: %s\n", buf); > -- > 2.17.1 > > _______________________________________________ > 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 ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps @ 2019-10-24 11:17 ` Petri Latvala 0 siblings, 0 replies; 22+ messages in thread From: Petri Latvala @ 2019-10-24 11:17 UTC (permalink / raw) To: Bhawanpreet Lakha; +Cc: igt-dev, intel-gfx, harry.wentland On Mon, Oct 21, 2019 at 03:42:59PM -0400, Bhawanpreet Lakha wrote: > The content protection tests only start if this debugfs entry exists. > Since the name is specific to intel driver these tests cannot be used with > other drivers. So we should check generic debugfs name also > > v2: Check i915_* if device is i915, otherwise check the generic name. > > Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Merged, thanks for the patch and reviews! -- Petri Latvala _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [Intel-gfx] [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps @ 2019-10-24 11:17 ` Petri Latvala 0 siblings, 0 replies; 22+ messages in thread From: Petri Latvala @ 2019-10-24 11:17 UTC (permalink / raw) To: Bhawanpreet Lakha; +Cc: igt-dev, intel-gfx On Mon, Oct 21, 2019 at 03:42:59PM -0400, Bhawanpreet Lakha wrote: > The content protection tests only start if this debugfs entry exists. > Since the name is specific to intel driver these tests cannot be used with > other drivers. So we should check generic debugfs name also > > v2: Check i915_* if device is i915, otherwise check the generic name. > > Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Merged, thanks for the patch and reviews! -- Petri Latvala _______________________________________________ igt-dev mailing list igt-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/igt-dev ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps @ 2019-10-24 11:17 ` Petri Latvala 0 siblings, 0 replies; 22+ messages in thread From: Petri Latvala @ 2019-10-24 11:17 UTC (permalink / raw) To: Bhawanpreet Lakha; +Cc: igt-dev, intel-gfx, harry.wentland On Mon, Oct 21, 2019 at 03:42:59PM -0400, Bhawanpreet Lakha wrote: > The content protection tests only start if this debugfs entry exists. > Since the name is specific to intel driver these tests cannot be used with > other drivers. So we should check generic debugfs name also > > v2: Check i915_* if device is i915, otherwise check the generic name. > > Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Merged, thanks for the patch and reviews! -- Petri Latvala _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 22+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for test/kms_content_protection: Use generic debugfs name for HDCP caps (rev2) 2019-09-23 18:23 ` [Intel-gfx] " Bhawanpreet Lakha ` (4 preceding siblings ...) (?) @ 2019-10-21 21:28 ` Patchwork -1 siblings, 0 replies; 22+ messages in thread From: Patchwork @ 2019-10-21 21:28 UTC (permalink / raw) To: Bhawanpreet Lakha; +Cc: igt-dev == Series Details == Series: test/kms_content_protection: Use generic debugfs name for HDCP caps (rev2) URL : https://patchwork.freedesktop.org/series/67125/ State : success == Summary == CI Bug Log - changes from CI_DRM_7144 -> IGTPW_3592 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/index.html Possible new issues ------------------- Here are the unknown changes that may have been introduced in IGTPW_3592: ### IGT changes ### #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * {igt@i915_selftest@live_gt_heartbeat}: - fi-cml-u2: [PASS][1] -> [DMESG-FAIL][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/fi-cml-u2/igt@i915_selftest@live_gt_heartbeat.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/fi-cml-u2/igt@i915_selftest@live_gt_heartbeat.html Known issues ------------ Here are the changes found in IGTPW_3592 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_mmap_gtt@basic-small-bo-tiledx: - fi-icl-u3: [PASS][3] -> [DMESG-WARN][4] ([fdo#107724]) +2 similar issues [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/fi-icl-u3/igt@gem_mmap_gtt@basic-small-bo-tiledx.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/fi-icl-u3/igt@gem_mmap_gtt@basic-small-bo-tiledx.html * igt@i915_selftest@live_gem_contexts: - fi-cfl-8109u: [PASS][5] -> [DMESG-FAIL][6] ([fdo#112050 ]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/fi-cfl-8109u/igt@i915_selftest@live_gem_contexts.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/fi-cfl-8109u/igt@i915_selftest@live_gem_contexts.html #### Possible fixes #### * igt@gem_mmap@basic: - fi-icl-u3: [DMESG-WARN][7] ([fdo#107724]) -> [PASS][8] +1 similar issue [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/fi-icl-u3/igt@gem_mmap@basic.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/fi-icl-u3/igt@gem_mmap@basic.html * {igt@i915_selftest@live_gt_heartbeat}: - fi-cml-u: [DMESG-FAIL][9] -> [PASS][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/fi-cml-u/igt@i915_selftest@live_gt_heartbeat.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/fi-cml-u/igt@i915_selftest@live_gt_heartbeat.html * igt@i915_selftest@live_hangcheck: - {fi-icl-dsi}: [INCOMPLETE][11] ([fdo#107713] / [fdo#108569]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/fi-icl-dsi/igt@i915_selftest@live_hangcheck.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/fi-icl-dsi/igt@i915_selftest@live_hangcheck.html #### Warnings #### * igt@kms_chamelium@hdmi-hpd-fast: - fi-kbl-7500u: [FAIL][13] ([fdo#111407]) -> [FAIL][14] ([fdo#111045] / [fdo#111096]) [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724 [fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569 [fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045 [fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096 [fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407 [fdo#111600]: https://bugs.freedesktop.org/show_bug.cgi?id=111600 [fdo#111831]: https://bugs.freedesktop.org/show_bug.cgi?id=111831 [fdo#112050 ]: https://bugs.freedesktop.org/show_bug.cgi?id=112050 Participating hosts (52 -> 44) ------------------------------ Additional (1): fi-kbl-soraka Missing (9): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-icl-u2 fi-bsw-cyan fi-icl-y fi-icl-guc fi-byt-clapper fi-bdw-samus Build changes ------------- * CI: CI-20190529 -> None * IGT: IGT_5235 -> IGTPW_3592 CI-20190529: 20190529 CI_DRM_7144: 5a109994e39e3c50909199ed6e970219155b5471 @ git://anongit.freedesktop.org/gfx-ci/linux IGTPW_3592: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/index.html IGT_5235: da9abbab69be80dd00812a4607a4ea2dffcc4544 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/index.html _______________________________________________ igt-dev mailing list igt-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/igt-dev ^ permalink raw reply [flat|nested] 22+ messages in thread
* [igt-dev] ✓ Fi.CI.IGT: success for test/kms_content_protection: Use generic debugfs name for HDCP caps (rev2) 2019-09-23 18:23 ` [Intel-gfx] " Bhawanpreet Lakha ` (5 preceding siblings ...) (?) @ 2019-10-22 5:42 ` Patchwork -1 siblings, 0 replies; 22+ messages in thread From: Patchwork @ 2019-10-22 5:42 UTC (permalink / raw) To: Bhawanpreet Lakha; +Cc: igt-dev == Series Details == Series: test/kms_content_protection: Use generic debugfs name for HDCP caps (rev2) URL : https://patchwork.freedesktop.org/series/67125/ State : success == Summary == CI Bug Log - changes from CI_DRM_7144_full -> IGTPW_3592_full ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/index.html Possible new issues ------------------- Here are the unknown changes that may have been introduced in IGTPW_3592_full: ### IGT changes ### #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * igt@gem_exec_schedule@preempt-hang-vebox: - {shard-tglb}: NOTRUN -> [INCOMPLETE][1] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-tglb6/igt@gem_exec_schedule@preempt-hang-vebox.html * igt@gem_pwrite@big-cpu-random: - {shard-tglb}: [PASS][2] -> [INCOMPLETE][3] [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-tglb5/igt@gem_pwrite@big-cpu-random.html [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-tglb7/igt@gem_pwrite@big-cpu-random.html Known issues ------------ Here are the changes found in IGTPW_3592_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_ctx_isolation@vcs1-clean: - shard-iclb: [PASS][4] -> [SKIP][5] ([fdo#109276] / [fdo#112080]) [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb1/igt@gem_ctx_isolation@vcs1-clean.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb5/igt@gem_ctx_isolation@vcs1-clean.html * igt@gem_eio@reset-stress: - shard-snb: [PASS][6] -> [FAIL][7] ([fdo#109661]) [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-snb5/igt@gem_eio@reset-stress.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-snb2/igt@gem_eio@reset-stress.html * igt@gem_exec_parallel@vcs1-fds: - shard-iclb: [PASS][8] -> [SKIP][9] ([fdo#112080]) +12 similar issues [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb1/igt@gem_exec_parallel@vcs1-fds.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb7/igt@gem_exec_parallel@vcs1-fds.html * igt@gem_exec_schedule@preempt-other-chain-bsd: - shard-iclb: [PASS][10] -> [SKIP][11] ([fdo#111325]) +4 similar issues [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb7/igt@gem_exec_schedule@preempt-other-chain-bsd.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb1/igt@gem_exec_schedule@preempt-other-chain-bsd.html * igt@gem_exec_schedule@preempt-queue-bsd1: - shard-iclb: [PASS][12] -> [SKIP][13] ([fdo#109276]) +13 similar issues [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb2/igt@gem_exec_schedule@preempt-queue-bsd1.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb7/igt@gem_exec_schedule@preempt-queue-bsd1.html * igt@gem_exec_whisper@normal: - shard-hsw: [PASS][14] -> [INCOMPLETE][15] ([fdo#103540]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-hsw4/igt@gem_exec_whisper@normal.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-hsw1/igt@gem_exec_whisper@normal.html * igt@gem_linear_blits@normal: - shard-apl: [PASS][16] -> [INCOMPLETE][17] ([fdo#103927]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-apl8/igt@gem_linear_blits@normal.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-apl4/igt@gem_linear_blits@normal.html * igt@gem_tiled_blits@interruptible: - shard-apl: [PASS][18] -> [DMESG-WARN][19] ([fdo#109385]) [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-apl2/igt@gem_tiled_blits@interruptible.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-apl6/igt@gem_tiled_blits@interruptible.html * igt@gem_userptr_blits@sync-unmap-cycles: - shard-snb: [PASS][20] -> [DMESG-WARN][21] ([fdo#111870]) +3 similar issues [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-snb7/igt@gem_userptr_blits@sync-unmap-cycles.html [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-snb6/igt@gem_userptr_blits@sync-unmap-cycles.html * igt@kms_cursor_crc@pipe-b-cursor-64x64-rapid-movement: - shard-iclb: [PASS][22] -> [INCOMPLETE][23] ([fdo#107713]) [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb4/igt@kms_cursor_crc@pipe-b-cursor-64x64-rapid-movement.html [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb7/igt@kms_cursor_crc@pipe-b-cursor-64x64-rapid-movement.html * igt@kms_cursor_crc@pipe-c-cursor-suspend: - shard-apl: [PASS][24] -> [DMESG-WARN][25] ([fdo#108566]) +3 similar issues [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-apl8/igt@kms_cursor_crc@pipe-c-cursor-suspend.html [25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-apl6/igt@kms_cursor_crc@pipe-c-cursor-suspend.html * igt@kms_flip@flip-vs-suspend: - shard-snb: [PASS][26] -> [INCOMPLETE][27] ([fdo#105411]) [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-snb6/igt@kms_flip@flip-vs-suspend.html [27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-snb1/igt@kms_flip@flip-vs-suspend.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render: - shard-iclb: [PASS][28] -> [FAIL][29] ([fdo#103167]) [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render.html [29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render.html * igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-spr-indfb-draw-mmap-cpu: - shard-glk: [PASS][30] -> [FAIL][31] ([fdo#103167]) [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-glk8/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-spr-indfb-draw-mmap-cpu.html [31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-glk3/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-spr-indfb-draw-mmap-cpu.html * igt@kms_psr@psr2_cursor_plane_move: - shard-iclb: [PASS][32] -> [SKIP][33] ([fdo#109441]) +1 similar issue [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html [33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb3/igt@kms_psr@psr2_cursor_plane_move.html * igt@kms_setmode@basic: - shard-apl: [PASS][34] -> [FAIL][35] ([fdo#99912]) [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-apl3/igt@kms_setmode@basic.html [35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-apl3/igt@kms_setmode@basic.html #### Possible fixes #### * igt@gem_ctx_exec@basic-invalid-context-vcs1: - shard-iclb: [SKIP][36] ([fdo#112080]) -> [PASS][37] +8 similar issues [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb3/igt@gem_ctx_exec@basic-invalid-context-vcs1.html [37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb1/igt@gem_ctx_exec@basic-invalid-context-vcs1.html * igt@gem_ctx_isolation@vcs1-none: - shard-iclb: [SKIP][38] ([fdo#109276] / [fdo#112080]) -> [PASS][39] +1 similar issue [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb8/igt@gem_ctx_isolation@vcs1-none.html [39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb2/igt@gem_ctx_isolation@vcs1-none.html * igt@gem_eio@in-flight-contexts-immediate: - shard-snb: [FAIL][40] ([fdo#111925]) -> [PASS][41] [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-snb2/igt@gem_eio@in-flight-contexts-immediate.html [41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-snb6/igt@gem_eio@in-flight-contexts-immediate.html * igt@gem_exec_schedule@reorder-wide-bsd: - shard-iclb: [SKIP][42] ([fdo#111325]) -> [PASS][43] +4 similar issues [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb1/igt@gem_exec_schedule@reorder-wide-bsd.html [43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb5/igt@gem_exec_schedule@reorder-wide-bsd.html * igt@gem_userptr_blits@dmabuf-sync: - shard-snb: [DMESG-WARN][44] ([fdo#111870]) -> [PASS][45] +1 similar issue [44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-snb2/igt@gem_userptr_blits@dmabuf-sync.html [45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-snb7/igt@gem_userptr_blits@dmabuf-sync.html * igt@gem_userptr_blits@sync-unmap-after-close: - shard-hsw: [DMESG-WARN][46] ([fdo#111870]) -> [PASS][47] +2 similar issues [46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-hsw7/igt@gem_userptr_blits@sync-unmap-after-close.html [47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-hsw7/igt@gem_userptr_blits@sync-unmap-after-close.html * igt@gem_workarounds@suspend-resume-context: - {shard-tglb}: [INCOMPLETE][48] ([fdo#111832] / [fdo#111850]) -> [PASS][49] +1 similar issue [48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-tglb4/igt@gem_workarounds@suspend-resume-context.html [49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-tglb3/igt@gem_workarounds@suspend-resume-context.html * {igt@i915_pm_dc@dc6-dpms}: - shard-iclb: [FAIL][50] ([fdo#110548]) -> [PASS][51] [50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb4/igt@i915_pm_dc@dc6-dpms.html [51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb6/igt@i915_pm_dc@dc6-dpms.html * igt@i915_pm_rpm@modeset-stress-extra-wait: - shard-glk: [DMESG-WARN][52] ([fdo#105763] / [fdo#106538]) -> [PASS][53] [52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-glk8/igt@i915_pm_rpm@modeset-stress-extra-wait.html [53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-glk8/igt@i915_pm_rpm@modeset-stress-extra-wait.html * igt@kms_cursor_crc@pipe-b-cursor-64x21-sliding: - shard-iclb: [INCOMPLETE][54] ([fdo#107713]) -> [PASS][55] [54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb1/igt@kms_cursor_crc@pipe-b-cursor-64x21-sliding.html [55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb6/igt@kms_cursor_crc@pipe-b-cursor-64x21-sliding.html * igt@kms_cursor_legacy@cursor-vs-flip-atomic: - shard-apl: [INCOMPLETE][56] ([fdo#103927]) -> [PASS][57] +1 similar issue [56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-apl6/igt@kms_cursor_legacy@cursor-vs-flip-atomic.html [57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-apl3/igt@kms_cursor_legacy@cursor-vs-flip-atomic.html * igt@kms_draw_crc@draw-method-xrgb8888-mmap-cpu-xtiled: - shard-snb: [SKIP][58] ([fdo#109271]) -> [PASS][59] +2 similar issues [58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-snb2/igt@kms_draw_crc@draw-method-xrgb8888-mmap-cpu-xtiled.html [59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-snb6/igt@kms_draw_crc@draw-method-xrgb8888-mmap-cpu-xtiled.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move: - {shard-tglb}: [FAIL][60] ([fdo#103167]) -> [PASS][61] +6 similar issues [60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move.html [61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-tglb4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt: - shard-iclb: [FAIL][62] ([fdo#103167]) -> [PASS][63] +4 similar issues [62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt.html [63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt.html * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a: - shard-iclb: [DMESG-WARN][64] ([fdo#111764]) -> [PASS][65] [64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb1/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html [65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb3/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c: - shard-apl: [DMESG-WARN][66] ([fdo#108566]) -> [PASS][67] +4 similar issues [66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-apl3/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html [67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-apl6/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html * igt@kms_psr@psr2_sprite_mmap_gtt: - shard-iclb: [SKIP][68] ([fdo#109441]) -> [PASS][69] +1 similar issue [68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb5/igt@kms_psr@psr2_sprite_mmap_gtt.html [69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html * igt@kms_vblank@pipe-d-ts-continuation-suspend: - {shard-tglb}: [INCOMPLETE][70] ([fdo#111850]) -> [PASS][71] [70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-tglb1/igt@kms_vblank@pipe-d-ts-continuation-suspend.html [71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-tglb3/igt@kms_vblank@pipe-d-ts-continuation-suspend.html * igt@prime_busy@hang-bsd2: - shard-iclb: [SKIP][72] ([fdo#109276]) -> [PASS][73] +10 similar issues [72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb5/igt@prime_busy@hang-bsd2.html [73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb2/igt@prime_busy@hang-bsd2.html #### Warnings #### * igt@gem_mocs_settings@mocs-settings-bsd2: - shard-iclb: [FAIL][74] ([fdo#111330]) -> [SKIP][75] ([fdo#109276]) [74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/shard-iclb4/igt@gem_mocs_settings@mocs-settings-bsd2.html [75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/shard-iclb3/igt@gem_mocs_settings@mocs-settings-bsd2.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167 [fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540 [fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927 [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#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566 [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276 [fdo#109385]: https://bugs.freedesktop.org/show_bug.cgi?id=109385 [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441 [fdo#109661]: https://bugs.freedesktop.org/show_bug.cgi?id=109661 [fdo#110548]: https://bugs.freedesktop.org/show_bug.cgi?id=110548 [fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325 [fdo#111329]: https://bugs.freedesktop.org/show_bug.cgi?id=111329 [fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330 [fdo#111703]: https://bugs.freedesktop.org/show_bug.cgi?id=111703 [fdo#111735]: https://bugs.freedesktop.org/show_bug.cgi?id=111735 [fdo#111764]: https://bugs.freedesktop.org/show_bug.cgi?id=111764 [fdo#111832]: https://bugs.freedesktop.org/show_bug.cgi?id=111832 [fdo#111850]: https://bugs.freedesktop.org/show_bug.cgi?id=111850 [fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870 [fdo#111884]: https://bugs.freedesktop.org/show_bug.cgi?id=111884 [fdo#111925]: https://bugs.freedesktop.org/show_bug.cgi?id=111925 [fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080 [fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912 Participating hosts (11 -> 8) ------------------------------ Missing (3): pig-skl-6260u pig-glk-j5005 pig-hsw-4770r Build changes ------------- * CI: CI-20190529 -> None * IGT: IGT_5235 -> IGTPW_3592 * Piglit: piglit_4509 -> None CI-20190529: 20190529 CI_DRM_7144: 5a109994e39e3c50909199ed6e970219155b5471 @ git://anongit.freedesktop.org/gfx-ci/linux IGTPW_3592: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/index.html IGT_5235: da9abbab69be80dd00812a4607a4ea2dffcc4544 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3592/index.html _______________________________________________ igt-dev mailing list igt-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/igt-dev ^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2019-10-24 11:17 UTC | newest] Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-09-23 18:23 [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps Bhawanpreet Lakha 2019-09-23 18:23 ` [Intel-gfx] " Bhawanpreet Lakha 2019-09-23 19:09 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork 2019-09-24 6:53 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork 2019-09-24 9:54 ` [igt-dev] [PATCH] " Petri Latvala 2019-09-24 9:54 ` Petri Latvala 2019-09-24 14:41 ` Lakha, Bhawanpreet 2019-09-24 14:41 ` Lakha, Bhawanpreet 2019-09-24 15:41 ` Ramalingam C 2019-09-24 15:41 ` Ramalingam C 2019-10-21 19:42 ` [PATCH i-g-t v2] tests/kms_content_protection: check i915 and " Bhawanpreet Lakha 2019-10-23 14:18 ` Harry Wentland 2019-10-23 14:18 ` [igt-dev] " Harry Wentland 2019-10-23 14:18 ` [Intel-gfx] " Harry Wentland 2019-10-23 15:27 ` Ramalingam C 2019-10-23 15:27 ` [igt-dev] [Intel-gfx] " Ramalingam C 2019-10-23 15:27 ` Ramalingam C 2019-10-24 11:17 ` Petri Latvala 2019-10-24 11:17 ` [igt-dev] [Intel-gfx] " Petri Latvala 2019-10-24 11:17 ` Petri Latvala 2019-10-21 21:28 ` [igt-dev] ✓ Fi.CI.BAT: success for test/kms_content_protection: Use generic debugfs name for HDCP caps (rev2) Patchwork 2019-10-22 5:42 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.