* [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_async_flips: Fix flip timestamp checks
2021-04-27 22:25 [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks Ville Syrjala
@ 2021-04-27 23:12 ` Patchwork
2021-04-28 2:37 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_async_flips: Fix flip timestamp checks (rev2) Patchwork
` (3 subsequent siblings)
4 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2021-04-27 23:12 UTC (permalink / raw)
To: Ville Syrjala; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 4139 bytes --]
== Series Details ==
Series: tests/kms_async_flips: Fix flip timestamp checks
URL : https://patchwork.freedesktop.org/series/89564/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10018 -> IGTPW_5766
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_5766 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_5766, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5766/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_5766:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@hugepages:
- fi-tgl-y: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10018/fi-tgl-y/igt@i915_selftest@live@hugepages.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5766/fi-tgl-y/igt@i915_selftest@live@hugepages.html
Known issues
------------
Here are the changes found in IGTPW_5766 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_parallel@engines@fds:
- fi-icl-u2: [PASS][3] -> [INCOMPLETE][4] ([i915#1895])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10018/fi-icl-u2/igt@gem_exec_parallel@engines@fds.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5766/fi-icl-u2/igt@gem_exec_parallel@engines@fds.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-kbl-7500u: [PASS][5] -> [DMESG-FAIL][6] ([i915#165])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10018/fi-kbl-7500u/igt@kms_chamelium@common-hpd-after-suspend.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5766/fi-kbl-7500u/igt@kms_chamelium@common-hpd-after-suspend.html
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s3:
- fi-tgl-u2: [FAIL][7] ([i915#1888]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10018/fi-tgl-u2/igt@gem_exec_suspend@basic-s3.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5766/fi-tgl-u2/igt@gem_exec_suspend@basic-s3.html
* igt@i915_selftest@live@gt_heartbeat:
- fi-tgl-y: [DMESG-FAIL][9] ([i915#541]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10018/fi-tgl-y/igt@i915_selftest@live@gt_heartbeat.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5766/fi-tgl-y/igt@i915_selftest@live@gt_heartbeat.html
- {fi-jsl-1}: [DMESG-WARN][11] ([i915#1222]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10018/fi-jsl-1/igt@i915_selftest@live@gt_heartbeat.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5766/fi-jsl-1/igt@i915_selftest@live@gt_heartbeat.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1222]: https://gitlab.freedesktop.org/drm/intel/issues/1222
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#1895]: https://gitlab.freedesktop.org/drm/intel/issues/1895
[i915#541]: https://gitlab.freedesktop.org/drm/intel/issues/541
Participating hosts (47 -> 40)
------------------------------
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-dg1-1 fi-icl-y fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_6076 -> IGTPW_5766
CI-20190529: 20190529
CI_DRM_10018: 929a4fa94d31990066fd8be6a02f1a6c2b9f1d2d @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5766: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5766/index.html
IGT_6076: 9ab0820dbd07781161c1ace6973ea222fd24e53a @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5766/index.html
[-- Attachment #1.2: Type: text/html, Size: 4895 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 8+ messages in thread* [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_async_flips: Fix flip timestamp checks (rev2)
2021-04-27 22:25 [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks Ville Syrjala
2021-04-27 23:12 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
@ 2021-04-28 2:37 ` Patchwork
2021-04-28 5:21 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
` (2 subsequent siblings)
4 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2021-04-28 2:37 UTC (permalink / raw)
To: Ville Syrjala; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 2624 bytes --]
== Series Details ==
Series: tests/kms_async_flips: Fix flip timestamp checks (rev2)
URL : https://patchwork.freedesktop.org/series/89564/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10019 -> IGTPW_5767
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/index.html
Known issues
------------
Here are the changes found in IGTPW_5767 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@runner@aborted:
- fi-tgl-y: NOTRUN -> [FAIL][1] ([i915#1436] / [i915#2966])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/fi-tgl-y/igt@runner@aborted.html
#### Possible fixes ####
* igt@kms_frontbuffer_tracking@basic:
- {fi-rkl-11500t}: [SKIP][2] ([i915#1849] / [i915#3180]) -> [PASS][3]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/fi-rkl-11500t/igt@kms_frontbuffer_tracking@basic.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/fi-rkl-11500t/igt@kms_frontbuffer_tracking@basic.html
#### Warnings ####
* igt@i915_selftest@live@gt_pm:
- fi-tgl-y: [DMESG-FAIL][4] ([i915#1759]) -> [INCOMPLETE][5] ([i915#1759])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/fi-tgl-y/igt@i915_selftest@live@gt_pm.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/fi-tgl-y/igt@i915_selftest@live@gt_pm.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1759]: https://gitlab.freedesktop.org/drm/intel/issues/1759
[i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849
[i915#2966]: https://gitlab.freedesktop.org/drm/intel/issues/2966
[i915#3180]: https://gitlab.freedesktop.org/drm/intel/issues/3180
Participating hosts (45 -> 40)
------------------------------
Missing (5): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-dg1-1 fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_6076 -> IGTPW_5767
CI-20190529: 20190529
CI_DRM_10019: acf28153df39c6dab44a8691ecaad05f1f37ed46 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5767: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/index.html
IGT_6076: 9ab0820dbd07781161c1ace6973ea222fd24e53a @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/index.html
[-- Attachment #1.2: Type: text/html, Size: 3328 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 8+ messages in thread* [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_async_flips: Fix flip timestamp checks (rev2)
2021-04-27 22:25 [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks Ville Syrjala
2021-04-27 23:12 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2021-04-28 2:37 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_async_flips: Fix flip timestamp checks (rev2) Patchwork
@ 2021-04-28 5:21 ` Patchwork
2021-04-28 14:38 ` [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks Juha-Pekka Heikkila
2021-04-29 5:37 ` Karthik B S
4 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2021-04-28 5:21 UTC (permalink / raw)
To: Ville Syrjala; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 30272 bytes --]
== Series Details ==
Series: tests/kms_async_flips: Fix flip timestamp checks (rev2)
URL : https://patchwork.freedesktop.org/series/89564/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10019_full -> IGTPW_5767_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_5767_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_5767_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://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_5767_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_big_fb@y-tiled-16bpp-rotate-90:
- shard-tglb: [PASS][1] -> [FAIL][2] +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-tglb5/igt@kms_big_fb@y-tiled-16bpp-rotate-90.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb7/igt@kms_big_fb@y-tiled-16bpp-rotate-90.html
Known issues
------------
Here are the changes found in IGTPW_5767_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_create@create-massive:
- shard-snb: NOTRUN -> [DMESG-WARN][3] ([i915#3002]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-snb5/igt@gem_create@create-massive.html
* igt@gem_ctx_persistence@clone:
- shard-snb: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#1099]) +6 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-snb5/igt@gem_ctx_persistence@clone.html
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [PASS][5] -> [FAIL][6] ([i915#2842])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-tglb7/igt@gem_exec_fair@basic-flow@rcs0.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb5/igt@gem_exec_fair@basic-flow@rcs0.html
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-kbl: [PASS][7] -> [FAIL][8] ([i915#2842]) +2 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl3/igt@gem_exec_fair@basic-none-share@rcs0.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl2/igt@gem_exec_fair@basic-none-share@rcs0.html
- shard-iclb: [PASS][9] -> [FAIL][10] ([i915#2842])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-iclb5/igt@gem_exec_fair@basic-none-share@rcs0.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb4/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_exec_fair@basic-none@vcs0:
- shard-glk: [PASS][11] -> [FAIL][12] ([i915#2842]) +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-glk1/igt@gem_exec_fair@basic-none@vcs0.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk2/igt@gem_exec_fair@basic-none@vcs0.html
* igt@gem_exec_fair@basic-pace@bcs0:
- shard-tglb: NOTRUN -> [FAIL][13] ([i915#2842]) +3 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb1/igt@gem_exec_fair@basic-pace@bcs0.html
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-iclb: NOTRUN -> [FAIL][14] ([i915#2842]) +1 similar issue
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb7/igt@gem_exec_fair@basic-pace@rcs0.html
* igt@gem_exec_fair@basic-pace@vcs0:
- shard-kbl: NOTRUN -> [FAIL][15] ([i915#2842])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl3/igt@gem_exec_fair@basic-pace@vcs0.html
* igt@gem_exec_fair@basic-sync@rcs0:
- shard-kbl: [PASS][16] -> [SKIP][17] ([fdo#109271])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl3/igt@gem_exec_fair@basic-sync@rcs0.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl4/igt@gem_exec_fair@basic-sync@rcs0.html
* igt@gem_exec_reloc@basic-wide-active@bcs0:
- shard-apl: NOTRUN -> [FAIL][18] ([i915#2389]) +3 similar issues
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl1/igt@gem_exec_reloc@basic-wide-active@bcs0.html
* igt@gem_pread@exhaustion:
- shard-snb: NOTRUN -> [WARN][19] ([i915#2658])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-snb5/igt@gem_pread@exhaustion.html
* igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled:
- shard-iclb: NOTRUN -> [SKIP][20] ([i915#768])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb4/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
* igt@gem_userptr_blits@dmabuf-sync:
- shard-apl: NOTRUN -> [SKIP][21] ([fdo#109271] / [i915#3323])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl7/igt@gem_userptr_blits@dmabuf-sync.html
* igt@gem_userptr_blits@dmabuf-unsync:
- shard-tglb: NOTRUN -> [SKIP][22] ([i915#3297]) +1 similar issue
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb3/igt@gem_userptr_blits@dmabuf-unsync.html
- shard-iclb: NOTRUN -> [SKIP][23] ([i915#3297]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb2/igt@gem_userptr_blits@dmabuf-unsync.html
* igt@gem_userptr_blits@input-checking:
- shard-apl: NOTRUN -> [DMESG-WARN][24] ([i915#3002]) +1 similar issue
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl2/igt@gem_userptr_blits@input-checking.html
* igt@gem_userptr_blits@set-cache-level:
- shard-kbl: NOTRUN -> [FAIL][25] ([i915#3324])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl3/igt@gem_userptr_blits@set-cache-level.html
- shard-tglb: NOTRUN -> [FAIL][26] ([i915#3324])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb6/igt@gem_userptr_blits@set-cache-level.html
- shard-apl: NOTRUN -> [FAIL][27] ([i915#3324])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl8/igt@gem_userptr_blits@set-cache-level.html
- shard-iclb: NOTRUN -> [FAIL][28] ([i915#3324])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb6/igt@gem_userptr_blits@set-cache-level.html
- shard-glk: NOTRUN -> [FAIL][29] ([i915#3324])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk8/igt@gem_userptr_blits@set-cache-level.html
* igt@gem_userptr_blits@vma-merge:
- shard-apl: NOTRUN -> [FAIL][30] ([i915#3318])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl3/igt@gem_userptr_blits@vma-merge.html
* igt@i915_pm_rpm@modeset-pc8-residency-stress:
- shard-apl: NOTRUN -> [SKIP][31] ([fdo#109271]) +207 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl8/igt@i915_pm_rpm@modeset-pc8-residency-stress.html
- shard-tglb: NOTRUN -> [SKIP][32] ([fdo#109506] / [i915#2411])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb8/igt@i915_pm_rpm@modeset-pc8-residency-stress.html
- shard-iclb: NOTRUN -> [SKIP][33] ([fdo#109293] / [fdo#109506])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb1/igt@i915_pm_rpm@modeset-pc8-residency-stress.html
* igt@i915_suspend@fence-restore-untiled:
- shard-apl: NOTRUN -> [DMESG-WARN][34] ([i915#180])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl1/igt@i915_suspend@fence-restore-untiled.html
* igt@kms_big_fb@linear-64bpp-rotate-90:
- shard-tglb: NOTRUN -> [SKIP][35] ([fdo#111614]) +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb7/igt@kms_big_fb@linear-64bpp-rotate-90.html
* igt@kms_big_fb@x-tiled-32bpp-rotate-270:
- shard-iclb: NOTRUN -> [SKIP][36] ([fdo#110725] / [fdo#111614]) +1 similar issue
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb3/igt@kms_big_fb@x-tiled-32bpp-rotate-270.html
* igt@kms_big_joiner@invalid-modeset:
- shard-apl: NOTRUN -> [SKIP][37] ([fdo#109271] / [i915#2705])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl1/igt@kms_big_joiner@invalid-modeset.html
* igt@kms_ccs@pipe-c-ccs-on-another-bo:
- shard-glk: NOTRUN -> [SKIP][38] ([fdo#109271]) +40 similar issues
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk1/igt@kms_ccs@pipe-c-ccs-on-another-bo.html
* igt@kms_chamelium@vga-edid-read:
- shard-apl: NOTRUN -> [SKIP][39] ([fdo#109271] / [fdo#111827]) +21 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl3/igt@kms_chamelium@vga-edid-read.html
* igt@kms_chamelium@vga-hpd-without-ddc:
- shard-kbl: NOTRUN -> [SKIP][40] ([fdo#109271] / [fdo#111827]) +9 similar issues
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl3/igt@kms_chamelium@vga-hpd-without-ddc.html
- shard-iclb: NOTRUN -> [SKIP][41] ([fdo#109284] / [fdo#111827]) +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb6/igt@kms_chamelium@vga-hpd-without-ddc.html
- shard-tglb: NOTRUN -> [SKIP][42] ([fdo#109284] / [fdo#111827]) +1 similar issue
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb6/igt@kms_chamelium@vga-hpd-without-ddc.html
- shard-glk: NOTRUN -> [SKIP][43] ([fdo#109271] / [fdo#111827]) +1 similar issue
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk8/igt@kms_chamelium@vga-hpd-without-ddc.html
* igt@kms_color_chamelium@pipe-a-ctm-0-25:
- shard-snb: NOTRUN -> [SKIP][44] ([fdo#109271] / [fdo#111827]) +13 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-snb5/igt@kms_color_chamelium@pipe-a-ctm-0-25.html
* igt@kms_content_protection@atomic-dpms:
- shard-apl: NOTRUN -> [TIMEOUT][45] ([i915#1319])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl7/igt@kms_content_protection@atomic-dpms.html
* igt@kms_cursor_crc@pipe-b-cursor-32x10-random:
- shard-tglb: NOTRUN -> [SKIP][46] ([i915#3359]) +1 similar issue
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb2/igt@kms_cursor_crc@pipe-b-cursor-32x10-random.html
* igt@kms_cursor_crc@pipe-b-cursor-512x170-random:
- shard-iclb: NOTRUN -> [SKIP][47] ([fdo#109278] / [fdo#109279])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb4/igt@kms_cursor_crc@pipe-b-cursor-512x170-random.html
* igt@kms_cursor_crc@pipe-c-cursor-64x21-random:
- shard-kbl: NOTRUN -> [FAIL][48] ([i915#54])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl4/igt@kms_cursor_crc@pipe-c-cursor-64x21-random.html
- shard-apl: NOTRUN -> [FAIL][49] ([i915#54])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl3/igt@kms_cursor_crc@pipe-c-cursor-64x21-random.html
* igt@kms_cursor_crc@pipe-d-cursor-32x32-rapid-movement:
- shard-tglb: NOTRUN -> [SKIP][50] ([i915#3319])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb6/igt@kms_cursor_crc@pipe-d-cursor-32x32-rapid-movement.html
* igt@kms_cursor_crc@pipe-d-cursor-512x512-onscreen:
- shard-tglb: NOTRUN -> [SKIP][51] ([fdo#109279] / [i915#3359]) +1 similar issue
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb1/igt@kms_cursor_crc@pipe-d-cursor-512x512-onscreen.html
* igt@kms_cursor_edge_walk@pipe-d-128x128-right-edge:
- shard-snb: NOTRUN -> [SKIP][52] ([fdo#109271]) +378 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-snb5/igt@kms_cursor_edge_walk@pipe-d-128x128-right-edge.html
* igt@kms_cursor_edge_walk@pipe-d-256x256-left-edge:
- shard-iclb: NOTRUN -> [SKIP][53] ([fdo#109278]) +11 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb8/igt@kms_cursor_edge_walk@pipe-d-256x256-left-edge.html
* igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic:
- shard-iclb: NOTRUN -> [SKIP][54] ([fdo#109274] / [fdo#109278]) +1 similar issue
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb6/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html
* igt@kms_flip@flip-vs-suspend@c-dp1:
- shard-kbl: [PASS][55] -> [DMESG-WARN][56] ([i915#180]) +3 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl3/igt@kms_flip@flip-vs-suspend@c-dp1.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl1/igt@kms_flip@flip-vs-suspend@c-dp1.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile:
- shard-apl: NOTRUN -> [SKIP][57] ([fdo#109271] / [i915#2642])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl1/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs:
- shard-kbl: NOTRUN -> [SKIP][58] ([fdo#109271] / [i915#2672])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl6/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs.html
* igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw:
- shard-glk: [PASS][59] -> [FAIL][60] ([i915#49])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-glk4/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk7/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-blt:
- shard-kbl: NOTRUN -> [SKIP][61] ([fdo#109271]) +128 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl7/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-cur-indfb-onoff:
- shard-tglb: NOTRUN -> [SKIP][62] ([fdo#111825]) +12 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb3/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-cur-indfb-onoff.html
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-shrfb-plflip-blt:
- shard-iclb: NOTRUN -> [SKIP][63] ([fdo#109280]) +10 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb1/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-shrfb-plflip-blt.html
* igt@kms_pipe_b_c_ivb@from-pipe-c-to-b-with-3-lanes:
- shard-iclb: NOTRUN -> [SKIP][64] ([fdo#109289]) +2 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb2/igt@kms_pipe_b_c_ivb@from-pipe-c-to-b-with-3-lanes.html
- shard-tglb: NOTRUN -> [SKIP][65] ([fdo#109289]) +2 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb6/igt@kms_pipe_b_c_ivb@from-pipe-c-to-b-with-3-lanes.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- shard-apl: NOTRUN -> [SKIP][66] ([fdo#109271] / [i915#533]) +2 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl7/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
* igt@kms_plane@plane-position-hole-pipe-a-planes:
- shard-glk: NOTRUN -> [FAIL][67] ([i915#2472])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk3/igt@kms_plane@plane-position-hole-pipe-a-planes.html
- shard-kbl: NOTRUN -> [FAIL][68] ([i915#2472])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl1/igt@kms_plane@plane-position-hole-pipe-a-planes.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
- shard-glk: NOTRUN -> [FAIL][69] ([i915#265])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk8/igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb.html
- shard-kbl: NOTRUN -> [FAIL][70] ([i915#265])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl3/igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb.html
* igt@kms_plane_alpha_blend@pipe-b-alpha-7efc:
- shard-apl: NOTRUN -> [FAIL][71] ([fdo#108145] / [i915#265]) +1 similar issue
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl2/igt@kms_plane_alpha_blend@pipe-b-alpha-7efc.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-opaque-fb:
- shard-kbl: NOTRUN -> [FAIL][72] ([fdo#108145] / [i915#265]) +2 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl7/igt@kms_plane_alpha_blend@pipe-c-alpha-opaque-fb.html
- shard-glk: NOTRUN -> [FAIL][73] ([fdo#108145] / [i915#265])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk2/igt@kms_plane_alpha_blend@pipe-c-alpha-opaque-fb.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb:
- shard-apl: NOTRUN -> [FAIL][74] ([i915#265]) +1 similar issue
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl8/igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb.html
* igt@kms_plane_multiple@atomic-pipe-a-tiling-yf:
- shard-tglb: NOTRUN -> [SKIP][75] ([fdo#111615])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb2/igt@kms_plane_multiple@atomic-pipe-a-tiling-yf.html
* igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping:
- shard-apl: NOTRUN -> [SKIP][76] ([fdo#109271] / [i915#2733])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl8/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4:
- shard-apl: NOTRUN -> [SKIP][77] ([fdo#109271] / [i915#658]) +4 similar issues
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl1/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4.html
* igt@kms_psr2_sf@plane-move-sf-dmg-area-0:
- shard-iclb: NOTRUN -> [SKIP][78] ([i915#2920])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb2/igt@kms_psr2_sf@plane-move-sf-dmg-area-0.html
- shard-glk: NOTRUN -> [SKIP][79] ([fdo#109271] / [i915#658])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk1/igt@kms_psr2_sf@plane-move-sf-dmg-area-0.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5:
- shard-kbl: NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#658]) +1 similar issue
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl4/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5.html
* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-iclb: [PASS][81] -> [SKIP][82] ([fdo#109441]) +1 similar issue
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb5/igt@kms_psr@psr2_cursor_plane_onoff.html
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: NOTRUN -> [SKIP][83] ([fdo#109441]) +1 similar issue
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb7/igt@kms_psr@psr2_primary_mmap_cpu.html
- shard-tglb: NOTRUN -> [FAIL][84] ([i915#132]) +1 similar issue
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb5/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_writeback@writeback-invalid-parameters:
- shard-apl: NOTRUN -> [SKIP][85] ([fdo#109271] / [i915#2437])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl2/igt@kms_writeback@writeback-invalid-parameters.html
* igt@perf@polling-parameterized:
- shard-iclb: [PASS][86] -> [FAIL][87] ([i915#1542])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-iclb3/igt@perf@polling-parameterized.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb8/igt@perf@polling-parameterized.html
* igt@prime_nv_api@i915_nv_double_export:
- shard-iclb: NOTRUN -> [SKIP][88] ([fdo#109291]) +1 similar issue
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb5/igt@prime_nv_api@i915_nv_double_export.html
* igt@prime_nv_api@nv_self_import:
- shard-tglb: NOTRUN -> [SKIP][89] ([fdo#109291]) +1 similar issue
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb7/igt@prime_nv_api@nv_self_import.html
* igt@runner@aborted:
- shard-snb: NOTRUN -> ([FAIL][90], [FAIL][91]) ([i915#3002] / [i915#698])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-snb6/igt@runner@aborted.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-snb5/igt@runner@aborted.html
* igt@sysfs_clients@fair-1:
- shard-glk: NOTRUN -> [SKIP][92] ([fdo#109271] / [i915#2994])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk6/igt@sysfs_clients@fair-1.html
- shard-iclb: NOTRUN -> [SKIP][93] ([i915#2994])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb3/igt@sysfs_clients@fair-1.html
- shard-apl: NOTRUN -> [SKIP][94] ([fdo#109271] / [i915#2994]) +4 similar issues
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl7/igt@sysfs_clients@fair-1.html
- shard-tglb: NOTRUN -> [SKIP][95] ([i915#2994])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb8/igt@sysfs_clients@fair-1.html
* igt@sysfs_clients@fair-3:
- shard-kbl: NOTRUN -> [SKIP][96] ([fdo#109271] / [i915#2994]) +2 similar issues
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl7/igt@sysfs_clients@fair-3.html
#### Possible fixes ####
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: [FAIL][97] ([i915#2846]) -> [PASS][98]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl4/igt@gem_exec_fair@basic-deadline.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl2/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-tglb: [FAIL][99] ([i915#2842]) -> [PASS][100]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-tglb3/igt@gem_exec_fair@basic-none-share@rcs0.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb7/igt@gem_exec_fair@basic-none-share@rcs0.html
- shard-glk: [FAIL][101] ([i915#2842]) -> [PASS][102]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-glk3/igt@gem_exec_fair@basic-none-share@rcs0.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk7/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [FAIL][103] ([i915#2849]) -> [PASS][104]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-iclb8/igt@gem_exec_fair@basic-throttle@rcs0.html
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb1/igt@gem_exec_fair@basic-throttle@rcs0.html
* igt@gem_exec_whisper@basic-queues-priority-all:
- shard-glk: [DMESG-WARN][105] ([i915#118] / [i915#95]) -> [PASS][106]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-glk8/igt@gem_exec_whisper@basic-queues-priority-all.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk9/igt@gem_exec_whisper@basic-queues-priority-all.html
* igt@gem_mmap_gtt@big-copy-xy:
- shard-glk: [FAIL][107] ([i915#307]) -> [PASS][108]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-glk9/igt@gem_mmap_gtt@big-copy-xy.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk4/igt@gem_mmap_gtt@big-copy-xy.html
* igt@gem_vm_create@destroy-race:
- shard-tglb: [FAIL][109] ([i915#2822]) -> [PASS][110]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-tglb6/igt@gem_vm_create@destroy-race.html
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb1/igt@gem_vm_create@destroy-race.html
* igt@gen9_exec_parse@allowed-all:
- shard-kbl: [DMESG-WARN][111] ([i915#1436] / [i915#716]) -> [PASS][112]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl4/igt@gen9_exec_parse@allowed-all.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl2/igt@gen9_exec_parse@allowed-all.html
* igt@kms_big_fb@x-tiled-64bpp-rotate-180:
- shard-tglb: [FAIL][113] -> [PASS][114]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-tglb2/igt@kms_big_fb@x-tiled-64bpp-rotate-180.html
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb6/igt@kms_big_fb@x-tiled-64bpp-rotate-180.html
* igt@kms_cursor_crc@pipe-a-cursor-256x85-onscreen:
- shard-kbl: [FAIL][115] ([i915#54]) -> [PASS][116]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl3/igt@kms_cursor_crc@pipe-a-cursor-256x85-onscreen.html
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-256x85-onscreen.html
- shard-glk: [FAIL][117] ([i915#54]) -> [PASS][118]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-glk3/igt@kms_cursor_crc@pipe-a-cursor-256x85-onscreen.html
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-glk9/igt@kms_cursor_crc@pipe-a-cursor-256x85-onscreen.html
* igt@kms_cursor_crc@pipe-a-cursor-64x21-sliding:
- shard-tglb: [FAIL][119] ([i915#2124]) -> [PASS][120]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-tglb5/igt@kms_cursor_crc@pipe-a-cursor-64x21-sliding.html
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-tglb1/igt@kms_cursor_crc@pipe-a-cursor-64x21-sliding.html
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [DMESG-WARN][121] ([i915#180]) -> [PASS][122] +2 similar issues
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl2/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
* igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
- shard-apl: [DMESG-WARN][123] ([i915#180]) -> [PASS][124]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-apl1/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl8/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
* igt@kms_psr@psr2_suspend:
- shard-iclb: [SKIP][125] ([fdo#109441]) -> [PASS][126] +3 similar issues
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-iclb3/igt@kms_psr@psr2_suspend.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb2/igt@kms_psr@psr2_suspend.html
#### Warnings ####
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: [WARN][127] ([i915#1804] / [i915#2684]) -> [WARN][128] ([i915#2684])
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-iclb6/igt@i915_pm_rc6_residency@rc6-idle.html
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb2/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-5:
- shard-iclb: [SKIP][129] ([i915#658]) -> [SKIP][130] ([i915#2920])
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-iclb5/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-5.html
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb2/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-5.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1:
- shard-iclb: [SKIP][131] ([i915#2920]) -> [SKIP][132] ([i915#658]) +2 similar issues
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-iclb2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1.html
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-iclb6/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1.html
* igt@runner@aborted:
- shard-kbl: ([FAIL][133], [FAIL][134], [FAIL][135], [FAIL][136], [FAIL][137], [FAIL][138]) ([fdo#109271] / [i915#1436] / [i915#180] / [i915#1814] / [i915#2505] / [i915#3002] / [i915#716]) -> ([FAIL][139], [FAIL][140], [FAIL][141], [FAIL][142]) ([i915#1436] / [i915#180] / [i915#1814] / [i915#3002])
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl1/igt@runner@aborted.html
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl7/igt@runner@aborted.html
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl6/igt@runner@aborted.html
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl2/igt@runner@aborted.html
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl4/igt@runner@aborted.html
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-kbl1/igt@runner@aborted.html
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl1/igt@runner@aborted.html
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl2/igt@runner@aborted.html
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl3/igt@runner@aborted.html
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-kbl1/igt@runner@aborted.html
- shard-apl: [FAIL][143] ([i915#180]) -> ([FAIL][144], [FAIL][145], [FAIL][146]) ([i915#180] / [i915#3002])
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10019/shard-apl1/igt@runner@aborted.html
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/shard-apl1/igt@runner@aborted.html
[145]:
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5767/index.html
[-- Attachment #1.2: Type: text/html, Size: 34195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks
2021-04-27 22:25 [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks Ville Syrjala
` (2 preceding siblings ...)
2021-04-28 5:21 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
@ 2021-04-28 14:38 ` Juha-Pekka Heikkila
2021-04-29 5:37 ` Karthik B S
4 siblings, 0 replies; 8+ messages in thread
From: Juha-Pekka Heikkila @ 2021-04-28 14:38 UTC (permalink / raw)
To: Ville Syrjala, igt-dev
Reviewed-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
On 28.4.2021 1.25, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Check the flip timestamp from the event (not the time we got the
> event) against the vblank timestamps. Also if things are going
> well we should expect the flip timestamp to in fact match the
> first vblank timestamp, so allow them to be equal.
>
> Cc: Karthik B S <karthik.b.s@intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> tests/kms_async_flips.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_async_flips.c b/tests/kms_async_flips.c
> index e397a54b874f..a60eab688024 100644
> --- a/tests/kms_async_flips.c
> +++ b/tests/kms_async_flips.c
> @@ -89,7 +89,7 @@ static void flip_handler(int fd_, unsigned int sequence, unsigned int tv_sec,
>
> last_ms = cur_ms;
>
> - data->flip_timestamp_us = ts.tv_sec * 1000000 + ts.tv_nsec / 1000;
> + data->flip_timestamp_us = tv_sec * 1000000l + tv_usec;
> }
>
> static void wait_flip_event(data_t *data)
> @@ -282,7 +282,7 @@ static void test_timestamp(data_t *data)
> igt_info("vbl1_timestamp = %ldus\nflip_timestamp = %ldus\nvbl2_timestamp = %ldus\n",
> vbl_time, data->flip_timestamp_us, vbl_time1);
>
> - igt_assert_f(vbl_time < data->flip_timestamp_us && vbl_time1 > data->flip_timestamp_us,
> + igt_assert_f(vbl_time <= data->flip_timestamp_us && vbl_time1 > data->flip_timestamp_us,
> "Async flip time stamp is expected to be in between 2 vblank time stamps\n");
> }
>
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks
2021-04-27 22:25 [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks Ville Syrjala
` (3 preceding siblings ...)
2021-04-28 14:38 ` [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks Juha-Pekka Heikkila
@ 2021-04-29 5:37 ` Karthik B S
2021-04-29 15:32 ` Ville Syrjälä
4 siblings, 1 reply; 8+ messages in thread
From: Karthik B S @ 2021-04-29 5:37 UTC (permalink / raw)
To: Ville Syrjala, igt-dev
On 4/28/2021 3:55 AM, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Check the flip timestamp from the event (not the time we got the
> event) against the vblank timestamps. Also if things are going
> well we should expect the flip timestamp to in fact match the
> first vblank timestamp, so allow them to be equal.
Hi,
During the initial implementation, the timestamp returned by the kernel
was vblank timestamp and we were not sending back the flip timestamp.
So we were calculating the time in the event rather than using the event
timestamp.
Is this now updated to return the flip timestamp? If not, we would
always have flip time stamp same as the previous vblank time stamp?
Thanks,
Karthik.B.S
>
> Cc: Karthik B S <karthik.b.s@intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> tests/kms_async_flips.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_async_flips.c b/tests/kms_async_flips.c
> index e397a54b874f..a60eab688024 100644
> --- a/tests/kms_async_flips.c
> +++ b/tests/kms_async_flips.c
> @@ -89,7 +89,7 @@ static void flip_handler(int fd_, unsigned int sequence, unsigned int tv_sec,
>
> last_ms = cur_ms;
>
> - data->flip_timestamp_us = ts.tv_sec * 1000000 + ts.tv_nsec / 1000;
> + data->flip_timestamp_us = tv_sec * 1000000l + tv_usec;
> }
>
> static void wait_flip_event(data_t *data)
> @@ -282,7 +282,7 @@ static void test_timestamp(data_t *data)
> igt_info("vbl1_timestamp = %ldus\nflip_timestamp = %ldus\nvbl2_timestamp = %ldus\n",
> vbl_time, data->flip_timestamp_us, vbl_time1);
>
> - igt_assert_f(vbl_time < data->flip_timestamp_us && vbl_time1 > data->flip_timestamp_us,
> + igt_assert_f(vbl_time <= data->flip_timestamp_us && vbl_time1 > data->flip_timestamp_us,
> "Async flip time stamp is expected to be in between 2 vblank time stamps\n");
> }
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks
2021-04-29 5:37 ` Karthik B S
@ 2021-04-29 15:32 ` Ville Syrjälä
2021-05-04 11:12 ` Karthik B S
0 siblings, 1 reply; 8+ messages in thread
From: Ville Syrjälä @ 2021-04-29 15:32 UTC (permalink / raw)
To: Karthik B S; +Cc: igt-dev
On Thu, Apr 29, 2021 at 11:07:53AM +0530, Karthik B S wrote:
> On 4/28/2021 3:55 AM, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Check the flip timestamp from the event (not the time we got the
> > event) against the vblank timestamps. Also if things are going
> > well we should expect the flip timestamp to in fact match the
> > first vblank timestamp, so allow them to be equal.
>
> Hi,
>
> During the initial implementation, the timestamp returned by the kernel
> was vblank timestamp and we were not sending back the flip timestamp.
>
> So we were calculating the time in the event rather than using the event
> timestamp.
That approach doesn't make too much sense since the two vblank
timestamps we're comparing against could both be in the future.
That happens if the flip is completed already during the first vblank.
But I haven't actually checked when the hw completes the flip when
scheduled during a vblank.
>
> Is this now updated to return the flip timestamp? If not, we would
> always have flip time stamp same as the previous vblank time stamp?
Looks like it just returns the last stored timestamp as before.
Which doesn't really make sense. At the very least we should
make sure the timestam and seq number are updated to reflect
the current frame. So if we do something like
1. wait for vblank
2. wait for several frames
3. async flip
then the event would now carry the timestamp from that ancient
vblank wait. Well, at least that's how it looks from the code,
still need to double check it. And the test should probably be
extended to catch stuff like that.
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks
2021-04-29 15:32 ` Ville Syrjälä
@ 2021-05-04 11:12 ` Karthik B S
0 siblings, 0 replies; 8+ messages in thread
From: Karthik B S @ 2021-05-04 11:12 UTC (permalink / raw)
To: Ville Syrjälä; +Cc: igt-dev
On 4/29/2021 9:02 PM, Ville Syrjälä wrote:
> On Thu, Apr 29, 2021 at 11:07:53AM +0530, Karthik B S wrote:
>> On 4/28/2021 3:55 AM, Ville Syrjala wrote:
>>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>>
>>> Check the flip timestamp from the event (not the time we got the
>>> event) against the vblank timestamps. Also if things are going
>>> well we should expect the flip timestamp to in fact match the
>>> first vblank timestamp, so allow them to be equal.
>> Hi,
>>
>> During the initial implementation, the timestamp returned by the kernel
>> was vblank timestamp and we were not sending back the flip timestamp.
>>
>> So we were calculating the time in the event rather than using the event
>> timestamp.
> That approach doesn't make too much sense since the two vblank
> timestamps we're comparing against could both be in the future.
> That happens if the flip is completed already during the first vblank.
> But I haven't actually checked when the hw completes the flip when
> scheduled during a vblank.
I think we are seeing this case on CI sporadically, where both the
vblanks are in the future. How should we handle this in IGT?
>
>> Is this now updated to return the flip timestamp? If not, we would
>> always have flip time stamp same as the previous vblank time stamp?
> Looks like it just returns the last stored timestamp as before.
> Which doesn't really make sense. At the very least we should
> make sure the timestam and seq number are updated to reflect
> the current frame. So if we do something like
>
> 1. wait for vblank
> 2. wait for several frames
> 3. async flip
>
> then the event would now carry the timestamp from that ancient
> vblank wait. Well, at least that's how it looks from the code,
> still need to double check it. And the test should probably be
> extended to catch stuff like that.
In the initial kernel patches enabling async flip, we tried to update
this using the frame counter register. But we received review comments
telling that the seq number and timestamp should correspond to the
vblank and should not update with flip. Any other way we can achieve this?
Agreed that the test should be extended to catch this once we have
kernel support. Also, we can remove the monotonic timestamps which we
are currently using in the test, which would fix the issue mentioned
above also.
Thanks,
Karthik.B.S
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 8+ messages in thread