lib/igt_chamelium.c: Skip test if chamelium
PATCH 1/1 lib/igt_chamelium.c: Skip test if chamelium
If chamelium is not present at the specified IP in the igtrc file, tests should be skipped instead of failing.
Adding a change to skip tests on any network related issue and assert on any other issue.
--- lib/igt_chamelium.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
lib/igt_chamelium.c +6 -3
@@ -344,9 +344,12 @@ static xmlrpc_value *chamelium_rpc(struct chamelium *chamelium, format_str, va_args);va_end (va_args); -igt_assert_f (!chamelium->env.fault_occurred, -"Chamelium RPC call failed: %s\n" , - chamelium->env.fault_string); +if (chamelium->env.fault_code ==XMLRPC_NETWORK_ERROR ) +igt_skip ("Chamelium not found at specified IP" ); +else +igt_assert_f (!chamelium->env.fault_occurred, +"Chamelium RPC call failed: %s\n" , + chamelium->env.fault_string);return res; }
Signature · 6 lines
2.7.4 _______________________________________________ igt-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 15 lines · Kunal Joshi
If chamelium is not present at the specified IP in the igtrc file, tests should be skipped instead of failing.
Adding a change to skip tests on any network related issue and assert on any other issue.Signed-off-by Kunal Joshi <[email protected]>--- lib/igt_chamelium.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)lib/igt_chamelium.c +0
-0
lib/igt_chamelium.c static xmlrpc_value *chamelium_rpc(struct chamelium *chamelium, · line 348
Quoted 8 lines
lib/igt_chamelium.c +2
-3@@ -344,9 +344,12 @@ static xmlrpc_value *chamelium_rpc(struct chamelium *chamelium, format_str, va_args);va_end (va_args); -igt_assert_f (!chamelium->env.fault_occurred, -"Chamelium RPC call failed: %s\n" , - chamelium->env.fault_string); +if (chamelium->env.fault_code ==XMLRPC_NETWORK_ERROR ) +igt_skip ("Chamelium not found at specified IP" );
This message is misleading when the network just did not come back.
I prefer the fact that the test fails as it draws attention to either a mis-configured igtrc, a network problem, or a chamelium problem.
What is your rationale for this change? Skips are considered as failure anyway from our bug tracking point of view.
Martin
lib/igt_chamelium.c static xmlrpc_value *chamelium_rpc(struct chamelium *chamelium, · line 355
Quoted 8 lines
lib/igt_chamelium.c +4
-0+else +igt_assert_f (!chamelium->env.fault_occurred, +"Chamelium RPC call failed: %s\n" , + chamelium->env.fault_string);return res; }
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 27 lines · Martin Peres
Quoted 15 lines · Kunal Joshi
If chamelium is not present at the specified IP in the igtrc file, tests should be skipped instead of failing.
Adding a change to skip tests on any network related issue and assert on any other issue.Signed-off-by Kunal Joshi <[email protected]>--- lib/igt_chamelium.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)lib/igt_chamelium.c +0
-0lib/igt_chamelium.c static xmlrpc_value *chamelium_rpc(struct chamelium *chamelium, · line 348
Quoted 8 lines
lib/igt_chamelium.c +2
-3@@ -344,9 +344,12 @@ static xmlrpc_value *chamelium_rpc(struct chamelium *chamelium, format_str, va_args);va_end (va_args); -igt_assert_f (!chamelium->env.fault_occurred, -"Chamelium RPC call failed: %s\n" , - chamelium->env.fault_string); +if (chamelium->env.fault_code ==XMLRPC_NETWORK_ERROR ) +igt_skip ("Chamelium not found at specified IP" );This message is misleading when the network just did not come back.
Quoted 3 lines
I prefer the fact that the test fails as it draws attention to either a mis-configured igtrc, a network problem, or a chamelium problem.
Would it be fine if I modify the log to state the cause more explicitly? Would you also suggest waiting for the xml-rpc timeout, to assure that the problem isn't with network not coming back?
Is there a better way I can handle this?
Quoted 3 lines
What is your rationale for this change? Skips are considered as failure anyway from our bug tracking point of view.
If we happen to use igt_chamelium library with some other tests, then skipping could be more appropriate than failing?
For Ex: In PSR tests we skip the test if edp panel is not present rather than failing.
The same way I think the test should be skipped if chamelium is not present.
Quoted 10 lines
Martin
lib/igt_chamelium.c static xmlrpc_value *chamelium_rpc(struct chamelium *chamelium, · line 355
Quoted 8 lines
lib/igt_chamelium.c +4
-0+else +igt_assert_f (!chamelium->env.fault_occurred, +"Chamelium RPC call failed: %s\n" , + chamelium->env.fault_string);return res; }
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 28 lines · Kunal Joshi
Quoted 27 lines · Martin Peres
Quoted 15 lines · Kunal Joshi
If chamelium is not present at the specified IP in the igtrc file, tests should be skipped instead of failing.
Adding a change to skip tests on any network related issue and assert on any other issue.Signed-off-by Kunal Joshi <[email protected]>--- lib/igt_chamelium.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)lib/igt_chamelium.c +0
-0lib/igt_chamelium.c static xmlrpc_value *chamelium_rpc(struct chamelium *chamelium, · line 348
Quoted 8 lines
lib/igt_chamelium.c +2
-3@@ -344,9 +344,12 @@ static xmlrpc_value *chamelium_rpc(struct chamelium *chamelium, format_str, va_args);va_end (va_args); -igt_assert_f (!chamelium->env.fault_occurred, -"Chamelium RPC call failed: %s\n" , - chamelium->env.fault_string); +if (chamelium->env.fault_code ==XMLRPC_NETWORK_ERROR ) +igt_skip ("Chamelium not found at specified IP" );This message is misleading when the network just did not come back.
Quoted 7 lines
Quoted 3 lines
I prefer the fact that the test fails as it draws attention to either a mis-configured igtrc, a network problem, or a chamelium problem.
Would it be fine if I modify the log to state the cause more explicitly? Would you also suggest waiting for the xml-rpc timeout, to assure that the problem isn't with network not coming back?
Is there a better way I can handle this?
Yes, you could provide possible explanations there (A. the device is not present or B. the network is down.
Quoted 9 lines
Quoted 3 lines
What is your rationale for this change? Skips are considered as failure anyway from our bug tracking point of view.
If we happen to use
igt_chameliumlibrary with some other tests, then skipping could be more appropriate than failing?
For Ex: In PSR tests we skip the test if edp panel is not present rather than failing.
The same way I think the test should be skipped if chamelium is not present.
I agree with the logic that if chamelium is not present, the tests should skip. However, if the user has said "Chamelium is at this IP address" but the test can't connect to it, then I would at least consider this a failure in deploying chamelium.
Martin
Quoted 10 lines
Quoted 10 lines
Martin
lib/igt_chamelium.c static xmlrpc_value *chamelium_rpc(struct chamelium *chamelium, · line 355
Quoted 8 lines
lib/igt_chamelium.c +4
-0+else +igt_assert_f (!chamelium->env.fault_occurred, +"Chamelium RPC call failed: %s\n" , + chamelium->env.fault_string);return res; }
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Patchwork
CI[igt-dev] ✓ Fi.CI.BAT: success for lib/igt_chamelium.c: Skip test if chamelium
In reply to Kunal Joshi== Series Details ==
== Series Details ==
Series: lib/igt_chamelium.c: Skip test if chamelium
URL : https://patchwork.freedesktop.org/series/70823/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7549 -> IGTPW_3854
====================================================
Summary
-------
**WARNING**
Minor unknown changes coming with IGTPW_3854 need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in IGTPW_3854, 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_3854/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_3854:
### IGT changes ###
#### Warnings ####
* igt@kms_chamelium@dp-hpd-fast:
- fi-cml-u2: [FAIL][1] ([i915#410]) -> [SKIP][2] +8 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/fi-cml-u2/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/fi-cml-u2/igt@[email protected]
Known issues
------------
Here are the changes found in IGTPW_3854 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@module-reload:
- fi-skl-6770hq: [PASS][3] -> [FAIL][4] ([i915#178])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/fi-skl-6770hq/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/fi-skl-6770hq/igt@[email protected]
* igt@i915_selftest@live_blt:
- fi-byt-j1900: [PASS][5] -> [DMESG-FAIL][6] ([i915#725])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/fi-byt-j1900/igt@i915_selftest@live_blt.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/fi-byt-j1900/igt@i915_selftest@live_blt.html
#### Possible fixes ####
* igt@gem_exec_gttfill@basic:
- {fi-tgl-u}: [INCOMPLETE][7] ([fdo#111593]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/fi-tgl-u/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/fi-tgl-u/igt@[email protected]
* igt@i915_selftest@live_blt:
- fi-ivb-3770: [DMESG-FAIL][9] ([i915#563]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/fi-ivb-3770/igt@i915_selftest@live_blt.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/fi-ivb-3770/igt@i915_selftest@live_blt.html
* igt@i915_selftest@live_hangcheck:
- fi-icl-u3: [INCOMPLETE][11] ([fdo#108569] / [i915#140]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/fi-icl-u3/igt@i915_selftest@live_hangcheck.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/fi-icl-u3/igt@i915_selftest@live_hangcheck.html
#### Warnings ####
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-kbl-x1275: [DMESG-WARN][13] ([i915#62] / [i915#92]) -> [DMESG-WARN][14] ([i915#62] / [i915#92] / [i915#95]) +6 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/fi-kbl-x1275/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/fi-kbl-x1275/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][15] ([fdo#111096] / [i915#323]) -> [FAIL][16] ([fdo#111407])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/fi-kbl-7500u/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/fi-kbl-7500u/igt@[email protected]
* igt@kms_cursor_legacy@basic-flip-after-cursor-legacy:
- fi-kbl-x1275: [DMESG-WARN][17] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][18] ([i915#62] / [i915#92]) +6 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/fi-kbl-x1275/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/fi-kbl-x1275/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#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
[fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
[fdo#111593]: https://bugs.freedesktop.org/show_bug.cgi?id=111593
[i915#140]: https://gitlab.freedesktop.org/drm/intel/issues/140
[i915#178]: https://gitlab.freedesktop.org/drm/intel/issues/178
[i915#323]: https://gitlab.freedesktop.org/drm/intel/issues/323
[i915#410]: https://gitlab.freedesktop.org/drm/intel/issues/410
[i915#563]: https://gitlab.freedesktop.org/drm/intel/issues/563
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#725]: https://gitlab.freedesktop.org/drm/intel/issues/725
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (48 -> 44)
------------------------------
Additional (3): fi-hsw-4770r fi-tgl-y fi-cfl-guc
Missing (7): fi-ilk-m540 fi-bsw-n3050 fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus fi-snb-2600
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5346 -> IGTPW_3854
CI-20190529: 20190529
CI_DRM_7549: 9573e1b7d1cb54cc984cf5c4f93a743641d868da @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3854: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/index.html
IGT_5346: 466b0e6cbcbaccff012b484d1fd7676364b37b93 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Patchwork
CI[igt-dev] ✗ Fi.CI.IGT: failure for lib/igt_chamelium.c: Skip test if chamelium
In reply to Kunal Joshi== Series Details ==
== Series Details ==
Series: lib/igt_chamelium.c: Skip test if chamelium
URL : https://patchwork.freedesktop.org/series/70823/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7549_full -> IGTPW_3854_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_3854_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in IGTPW_3854_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_3854/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_3854_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_ctx_persistence@processes:
- shard-iclb: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb3/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb1/igt@[email protected]
Known issues
------------
Here are the changes found in IGTPW_3854_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@bcs0-s3:
- shard-apl: [PASS][3] -> [DMESG-WARN][4] ([i915#180]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-apl8/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-apl1/igt@[email protected]
* igt@gem_ctx_persistence@vcs1-mixed-process:
- shard-iclb: [PASS][5] -> [SKIP][6] ([fdo#109276] / [fdo#112080])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb1/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb8/igt@[email protected]
* igt@gem_ctx_shared@exec-single-timeline-bsd:
- shard-iclb: [PASS][7] -> [SKIP][8] ([fdo#110841])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb5/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb1/igt@[email protected]
* igt@gem_exec_balancer@nop:
- shard-tglb: [PASS][9] -> [INCOMPLETE][10] ([fdo#111736])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-tglb6/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-tglb5/igt@[email protected]
* igt@gem_exec_schedule@deep-bsd2:
- shard-iclb: [PASS][11] -> [SKIP][12] ([fdo#109276]) +6 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb1/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb3/igt@[email protected]
* igt@gem_exec_schedule@preempt-queue-bsd:
- shard-iclb: [PASS][13] -> [SKIP][14] ([fdo#112146]) +3 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb3/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb2/igt@[email protected]
* igt@gem_persistent_relocs@forked-faulting-reloc-thrash-inactive:
- shard-tglb: [PASS][15] -> [TIMEOUT][16] ([i915#530])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-tglb8/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-tglb2/igt@[email protected]
* igt@gem_ppgtt@flink-and-close-vma-leak:
- shard-glk: [PASS][17] -> [FAIL][18] ([i915#644])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-glk7/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-glk7/igt@[email protected]
* igt@gem_userptr_blits@dmabuf-sync:
- shard-snb: [PASS][19] -> [DMESG-WARN][20] ([fdo#111870]) +2 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-snb4/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-snb5/igt@[email protected]
* igt@i915_pm_rpm@modeset-stress-extra-wait:
- shard-glk: [PASS][21] -> [DMESG-WARN][22] ([i915#118] / [i915#95])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-glk5/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-glk8/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-128x42-offscreen:
- shard-hsw: [PASS][23] -> [DMESG-WARN][24] ([IGT#6])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-hsw8/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-hsw6/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [PASS][25] -> [DMESG-WARN][26] ([i915#180]) +3 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-kbl3/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-kbl4/igt@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-hsw: [PASS][27] -> [INCOMPLETE][28] ([i915#61])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-hsw5/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-hsw1/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-onoff:
- shard-tglb: [PASS][29] -> [INCOMPLETE][30] ([i915#435] / [i915#474] / [i915#667])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-tglb2/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-tglb2/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt:
- shard-glk: [PASS][31] -> [FAIL][32] ([i915#49]) +1 similar issue
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-glk9/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-glk9/igt@[email protected]
- shard-apl: [PASS][33] -> [FAIL][34] ([i915#49])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-apl1/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-apl3/igt@[email protected]
- shard-kbl: [PASS][35] -> [FAIL][36] ([i915#49])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-kbl7/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-kbl1/igt@[email protected]
* igt@kms_psr2_su@page_flip:
- shard-iclb: [PASS][37] -> [SKIP][38] ([fdo#109642] / [fdo#111068])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb2/igt@kms_psr2_su@page_flip.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb4/igt@kms_psr2_su@page_flip.html
* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-iclb: [PASS][39] -> [SKIP][40] ([fdo#109441])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb5/igt@kms_psr@psr2_sprite_mmap_gtt.html
* igt@perf_pmu@idle-vcs1:
- shard-iclb: [PASS][41] -> [SKIP][42] ([fdo#112080]) +2 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb4/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb5/igt@[email protected]
#### Possible fixes ####
* igt@gem_ctx_isolation@vcs1-s3:
- shard-tglb: [INCOMPLETE][43] ([i915#456]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-tglb3/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-tglb1/igt@[email protected]
* igt@gem_ctx_persistence@vcs1-persistence:
- shard-iclb: [SKIP][45] ([fdo#109276] / [fdo#112080]) -> [PASS][46] +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb5/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb2/igt@[email protected]
* igt@gem_eio@reset-stress:
- shard-snb: [FAIL][47] ([i915#232]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-snb2/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-snb7/igt@[email protected]
* igt@gem_exec_balancer@smoke:
- shard-iclb: [SKIP][49] ([fdo#110854]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb8/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb4/igt@[email protected]
* igt@gem_exec_schedule@preempt-other-chain-bsd:
- shard-iclb: [SKIP][51] ([fdo#112146]) -> [PASS][52] +1 similar issue
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb1/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb5/igt@[email protected]
* igt@gem_exec_schedule@preempt-queue-bsd1:
- shard-iclb: [SKIP][53] ([fdo#109276]) -> [PASS][54] +17 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb8/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb4/igt@[email protected]
* igt@gem_persistent_relocs@forked-faulting-reloc-thrash-inactive:
- shard-snb: [TIMEOUT][55] ([i915#530]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-snb1/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-snb7/igt@[email protected]
* igt@gem_persistent_relocs@forked-interruptible-thrashing:
- shard-hsw: [FAIL][57] ([i915#520]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-hsw4/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-hsw2/igt@[email protected]
* igt@gem_persistent_relocs@forked-thrashing:
- shard-iclb: [TIMEOUT][59] ([i915#530]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb6/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb8/igt@[email protected]
* igt@gem_userptr_blits@map-fixed-invalidate-busy:
- shard-snb: [DMESG-WARN][61] ([fdo#111870]) -> [PASS][62] +2 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-snb4/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-snb4/igt@[email protected]
* igt@i915_selftest@mock_sanitycheck:
- shard-snb: [DMESG-WARN][63] ([i915#747]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-snb1/igt@i915_selftest@mock_sanitycheck.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-snb4/igt@i915_selftest@mock_sanitycheck.html
* igt@kms_color@pipe-a-gamma:
- shard-tglb: [FAIL][65] ([i915#71]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-tglb1/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-tglb8/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [DMESG-WARN][67] ([i915#180]) -> [PASS][68] +6 similar issues
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-kbl6/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-kbl2/igt@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-apl: [DMESG-WARN][69] ([i915#180]) -> [PASS][70] +1 similar issue
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-apl1/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-apl2/igt@[email protected]
- shard-snb: [DMESG-WARN][71] ([i915#42]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-snb2/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-snb4/igt@[email protected]
* igt@kms_flip@plain-flip-interruptible:
- shard-kbl: [INCOMPLETE][73] ([fdo#103665]) -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-kbl7/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-kbl4/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-indfb-draw-mmap-wc:
- shard-tglb: [INCOMPLETE][75] ([i915#474] / [i915#667]) -> [PASS][76]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-tglb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-indfb-draw-mmap-wc.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-tglb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-indfb-draw-mmap-wc.html
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][77] ([fdo#109642] / [fdo#111068]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb4/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb2/igt@[email protected]
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [SKIP][79] ([fdo#109441]) -> [PASS][80] +1 similar issue
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb6/igt@kms_psr@psr2_no_drrs.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
* igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend:
- shard-tglb: [INCOMPLETE][81] ([i915#460]) -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-tglb1/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-tglb7/igt@[email protected]
* igt@perf_pmu@busy-check-all-vcs1:
- shard-iclb: [SKIP][83] ([fdo#112080]) -> [PASS][84] +12 similar issues
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb5/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb4/igt@[email protected]
#### Warnings ####
* igt@gem_ctx_isolation@vcs1-nonpriv:
- shard-iclb: [SKIP][85] ([fdo#109276] / [fdo#112080]) -> [FAIL][86] ([IGT#28])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb8/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb4/igt@[email protected]
* igt@kms_dp_dsc@basic-dsc-enable-edp:
- shard-iclb: [SKIP][87] ([fdo#109349]) -> [DMESG-WARN][88] ([fdo#107724])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7549/shard-iclb5/igt@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/shard-iclb2/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[IGT#28]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/28
[IGT#6]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/6
[fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109349]: https://bugs.freedesktop.org/show_bug.cgi?id=109349
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[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#111736]: https://bugs.freedesktop.org/show_bug.cgi?id=111736
[fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
[fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
[fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#232]: https://gitlab.freedesktop.org/drm/intel/issues/232
[i915#42]: https://gitlab.freedesktop.org/drm/intel/issues/42
[i915#435]: https://gitlab.freedesktop.org/drm/intel/issues/435
[i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456
[i915#460]: https://gitlab.freedesktop.org/drm/intel/issues/460
[i915#474]: https://gitlab.freedesktop.org/drm/intel/issues/474
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#520]: https://gitlab.freedesktop.org/drm/intel/issues/520
[i915#530]: https://gitlab.freedesktop.org/drm/intel/issues/530
[i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61
[i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644
[i915#667]: https://gitlab.freedesktop.org/drm/intel/issues/667
[i915#71]: https://gitlab.freedesktop.org/drm/intel/issues/71
[i915#747]: https://gitlab.freedesktop.org/drm/intel/issues/747
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (11 -> 8)
------------------------------
Missing (3): pig-skl-6260u pig-glk-j5005 pig-hsw-4770r
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5346 -> IGTPW_3854
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_7549: 9573e1b7d1cb54cc984cf5c4f93a743641d868da @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3854: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/index.html
IGT_5346: 466b0e6cbcbaccff012b484d1fd7676364b37b93 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3854/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev