[igt-dev] [PATCH i-g-t] intel-ci: Add testdisplay test to BAT

[igt-dev] [PATCH i-g-t] intel-ci: Add testdisplay test to BAT

[Swati Sharma]

testdisplay should be added to BAT. testdisplay is considered
to be the most basic test to test display functionality.
With this test we will be able to test modesetting.

Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
Cc: Petri Latvala <petri.latvala@intel.com>
Cc: Karthik B S <karthik.b.s@intel.com>
---
 tests/intel-ci/fast-feedback.testlist | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist
index b796b264..b245b7a7 100644
--- a/tests/intel-ci/fast-feedback.testlist
+++ b/tests/intel-ci/fast-feedback.testlist
@@ -149,6 +149,7 @@ igt@vgem_basic@dmabuf-mmap
 igt@vgem_basic@mmap
 igt@vgem_basic@second-client
 igt@vgem_basic@sysfs
+igt@testdisplay
 
 # All tests that do module unloading and reloading are executed last.
 # They will sometimes reveal issues of earlier tests leaving the
-- 
2.25.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

[igt-dev] ✓ Fi.CI.BAT: success for intel-ci: Add testdisplay test to BAT (rev2)

[Patchwork]

[-- Attachment #1.1: Type: text/plain, Size: 6594 bytes --]

== Series Details ==

Series: intel-ci: Add testdisplay test to BAT (rev2)
URL   : https://patchwork.freedesktop.org/series/80338/
State : success

== Summary ==

CI Bug Log - changes from IGT_5761 -> IGTPW_4858
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/index.html

Known issues
------------

  Here are the changes found in IGTPW_4858 that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@gem_exec_suspend@basic-s3:
    - fi-tgl-u2:          [PASS][1] -> [FAIL][2] ([i915#1888])
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/fi-tgl-u2/igt@gem_exec_suspend@basic-s3.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/fi-tgl-u2/igt@gem_exec_suspend@basic-s3.html

  * igt@i915_pm_rpm@module-reload:
    - fi-bsw-n3050:       [PASS][3] -> [DMESG-WARN][4] ([i915#1982])
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/fi-bsw-n3050/igt@i915_pm_rpm@module-reload.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/fi-bsw-n3050/igt@i915_pm_rpm@module-reload.html

  * igt@i915_selftest@live@execlists:
    - fi-icl-y:           [PASS][5] -> [INCOMPLETE][6] ([i915#2089] / [i915#2276])
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/fi-icl-y/igt@i915_selftest@live@execlists.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/fi-icl-y/igt@i915_selftest@live@execlists.html

  * igt@i915_selftest@live@gt_lrc:
    - fi-tgl-u2:          [PASS][7] -> [DMESG-FAIL][8] ([i915#1233])
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/fi-tgl-u2/igt@i915_selftest@live@gt_lrc.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/fi-tgl-u2/igt@i915_selftest@live@gt_lrc.html

  * igt@kms_chamelium@common-hpd-after-suspend:
    - fi-kbl-7500u:       [PASS][9] -> [DMESG-WARN][10] ([i915#2203])
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/fi-kbl-7500u/igt@kms_chamelium@common-hpd-after-suspend.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/fi-kbl-7500u/igt@kms_chamelium@common-hpd-after-suspend.html

  * igt@kms_cursor_legacy@basic-flip-before-cursor-atomic:
    - fi-bsw-kefka:       [PASS][11] -> [DMESG-WARN][12] ([i915#1982])
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/fi-bsw-kefka/igt@kms_cursor_legacy@basic-flip-before-cursor-atomic.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/fi-bsw-kefka/igt@kms_cursor_legacy@basic-flip-before-cursor-atomic.html

  
#### Possible fixes ####

  * igt@gem_exec_suspend@basic-s0:
    - fi-tgl-u2:          [FAIL][13] ([i915#1888]) -> [PASS][14]
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/fi-tgl-u2/igt@gem_exec_suspend@basic-s0.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/fi-tgl-u2/igt@gem_exec_suspend@basic-s0.html

  * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
    - {fi-kbl-7560u}:     [DMESG-WARN][15] ([i915#1982]) -> [PASS][16]
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/fi-kbl-7560u/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/fi-kbl-7560u/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html

  * igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1:
    - fi-icl-u2:          [DMESG-WARN][17] ([i915#1982]) -> [PASS][18]
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/fi-icl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/fi-icl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1.html

  
#### Warnings ####

  * igt@i915_pm_rpm@module-reload:
    - fi-kbl-x1275:       [DMESG-FAIL][19] ([i915#62]) -> [SKIP][20] ([fdo#109271])
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/fi-kbl-x1275/igt@i915_pm_rpm@module-reload.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/fi-kbl-x1275/igt@i915_pm_rpm@module-reload.html

  * igt@kms_cursor_legacy@basic-flip-after-cursor-legacy:
    - fi-kbl-x1275:       [DMESG-WARN][21] ([i915#62] / [i915#92]) -> [DMESG-WARN][22] ([i915#62] / [i915#92] / [i915#95]) +4 similar issues
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/fi-kbl-x1275/igt@kms_cursor_legacy@basic-flip-after-cursor-legacy.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/fi-kbl-x1275/igt@kms_cursor_legacy@basic-flip-after-cursor-legacy.html

  * igt@kms_force_connector_basic@force-edid:
    - fi-kbl-x1275:       [DMESG-WARN][23] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][24] ([i915#62] / [i915#92]) +3 similar issues
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/fi-kbl-x1275/igt@kms_force_connector_basic@force-edid.html
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/fi-kbl-x1275/igt@kms_force_connector_basic@force-edid.html

  
  {name}: This element is suppressed. This means it is ignored when computing
          the status of the difference (SUCCESS, WARNING, or FAILURE).

  [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
  [i915#1233]: https://gitlab.freedesktop.org/drm/intel/issues/1233
  [i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
  [i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
  [i915#2089]: https://gitlab.freedesktop.org/drm/intel/issues/2089
  [i915#2100]: https://gitlab.freedesktop.org/drm/intel/issues/2100
  [i915#2203]: https://gitlab.freedesktop.org/drm/intel/issues/2203
  [i915#2268]: https://gitlab.freedesktop.org/drm/intel/issues/2268
  [i915#2276]: https://gitlab.freedesktop.org/drm/intel/issues/2276
  [i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
  [i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
  [i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95


Participating hosts (44 -> 38)
------------------------------

  Additional (1): fi-tgl-y 
  Missing    (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus 


Build changes
-------------

  * CI: CI-20190529 -> None
  * IGT: IGT_5761 -> IGTPW_4858

  CI-20190529: 20190529
  CI_DRM_8848: f39035176cb854c6d620af7614a60a485ee26818 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_4858: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/index.html
  IGT_5761: dc048961c2f54a251b43b81ebf2a95d1bab490f2 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/index.html

[-- Attachment #1.2: Type: text/html, Size: 8143 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

[igt-dev] ✗ Fi.CI.IGT: failure for intel-ci: Add testdisplay test to BAT (rev2)

[Patchwork]

[-- Attachment #1.1: Type: text/plain, Size: 13948 bytes --]

== Series Details ==

Series: intel-ci: Add testdisplay test to BAT (rev2)
URL   : https://patchwork.freedesktop.org/series/80338/
State : failure

== Summary ==

CI Bug Log - changes from IGT_5761_full -> IGTPW_4858_full
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with IGTPW_4858_full absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in IGTPW_4858_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_4858/index.html

Possible new issues
-------------------

  Here are the unknown changes that may have been introduced in IGTPW_4858_full:

### IGT changes ###

#### Possible regressions ####

  * igt@kms_vblank@pipe-a-wait-busy-hang:
    - shard-hsw:          [PASS][1] -> [INCOMPLETE][2]
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-hsw1/igt@kms_vblank@pipe-a-wait-busy-hang.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-hsw1/igt@kms_vblank@pipe-a-wait-busy-hang.html

  
#### Warnings ####

  * igt@perf@blocking-parameterized:
    - shard-hsw:          [FAIL][3] ([i915#1542]) -> [INCOMPLETE][4]
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-hsw4/igt@perf@blocking-parameterized.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-hsw1/igt@perf@blocking-parameterized.html

  
Known issues
------------

  Here are the changes found in IGTPW_4858_full that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@gem_ctx_isolation@preservation-s3@vcs0:
    - shard-kbl:          [PASS][5] -> [DMESG-WARN][6] ([i915#180]) +2 similar issues
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-kbl7/igt@gem_ctx_isolation@preservation-s3@vcs0.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-kbl4/igt@gem_ctx_isolation@preservation-s3@vcs0.html

  * igt@gem_exec_params@no-vebox:
    - shard-snb:          [PASS][7] -> [TIMEOUT][8] ([i915#1958]) +1 similar issue
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-snb4/igt@gem_exec_params@no-vebox.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-snb6/igt@gem_exec_params@no-vebox.html

  * igt@kms_big_fb@x-tiled-32bpp-rotate-0:
    - shard-glk:          [PASS][9] -> [FAIL][10] ([i915#1119])
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-glk8/igt@kms_big_fb@x-tiled-32bpp-rotate-0.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-glk7/igt@kms_big_fb@x-tiled-32bpp-rotate-0.html

  * igt@kms_cursor_edge_walk@pipe-b-256x256-top-edge:
    - shard-glk:          [PASS][11] -> [DMESG-WARN][12] ([i915#1982])
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-glk3/igt@kms_cursor_edge_walk@pipe-b-256x256-top-edge.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-glk4/igt@kms_cursor_edge_walk@pipe-b-256x256-top-edge.html

  * igt@kms_draw_crc@draw-method-xrgb2101010-blt-untiled:
    - shard-apl:          [PASS][13] -> [DMESG-WARN][14] ([i915#1635] / [i915#1982])
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-apl3/igt@kms_draw_crc@draw-method-xrgb2101010-blt-untiled.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-apl4/igt@kms_draw_crc@draw-method-xrgb2101010-blt-untiled.html

  * igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1:
    - shard-iclb:         [PASS][15] -> [FAIL][16] ([i915#79])
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-iclb4/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-iclb6/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1.html

  * igt@kms_flip@plain-flip-ts-check-interruptible@c-hdmi-a2:
    - shard-glk:          [PASS][17] -> [FAIL][18] ([i915#2122])
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-glk3/igt@kms_flip@plain-flip-ts-check-interruptible@c-hdmi-a2.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-glk5/igt@kms_flip@plain-flip-ts-check-interruptible@c-hdmi-a2.html

  * igt@kms_frontbuffer_tracking@psr-rgb565-draw-mmap-wc:
    - shard-tglb:         [PASS][19] -> [DMESG-WARN][20] ([i915#1982]) +6 similar issues
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-tglb6/igt@kms_frontbuffer_tracking@psr-rgb565-draw-mmap-wc.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-tglb3/igt@kms_frontbuffer_tracking@psr-rgb565-draw-mmap-wc.html

  * igt@kms_psr@psr2_sprite_plane_move:
    - shard-iclb:         [PASS][21] -> [SKIP][22] ([fdo#109441]) +2 similar issues
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-iclb8/igt@kms_psr@psr2_sprite_plane_move.html

  * igt@kms_vblank@pipe-c-wait-forked-busy:
    - shard-kbl:          [PASS][23] -> [DMESG-WARN][24] ([i915#1982]) +1 similar issue
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-kbl4/igt@kms_vblank@pipe-c-wait-forked-busy.html
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-kbl4/igt@kms_vblank@pipe-c-wait-forked-busy.html

  * igt@perf@polling-parameterized:
    - shard-iclb:         [PASS][25] -> [FAIL][26] ([i915#1542])
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-iclb2/igt@perf@polling-parameterized.html
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-iclb7/igt@perf@polling-parameterized.html

  * igt@prime_busy@after-wait@vcs0:
    - shard-hsw:          [PASS][27] -> [FAIL][28] ([i915#2258]) +1 similar issue
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-hsw7/igt@prime_busy@after-wait@vcs0.html
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-hsw6/igt@prime_busy@after-wait@vcs0.html

  
#### Possible fixes ####

  * {igt@feature_discovery@psr2}:
    - shard-iclb:         [SKIP][29] ([i915#658]) -> [PASS][30]
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-iclb3/igt@feature_discovery@psr2.html
   [30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-iclb2/igt@feature_discovery@psr2.html

  * igt@i915_pm_lpsp@screens-disabled:
    - shard-hsw:          [TIMEOUT][31] ([i915#1958]) -> [PASS][32] +1 similar issue
   [31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-hsw4/igt@i915_pm_lpsp@screens-disabled.html
   [32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-hsw4/igt@i915_pm_lpsp@screens-disabled.html

  * igt@kms_cursor_crc@pipe-a-cursor-128x42-onscreen:
    - shard-apl:          [FAIL][33] ([i915#1635] / [i915#54]) -> [PASS][34]
   [33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-apl6/igt@kms_cursor_crc@pipe-a-cursor-128x42-onscreen.html
   [34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-apl6/igt@kms_cursor_crc@pipe-a-cursor-128x42-onscreen.html
    - shard-kbl:          [FAIL][35] ([i915#54]) -> [PASS][36]
   [35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-kbl6/igt@kms_cursor_crc@pipe-a-cursor-128x42-onscreen.html
   [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-kbl6/igt@kms_cursor_crc@pipe-a-cursor-128x42-onscreen.html

  * igt@kms_cursor_legacy@flip-vs-cursor-varying-size:
    - shard-glk:          [FAIL][37] ([IGT#5]) -> [PASS][38]
   [37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-glk7/igt@kms_cursor_legacy@flip-vs-cursor-varying-size.html
   [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-glk1/igt@kms_cursor_legacy@flip-vs-cursor-varying-size.html

  * igt@kms_flip_tiling@flip-changes-tiling:
    - shard-iclb:         [DMESG-WARN][39] ([i915#1982]) -> [PASS][40]
   [39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-iclb8/igt@kms_flip_tiling@flip-changes-tiling.html
   [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-iclb7/igt@kms_flip_tiling@flip-changes-tiling.html

  * igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc:
    - shard-kbl:          [DMESG-WARN][41] ([i915#1982]) -> [PASS][42] +1 similar issue
   [41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-kbl6/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html
   [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-kbl7/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html

  * igt@kms_frontbuffer_tracking@fbcpsr-shrfb-scaledprimary:
    - shard-tglb:         [DMESG-WARN][43] ([i915#1982]) -> [PASS][44]
   [43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-tglb6/igt@kms_frontbuffer_tracking@fbcpsr-shrfb-scaledprimary.html
   [44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-tglb3/igt@kms_frontbuffer_tracking@fbcpsr-shrfb-scaledprimary.html

  * igt@kms_hdr@bpc-switch-suspend:
    - shard-kbl:          [INCOMPLETE][45] ([i915#155]) -> [PASS][46]
   [45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-kbl6/igt@kms_hdr@bpc-switch-suspend.html
   [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-kbl6/igt@kms_hdr@bpc-switch-suspend.html

  * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
    - shard-kbl:          [DMESG-WARN][47] ([i915#180]) -> [PASS][48] +7 similar issues
   [47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-kbl4/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
   [48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-kbl6/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html

  * igt@kms_psr@psr2_sprite_mmap_gtt:
    - shard-iclb:         [SKIP][49] ([fdo#109441]) -> [PASS][50] +3 similar issues
   [49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-iclb6/igt@kms_psr@psr2_sprite_mmap_gtt.html
   [50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html

  * igt@prime_busy@after@vecs0:
    - shard-hsw:          [FAIL][51] ([i915#2258]) -> [PASS][52] +1 similar issue
   [51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-hsw2/igt@prime_busy@after@vecs0.html
   [52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-hsw4/igt@prime_busy@after@vecs0.html

  
#### Warnings ####

  * igt@gem_exec_reloc@basic-concurrent16:
    - shard-snb:          [FAIL][53] ([i915#1930]) -> [TIMEOUT][54] ([i915#1958])
   [53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-snb6/igt@gem_exec_reloc@basic-concurrent16.html
   [54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-snb6/igt@gem_exec_reloc@basic-concurrent16.html

  * igt@kms_frontbuffer_tracking@fbcpsr-1p-indfb-fliptrack:
    - shard-hsw:          [TIMEOUT][55] ([i915#1958]) -> [SKIP][56] ([fdo#109271]) +1 similar issue
   [55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-hsw4/igt@kms_frontbuffer_tracking@fbcpsr-1p-indfb-fliptrack.html
   [56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-hsw2/igt@kms_frontbuffer_tracking@fbcpsr-1p-indfb-fliptrack.html

  * igt@kms_vblank@pipe-d-query-forked-busy:
    - shard-snb:          [SKIP][57] ([fdo#109271]) -> [TIMEOUT][58] ([i915#1958]) +3 similar issues
   [57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-snb5/igt@kms_vblank@pipe-d-query-forked-busy.html
   [58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-snb6/igt@kms_vblank@pipe-d-query-forked-busy.html

  * igt@prime_nv_api@nv_i915_import_twice_check_flink_name:
    - shard-tglb:         [INCOMPLETE][59] ([i915#1686]) -> [SKIP][60] ([fdo#109291])
   [59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5761/shard-tglb3/igt@prime_nv_api@nv_i915_import_twice_check_flink_name.html
   [60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/shard-tglb3/igt@prime_nv_api@nv_i915_import_twice_check_flink_name.html

  
  {name}: This element is suppressed. This means it is ignored when computing
          the status of the difference (SUCCESS, WARNING, or FAILURE).

  [IGT#5]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/5
  [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
  [fdo#109291]: https://bugs.freedesktop.org/show_bug.cgi?id=109291
  [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
  [i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119
  [i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
  [i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
  [i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
  [i915#1686]: https://gitlab.freedesktop.org/drm/intel/issues/1686
  [i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
  [i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
  [i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
  [i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
  [i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
  [i915#2258]: https://gitlab.freedesktop.org/drm/intel/issues/2258
  [i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
  [i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
  [i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79


Participating hosts (8 -> 8)
------------------------------

  No changes in participating hosts


Build changes
-------------

  * CI: CI-20190529 -> None
  * IGT: IGT_5761 -> IGTPW_4858

  CI-20190529: 20190529
  CI_DRM_8848: f39035176cb854c6d620af7614a60a485ee26818 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_4858: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/index.html
  IGT_5761: dc048961c2f54a251b43b81ebf2a95d1bab490f2 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/index.html

[-- Attachment #1.2: Type: text/html, Size: 16446 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

Re: [igt-dev] [PATCH i-g-t] intel-ci: Add testdisplay test to BAT

[Sharma, Swati2]

BAT results
https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/index.html?testfilter=testdisplay

Execution time of few CI m/c.
|fi-tgl-dsi|fi-tgl-u2|fi-tgl-y|fi-ehl-1|fi-icl-u2|fi-icl-y|fi-cml-u2|
|  0.352s  |  0.064s | 0.548s |	4.686s |  5.311s | 0.101s | 1.464s  |

Execution time depends upon which panel is connected if its edp max it 
supports 2 resolutions => less time. For HDMI; having multiple 
resolutions its taking more time.

On 06-Aug-20 4:38 PM, Swati Sharma wrote:
> testdisplay should be added to BAT. testdisplay is considered
> to be the most basic test to test display functionality.
> With this test we will be able to test modesetting.
> 
> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Cc: Karthik B S <karthik.b.s@intel.com>
> ---
>   tests/intel-ci/fast-feedback.testlist | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist
> index b796b264..b245b7a7 100644
> --- a/tests/intel-ci/fast-feedback.testlist
> +++ b/tests/intel-ci/fast-feedback.testlist
> @@ -149,6 +149,7 @@ igt@vgem_basic@dmabuf-mmap
>   igt@vgem_basic@mmap
>   igt@vgem_basic@second-client
>   igt@vgem_basic@sysfs
> +igt@testdisplay
>   
>   # All tests that do module unloading and reloading are executed last.
>   # They will sometimes reveal issues of earlier tests leaving the
> 

-- 
~Swati Sharma
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t] intel-ci: Add testdisplay test to BAT

[Sharma, Swati2]

@martin peres any thoughts?

On 10-Aug-20 1:59 PM, Sharma, Swati2 wrote:
> BAT results
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/index.html?testfilter=testdisplay 
> 
> 
> Execution time of few CI m/c.
> |fi-tgl-dsi|fi-tgl-u2|fi-tgl-y|fi-ehl-1|fi-icl-u2|fi-icl-y|fi-cml-u2|
> |  0.352s  |  0.064s | 0.548s |    4.686s |  5.311s | 0.101s | 1.464s  |
> 
> Execution time depends upon which panel is connected if its edp max it 
> supports 2 resolutions => less time. For HDMI; having multiple 
> resolutions its taking more time.
> 
> On 06-Aug-20 4:38 PM, Swati Sharma wrote:
>> testdisplay should be added to BAT. testdisplay is considered
>> to be the most basic test to test display functionality.
>> With this test we will be able to test modesetting.
>>
>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
>> Cc: Petri Latvala <petri.latvala@intel.com>
>> Cc: Karthik B S <karthik.b.s@intel.com>
>> ---
>>   tests/intel-ci/fast-feedback.testlist | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/tests/intel-ci/fast-feedback.testlist 
>> b/tests/intel-ci/fast-feedback.testlist
>> index b796b264..b245b7a7 100644
>> --- a/tests/intel-ci/fast-feedback.testlist
>> +++ b/tests/intel-ci/fast-feedback.testlist
>> @@ -149,6 +149,7 @@ igt@vgem_basic@dmabuf-mmap
>>   igt@vgem_basic@mmap
>>   igt@vgem_basic@second-client
>>   igt@vgem_basic@sysfs
>> +igt@testdisplay
>>   # All tests that do module unloading and reloading are executed last.
>>   # They will sometimes reveal issues of earlier tests leaving the
>>
> 

-- 
~Swati Sharma
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t] intel-ci: Add testdisplay test to BAT

[Peres, Martin]

[-- Attachment #1: Type: text/plain, Size: 2123 bytes --]

Hi,

I do not think the added time is bad, but wasn't testdisplay considered
for eviction as it was not testing anything else but the fact that the
kernel does not blow up on modeset?

Could it be improved to check that we generate a valid image? This might
require pipe writeback though, so we shouldn't block on that.

Also, how slow is it when we have 6 pipes and 6 DP displays connected?
Wouldn't it be taking a lot of time?

Martin

On 2020-08-13 10:24, Sharma, Swati2 wrote:
> @martin peres any thoughts?
> 
> On 10-Aug-20 1:59 PM, Sharma, Swati2 wrote:
>> BAT results
>> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/index.html?testfilter=testdisplay
>>
>>
>> Execution time of few CI m/c.
>> |fi-tgl-dsi|fi-tgl-u2|fi-tgl-y|fi-ehl-1|fi-icl-u2|fi-icl-y|fi-cml-u2|
>> |  0.352s  |  0.064s | 0.548s |    4.686s |  5.311s | 0.101s | 1.464s  |
>>
>> Execution time depends upon which panel is connected if its edp max it
>> supports 2 resolutions => less time. For HDMI; having multiple
>> resolutions its taking more time.
>>
>> On 06-Aug-20 4:38 PM, Swati Sharma wrote:
>>> testdisplay should be added to BAT. testdisplay is considered
>>> to be the most basic test to test display functionality.
>>> With this test we will be able to test modesetting.
>>>
>>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
>>> Cc: Petri Latvala <petri.latvala@intel.com>
>>> Cc: Karthik B S <karthik.b.s@intel.com>
>>> ---
>>>   tests/intel-ci/fast-feedback.testlist | 1 +
>>>   1 file changed, 1 insertion(+)
>>>
>>> diff --git a/tests/intel-ci/fast-feedback.testlist
>>> b/tests/intel-ci/fast-feedback.testlist
>>> index b796b264..b245b7a7 100644
>>> --- a/tests/intel-ci/fast-feedback.testlist
>>> +++ b/tests/intel-ci/fast-feedback.testlist
>>> @@ -149,6 +149,7 @@ igt@vgem_basic@dmabuf-mmap
>>>   igt@vgem_basic@mmap
>>>   igt@vgem_basic@second-client
>>>   igt@vgem_basic@sysfs
>>> +igt@testdisplay
>>>   # All tests that do module unloading and reloading are executed last.
>>>   # They will sometimes reveal issues of earlier tests leaving the
>>>
>>
> 


[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1774 bytes --]

[-- Attachment #3: Type: text/plain, Size: 154 bytes --]

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t] intel-ci: Add testdisplay test to BAT

[Sharma, Swati2]

On 13-Aug-20 2:56 PM, Peres, Martin wrote:
> Hi,
> 
> I do not think the added time is bad, but wasn't testdisplay considered
> for eviction as it was not testing anything else but the fact that the
> kernel does not blow up on modeset?

Correct. It's for modeset testing. However, Chris commented saying same 
can be tested with kms_setmode@basic. Should we add this test in 
fast-feedback then?
AON, igt@kms_setmode@basic-clone-single-crtc is present.

> 
> Could it be improved to check that we generate a valid image? This might
> require pipe writeback though, so we shouldn't block on that.
> 
> Also, how slow is it when we have 6 pipes and 6 DP displays connected?
> Wouldn't it be taking a lot of time?
> 
Yes indeed it will take long time.

> Martin
> 
> On 2020-08-13 10:24, Sharma, Swati2 wrote:
>> @martin peres any thoughts?
>>
>> On 10-Aug-20 1:59 PM, Sharma, Swati2 wrote:
>>> BAT results
>>> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/index.html?testfilter=testdisplay
>>>
>>>
>>> Execution time of few CI m/c.
>>> |fi-tgl-dsi|fi-tgl-u2|fi-tgl-y|fi-ehl-1|fi-icl-u2|fi-icl-y|fi-cml-u2|
>>> |  0.352s  |  0.064s | 0.548s |    4.686s |  5.311s | 0.101s | 1.464s  |
>>>
>>> Execution time depends upon which panel is connected if its edp max it
>>> supports 2 resolutions => less time. For HDMI; having multiple
>>> resolutions its taking more time.
>>>
>>> On 06-Aug-20 4:38 PM, Swati Sharma wrote:
>>>> testdisplay should be added to BAT. testdisplay is considered
>>>> to be the most basic test to test display functionality.
>>>> With this test we will be able to test modesetting.
>>>>
>>>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
>>>> Cc: Petri Latvala <petri.latvala@intel.com>
>>>> Cc: Karthik B S <karthik.b.s@intel.com>
>>>> ---
>>>>    tests/intel-ci/fast-feedback.testlist | 1 +
>>>>    1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/tests/intel-ci/fast-feedback.testlist
>>>> b/tests/intel-ci/fast-feedback.testlist
>>>> index b796b264..b245b7a7 100644
>>>> --- a/tests/intel-ci/fast-feedback.testlist
>>>> +++ b/tests/intel-ci/fast-feedback.testlist
>>>> @@ -149,6 +149,7 @@ igt@vgem_basic@dmabuf-mmap
>>>>    igt@vgem_basic@mmap
>>>>    igt@vgem_basic@second-client
>>>>    igt@vgem_basic@sysfs
>>>> +igt@testdisplay
>>>>    # All tests that do module unloading and reloading are executed last.
>>>>    # They will sometimes reveal issues of earlier tests leaving the
>>>>
>>>
>>
> 

-- 
~Swati Sharma
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t] intel-ci: Add testdisplay test to BAT

[Chris Wilson]

Quoting Swati Sharma (2020-08-06 12:08:03)
> testdisplay should be added to BAT. testdisplay is considered
> to be the most basic test to test display functionality.
> With this test we will be able to test modesetting.

Some might say that kms_setmode@basic provides the same coverage of
basic modesetting. So what can be replaced? Does testdisplay have a good
history of detecting bugs that others cannot? Does testdisplay have a
good history of providing easy-to-debug results? [The latter is asking
if it is a good primary test.] As I remember, testdisplay was relegated
because it wasn't particularly helpful as anything other than an
exhaustive sweep through all the modes.
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t] intel-ci: Add testdisplay test to BAT

[Petri Latvala]

On Thu, Aug 13, 2020 at 09:39:27AM +0100, Chris Wilson wrote:
> Quoting Swati Sharma (2020-08-06 12:08:03)
> > testdisplay should be added to BAT. testdisplay is considered
> > to be the most basic test to test display functionality.
> > With this test we will be able to test modesetting.
> 
> Some might say that kms_setmode@basic provides the same coverage of
> basic modesetting. So what can be replaced? Does testdisplay have a good
> history of detecting bugs that others cannot? Does testdisplay have a
> good history of providing easy-to-debug results? [The latter is asking
> if it is a good primary test.] As I remember, testdisplay was relegated
> because it wasn't particularly helpful as anything other than an
> exhaustive sweep through all the modes.

I had similar recollections but testdisplay was never part of BAT,
says git log. I believe the original reason to not even consider it
was the runtime, which has been considerably impoved lately.

Other than that, the questions could use some answers.

(We should write those questions down in tests/intel-ci/README)


-- 
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev