tests/kms_chamelium: Don't use CCS modifiers in random plane setup
PATCH 1/2 tests/kms_chamelium: Don't use CCS modifiers in random plane setup
The randomized setup happens for overlay planes only and the randomization of each value is completely independent, whereas every CCS plane needs to come paired with a main surface that is setup correctly:
Each CCS tile matches a 1024x512 pixel area of the main surface. To match certain aspects of the 3D hardware the CCS is considered to be made up of normal 128Bx32 Y tiles, Thus the CCS pitch must be specified in multiples of 128 bytes.
Let's not use CCS modifiers on the surfaces for the random tests - it would complicate the code too much to create valid configurations. A dedicated test for CCS would be much better.
--- lib/igt_fb.c | 12 ++++++------ lib/igt_fb.h | 2 ++ tests/kms_chamelium.c | 1 + 3 files changed, 9 insertions(+), 6 deletions(-)
lib/igt_fb.c +6 -6
@@ -493,7 +493,7 @@ static bool is_gen12_ccs_modifier(uint64_t modifier) modifier ==I915_FORMAT_MOD_Y_TILED_GEN12_RC_CCS_CC ; } -static bool is_ccs_modifier (uint64_t modifier) +bool igt_is_ccs_modifier (uint64_t modifier) {return is_gen12_ccs_modifier (modifier) || modifier == I915_FORMAT_MOD_Y_TILED_CCS ||
@@ -502,7 +502,7 @@ static bool is_ccs_modifier(uint64_t modifier)static bool is_ccs_plane (const struct igt_fb *fb,int plane) { -if (!is_ccs_modifier (fb->modifier)) +if (!igt_is_ccs_modifier (fb->modifier))return false;return plane >= fb->num_planes /2 ;
@@ -604,7 +604,7 @@ static int fb_num_planes(const struct igt_fb *fb) {int num_planes =lookup_drm_format (fb->drm_format)->num_planes; -if (is_ccs_modifier (fb->modifier)) +if (igt_is_ccs_modifier (fb->modifier)) num_planes *=2 ;if (fb->modifier ==I915_FORMAT_MOD_Y_TILED_GEN12_RC_CCS_CC )
@@ -1995,7 +1995,7 @@ static bool blitter_ok(const struct igt_fb *fb)if (!is_i915_device (fb->fd))return false; -if (is_ccs_modifier (fb->modifier)) +if (igt_is_ccs_modifier (fb->modifier))return false;for (int i =0 ; i < fb->num_planes; i++) {
@@ -2030,7 +2030,7 @@ static bool use_enginecopy(const struct igt_fb *fb)return false;return fb->modifier == I915_FORMAT_MOD_Yf_TILED || -is_ccs_modifier (fb->modifier) || +igt_is_ccs_modifier (fb->modifier) || !gem_has_mappable_ggtt (fb->fd); }
@@ -2095,7 +2095,7 @@ static void init_buf(struct fb_blit_upload *blit,if (buf->format_is_yuv_semiplanar) buf->yuv_semiplanar_bpp =yuv_semiplanar_bpp (fb->drm_format); -if (is_ccs_modifier (fb->modifier)) { +if (igt_is_ccs_modifier (fb->modifier)) {igt_assert_eq (fb->strides[0 ] &127 ,0 );if (is_gen12_ccs_modifier (fb->modifier))
lib/igt_fb.h +2 -0
@@ -207,5 +207,7 @@ int igt_format_plane_bpp(uint32_t drm_format, int plane);void igt_format_array_fill (uint32_t **formats_array,unsigned int *count,bool allow_yuv); +bool igt_is_ccs_modifier (uint64_t modifier); +#endif /* __IGT_FB_H__ */
tests/kms_chamelium.c +1 -0
@@ -2079,6 +2079,7 @@ static void randomize_plane_setup(data_t *data, igt_plane_t *plane,/* First pass to count the supported formats. */ for (i =0 ; i < plane->format_mod_count; i++)if (igt_fb_supported_format (plane->formats[i]) && + !igt_is_ccs_modifier (plane->modifiers[i]) && (allow_yuv || !igt_format_is_yuv (plane->formats[i]))) idx[count++] = i;
Signature · 6 lines
2.24.1 _______________________________________________ igt-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/igt-dev
PATCH 2/2 tests/kms_chamelium: Don't fail random palnes tests on invalid config
It is possible to generate a configuration that the driver rejects because it cannot be handled (e.g. exceeding the number of available scalers). Until now the test was failing in such cases with:
igt_kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file ../lib/igt_kms.c:3490:
igt_kms-CRITICAL: Failed assertion: ret == 0
igt_kms-CRITICAL: Last errno: 22, Invalid argument
igt_kms-CRITICAL: error: -22 != 0
With this change we will just note that the atomic commit is invalid and pass the test without causing random noise.
--- tests/kms_chamelium.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-)
tests/kms_chamelium.c +12 -1
@@ -2402,6 +2402,7 @@ static void test_display_planes_random(data_t *data,bool allow_yuv;unsigned int i;unsigned int fb_id; +int ret;switch (check) {case CHAMELIUM_CHECK_CRC :
@@ -2478,7 +2479,15 @@ static void test_display_planes_random(data_t *data, fb_crc =chamelium_calculate_fb_crc_async_start (data->drm_fd, &result_fb); -igt_display_commit2 (&data->display,COMMIT_ATOMIC ); + ret =igt_display_try_commit2 (&data->display,COMMIT_ATOMIC ); + +/* we have invalid configuration, noting we can do */ +if (ret == -EINVAL ) { +igt_info ("The random plane configuration is invalid, " +"passing the test without testing anything.\n" ); + goto cleanup; + } +if (check ==CHAMELIUM_CHECK_CRC ) {chamelium_capture (data->chamelium, port,0 ,0 ,0 ,0 ,1 );
@@ -2505,6 +2514,8 @@ static void test_display_planes_random(data_t *data,chamelium_destroy_frame_dump (dump); } +cleanup: +for (i =0 ; i < overlay_planes_count; i++)igt_remove_fb (data->drm_fd, &overlay_fbs[i]);
Signature · 6 lines
2.24.1 _______________________________________________ igt-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/igt-dev
Re: [igt-dev] [PATCH i-g-t 2/2] tests/kms_chamelium: Don't fail random palnes tests on invalid config
Quoted 32 lines · Arkadiusz Hiler
It is possible to generate a configuration that the driver rejects because it cannot be handled (e.g. exceeding the number of available scalers). Until now the test was failing in such cases with:
igt_kms-CRITICAL: Test assertion failure function
igt_display_commit_atomic, file../lib/igt_kms.c:3490:
igt_kms-CRITICAL: Failed assertion: ret == 0
igt_kms-CRITICAL: Last errno: 22, Invalid argument
igt_kms-CRITICAL: error: -22 != 0With this change we will just note that the atomic commit is invalid and pass the test without causing random noise.
Cc Petri Latvala <[email protected]>Cc Martin Peres <[email protected]>Signed-off-by Arkadiusz Hiler <[email protected]>--- tests/kms_chamelium.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-)tests/kms_chamelium.c +1
-0@@ -2402,6 +2402,7 @@ static void test_display_planes_random(data_t *data,bool allow_yuv;unsigned int i;unsigned int fb_id; +int ret;switch (check) {case CHAMELIUM_CHECK_CRC :
tests/kms_chamelium.c static void test_display_planes_random(data_t *data, · line 2484
Quoted 7 lines
tests/kms_chamelium.c +3
-1@@ -2478,7 +2479,15 @@ static void test_display_planes_random(data_t *data, fb_crc =chamelium_calculate_fb_crc_async_start (data->drm_fd, &result_fb); -igt_display_commit2 (&data->display,COMMIT_ATOMIC ); + ret =igt_display_try_commit2 (&data->display,COMMIT_ATOMIC ); + +/* we have invalid configuration, noting we can do */
I'm noting that there's nothing we can do.
Signature · 1 line
Petri Latvala
Quoted 21 lines
tests/kms_chamelium.c +8
-0+if (ret == -EINVAL ) { +igt_info ("The random plane configuration is invalid, " +"passing the test without testing anything.\n" ); + goto cleanup; + } +if (check ==CHAMELIUM_CHECK_CRC ) {chamelium_capture (data->chamelium, port,0 ,0 ,0 ,0 ,1 );@@ -2505,6 +2514,8 @@ static void test_display_planes_random(data_t *data,chamelium_destroy_frame_dump (dump); } +cleanup: +for (i =0 ; i < overlay_planes_count; i++)igt_remove_fb (data->drm_fd, &overlay_fbs[i]);Signature · 1 line
2.24.1
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Re: [igt-dev] [PATCH i-g-t 2/2] tests/kms_chamelium: Don't fail random palnes tests on invalid config
In reply to Arkadiusz Hilers/palnes/planes
Quoted 11 lines · Arkadiusz
It is possible to generate a configuration that the driver rejects because it cannot be handled (e.g. exceeding the number of available scalers). Until now the test was failing in such cases with:
igt_kms-CRITICAL: Test assertion failure function
igt_display_commit_atomic, file../lib/igt_kms.c:3490:
igt_kms-CRITICAL: Failed assertion: ret == 0
igt_kms-CRITICAL: Last errno: 22, Invalid argument
igt_kms-CRITICAL: error: -22 != 0With this change we will just note that the atomic commit is invalid and pass the test without causing random noise.
I was about to object strongly, but thinking about it further, I think this whole subtest makes no sense. We have a ton of tests for planes, and if the targeted HW does not have support for CRCs, then it should be emulated using pipe writeback or using chamelium as a source of CRC.
Anyway, fixing this test would require a loop of atomic tries until a suitable configuration would be found, until then, I would rather skip than give the idea that the test could test anything.
In summary, either:
- nuke the subtest
- make it skip upon atomic check failure
- fix it by looking for valid configurations
I am just against the idea of passing a test without it doing anything.
Martin
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Re: [igt-dev] [PATCH i-g-t 2/2] tests/kms_chamelium: Don't fail random palnes tests on invalid config
Quoted 15 lines · Martin
s/palnes/planes
Quoted 11 lines · Arkadiusz
It is possible to generate a configuration that the driver rejects because it cannot be handled (e.g. exceeding the number of available scalers). Until now the test was failing in such cases with:
igt_kms-CRITICAL: Test assertion failure function
igt_display_commit_atomic, file../lib/igt_kms.c:3490:
igt_kms-CRITICAL: Failed assertion: ret == 0
igt_kms-CRITICAL: Last errno: 22, Invalid argument
igt_kms-CRITICAL: error: -22 != 0With this change we will just note that the atomic commit is invalid and pass the test without causing random noise.
Quoted 8 lines
I was about to object strongly, but thinking about it further, I think this whole subtest makes no sense. We have a ton of tests for planes, and if the targeted HW does not have support for CRCs, then it should be emulated using pipe writeback or using chamelium as a source of CRC.
Anyway, fixing this test would require a loop of atomic tries until a suitable configuration would be found, until then, I would rather skip than give the idea that the test could test anything.
You would get a valid configuration most of the runs. It looks like the test was originally coined as "maybe we hit some real issue sometime" as exhaustive testing of all valid configurations is impossible.
Quoted 3 lines
In summary, either:
- nuke the subtest
I was thinking about it, but prefered to have someone else say that aloud.
Quoted 1 line
- make it skip upon atomic check failure
You would get a random skip flip-floper. This would make many people quite grumpy.
Quoted 1 line
- fix it by looking for valid configurations
Better to nuke it than to throw even more complexity at it.
Quoted 1 line
I am just against the idea of passing a test without it doing anything.
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Patchwork
CI[igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] tests/kms_chamelium: Don't use CCS modifiers in random plane setup
In reply to Arkadiusz Hiler== Series Details ==
== Series Details ==
Series: series starting with [i-g-t,1/2] tests/kms_chamelium: Don't use CCS modifiers in random plane setup
URL : https://patchwork.freedesktop.org/series/74635/
State : success
== Summary ==
CI Bug Log - changes from IGT_5506 -> IGTPW_4296
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/index.html
Known issues
------------
Here are the changes found in IGTPW_4296 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live@execlists:
- fi-glk-dsi: [PASS][1] -> [INCOMPLETE][2] ([i915#1430] / [i915#58] / [k.org#198133])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/fi-glk-dsi/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/fi-glk-dsi/igt@i915_selftest@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@active:
- fi-bxt-dsi: [DMESG-FAIL][3] ([i915#666]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/fi-bxt-dsi/igt@i915_selftest@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/fi-bxt-dsi/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@execlists:
- fi-skl-6770hq: [INCOMPLETE][5] ([i915#1430]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/fi-skl-6770hq/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/fi-skl-6770hq/igt@i915_selftest@[email protected]
[i915#1430]: https://gitlab.freedesktop.org/drm/intel/issues/1430
[i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58
[i915#666]: https://gitlab.freedesktop.org/drm/intel/issues/666
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
Participating hosts (47 -> 40)
------------------------------
Missing (7): fi-kbl-soraka fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-elk-e7500 fi-kbl-7560u fi-byt-clapper
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5506 -> IGTPW_4296
CI-20190529: 20190529
CI_DRM_8126: 2bd9e989a5653d4cd710e9dd2b42b0a080f1add8 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_4296: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/index.html
IGT_5506: 59fd8a0d01dac58dc6c7d86ef391ed4393ab5aae @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Patchwork
CI[igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/2] tests/kms_chamelium: Don't use CCS modifiers in random plane setup
In reply to Arkadiusz Hiler== Series Details ==
== Series Details ==
Series: series starting with [i-g-t,1/2] tests/kms_chamelium: Don't use CCS modifiers in random plane setup
URL : https://patchwork.freedesktop.org/series/74635/
State : success
== Summary ==
CI Bug Log - changes from IGT_5506_full -> IGTPW_4296_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/index.html
Known issues
------------
Here are the changes found in IGTPW_4296_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@rcs0-s3:
- shard-apl: [PASS][1] -> [DMESG-WARN][2] ([i915#180]) +3 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-apl4/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-apl8/igt@[email protected]
* igt@gem_ctx_persistence@legacy-engines-mixed-process@vebox:
- shard-apl: [PASS][3] -> [FAIL][4] ([i915#679])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-apl4/igt@gem_ctx_persistence@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-apl1/igt@gem_ctx_persistence@[email protected]
* igt@gem_exec_balancer@smoke:
- shard-iclb: [PASS][5] -> [SKIP][6] ([fdo#110854])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb4/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb7/igt@[email protected]
* igt@gem_exec_schedule@implicit-both-bsd1:
- shard-iclb: [PASS][7] -> [SKIP][8] ([fdo#109276] / [i915#677])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb1/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb3/igt@[email protected]
* igt@gem_exec_schedule@pi-common-bsd:
- shard-iclb: [PASS][9] -> [SKIP][10] ([i915#677]) +2 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb5/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb4/igt@[email protected]
* igt@gem_exec_schedule@promotion-bsd1:
- shard-iclb: [PASS][11] -> [SKIP][12] ([fdo#109276]) +17 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb2/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb8/igt@[email protected]
* igt@gem_exec_schedule@reorder-wide-bsd:
- shard-iclb: [PASS][13] -> [SKIP][14] ([fdo#112146]) +3 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb8/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb4/igt@[email protected]
* igt@gem_workarounds@suspend-resume-fd:
- shard-kbl: [PASS][15] -> [DMESG-WARN][16] ([i915#180]) +3 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-kbl1/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-kbl1/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-kbl: [PASS][17] -> [DMESG-WARN][18] ([i915#716])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-kbl4/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-kbl7/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [PASS][19] -> [FAIL][20] ([i915#454])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb5/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb4/igt@[email protected]
* igt@i915_pm_rpm@fences:
- shard-tglb: [PASS][21] -> [SKIP][22] ([i915#1316])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-tglb6/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-tglb8/igt@[email protected]
- shard-iclb: [PASS][23] -> [SKIP][24] ([i915#1316])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb5/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb6/igt@[email protected]
- shard-hsw: [PASS][25] -> [SKIP][26] ([fdo#109271])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-hsw6/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-hsw1/igt@[email protected]
- shard-glk: [PASS][27] -> [SKIP][28] ([fdo#109271])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-glk2/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-glk1/igt@[email protected]
* igt@i915_pm_rps@waitboost:
- shard-iclb: [PASS][29] -> [FAIL][30] ([i915#413])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb7/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb8/igt@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-hsw: [PASS][31] -> [INCOMPLETE][32] ([i915#61])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-hsw2/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-hsw4/igt@[email protected]
* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-glk: [PASS][33] -> [FAIL][34] ([i915#899])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-glk9/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-glk8/igt@[email protected]
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [PASS][35] -> [SKIP][36] ([fdo#109642] / [fdo#111068])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb2/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb7/igt@[email protected]
* igt@kms_psr@psr2_suspend:
- shard-iclb: [PASS][37] -> [SKIP][38] ([fdo#109441]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb2/igt@kms_psr@psr2_suspend.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb1/igt@kms_psr@psr2_suspend.html
* igt@kms_setmode@basic:
- shard-kbl: [PASS][39] -> [FAIL][40] ([i915#31])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-kbl7/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-kbl4/igt@[email protected]
* igt@kms_universal_plane@universal-plane-pipe-c-functional:
- shard-glk: [PASS][41] -> [FAIL][42] ([i915#331])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-glk3/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-glk7/igt@[email protected]
- shard-kbl: [PASS][43] -> [FAIL][44] ([i915#331])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-kbl7/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-kbl1/igt@[email protected]
- shard-apl: [PASS][45] -> [FAIL][46] ([i915#331])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-apl8/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-apl7/igt@[email protected]
* igt@perf_pmu@busy-vcs1:
- shard-iclb: [PASS][47] -> [SKIP][48] ([fdo#112080]) +11 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb4/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb6/igt@[email protected]
#### Possible fixes ####
* igt@gem_busy@busy-vcs1:
- shard-iclb: [SKIP][49] ([fdo#112080]) -> [PASS][50] +17 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb6/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb1/igt@[email protected]
* igt@gem_ctx_persistence@close-replace-race:
- shard-iclb: [INCOMPLETE][51] ([i915#1402]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb4/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb2/igt@[email protected]
* igt@gem_ctx_shared@exec-single-timeline-bsd:
- shard-iclb: [SKIP][53] ([fdo#110841]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb1/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb6/igt@[email protected]
* igt@gem_exec_schedule@implicit-both-bsd:
- shard-iclb: [SKIP][55] ([i915#677]) -> [PASS][56] +1 similar issue
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb1/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb8/igt@[email protected]
* igt@gem_exec_schedule@in-order-bsd:
- shard-iclb: [SKIP][57] ([fdo#112146]) -> [PASS][58] +3 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb2/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb3/igt@[email protected]
* igt@gem_exec_whisper@basic-fds-priority:
- shard-tglb: [INCOMPLETE][59] ([i915#1401]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-tglb6/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-tglb3/igt@[email protected]
* igt@gem_ppgtt@flink-and-close-vma-leak:
- shard-glk: [FAIL][61] ([i915#644]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-glk2/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-glk2/igt@[email protected]
* igt@gem_softpin@noreloc-s3:
- shard-hsw: [INCOMPLETE][63] ([i915#61]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-hsw5/igt@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-hsw4/igt@[email protected]
* igt@i915_suspend@debugfs-reader:
- shard-apl: [DMESG-WARN][65] ([i915#180]) -> [PASS][66] +3 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-apl2/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-apl3/igt@[email protected]
* igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy:
- shard-glk: [FAIL][67] ([i915#72]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-glk1/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-glk5/igt@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-kbl: [DMESG-WARN][69] ([i915#180]) -> [PASS][70] +1 similar issue
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-kbl2/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-kbl4/igt@[email protected]
* igt@kms_psr2_su@page_flip:
- shard-iclb: [SKIP][71] ([fdo#109642] / [fdo#111068]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb6/igt@kms_psr2_su@page_flip.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb2/igt@kms_psr2_su@page_flip.html
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [SKIP][73] ([fdo#109441]) -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb7/igt@kms_psr@psr2_cursor_mmap_cpu.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][75] ([i915#31]) -> [PASS][76]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-apl3/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-apl6/igt@[email protected]
* igt@prime_vgem@fence-wait-bsd2:
- shard-iclb: [SKIP][77] ([fdo#109276]) -> [PASS][78] +14 similar issues
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-iclb8/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-iclb4/igt@[email protected]
#### Warnings ####
* igt@runner@aborted:
- shard-kbl: ([FAIL][79], [FAIL][80]) ([i915#1389] / [i915#1402] / [i915#92]) -> ([FAIL][81], [FAIL][82], [FAIL][83]) ([i915#1389] / [i915#1402] / [i915#716] / [i915#92])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-kbl2/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-kbl1/igt@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-kbl7/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-kbl6/igt@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-kbl2/igt@[email protected]
- shard-apl: ([FAIL][84], [FAIL][85]) ([fdo#103927] / [i915#1402]) -> [FAIL][86] ([fdo#103927])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-apl2/igt@[email protected]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5506/shard-apl4/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/shard-apl3/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110789]: https://bugs.freedesktop.org/show_bug.cgi?id=110789
[fdo#110841]: https://bugs.freedesktop.org/show_bug.cgi?id=110841
[fdo#110854]: https://bugs.freedesktop.org/show_bug.cgi?id=110854
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
[fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146
[i915#1316]: https://gitlab.freedesktop.org/drm/intel/issues/1316
[i915#1389]: https://gitlab.freedesktop.org/drm/intel/issues/1389
[i915#1401]: https://gitlab.freedesktop.org/drm/intel/issues/1401
[i915#1402]: https://gitlab.freedesktop.org/drm/intel/issues/1402
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#331]: https://gitlab.freedesktop.org/drm/intel/issues/331
[i915#413]: https://gitlab.freedesktop.org/drm/intel/issues/413
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#478]: https://gitlab.freedesktop.org/drm/intel/issues/478
[i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61
[i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644
[i915#677]: https://gitlab.freedesktop.org/drm/intel/issues/677
[i915#679]: https://gitlab.freedesktop.org/drm/intel/issues/679
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#72]: https://gitlab.freedesktop.org/drm/intel/issues/72
[i915#899]: https://gitlab.freedesktop.org/drm/intel/issues/899
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
Participating hosts (8 -> 8)
------------------------------
No changes in participating hosts
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5506 -> IGTPW_4296
CI-20190529: 20190529
CI_DRM_8126: 2bd9e989a5653d4cd710e9dd2b42b0a080f1add8 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_4296: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/index.html
IGT_5506: 59fd8a0d01dac58dc6c7d86ef391ed4393ab5aae @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4296/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev