* [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts
@ 2020-12-04 19:50 Janusz Krzysztofik
2020-12-04 20:54 ` [igt-dev] ✓ Fi.CI.BAT: success for runner: Don't kill a test on taint if watching timeouts (rev2) Patchwork
` (4 more replies)
0 siblings, 5 replies; 15+ messages in thread
From: Janusz Krzysztofik @ 2020-12-04 19:50 UTC (permalink / raw)
To: igt-dev; +Cc: intel-gfx, Chris Wilson
We may still be interested in results of a test even if it has tainted
the kernel. On the other hand, we need to kill the test on taint if no
other means of killing it on a jam is active.
If abort on both kernel taint or a timeout is requested, decrease all
potential timeouts significantly while the taint is detected instead of
aborting immediately. However, report the taint as the reason of the
abort if a timeout decreased by the taint expires.
v2: Fix missing show_kernel_task_state() lost on rebase conflict
resolution (Chris - thanks!)
Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
---
runner/executor.c | 26 ++++++++++++++++++++------
1 file changed, 20 insertions(+), 6 deletions(-)
diff --git a/runner/executor.c b/runner/executor.c
index 1688ae41d..faf272d85 100644
--- a/runner/executor.c
+++ b/runner/executor.c
@@ -726,6 +726,8 @@ static const char *need_to_timeout(struct settings *settings,
double time_since_kill,
size_t disk_usage)
{
+ int decrease = 1;
+
if (killed) {
/*
* Timeout after being killed is a hardcoded amount
@@ -753,20 +755,32 @@ static const char *need_to_timeout(struct settings *settings,
}
/*
- * If we're configured to care about taints, kill the
- * test if there's a taint.
+ * If we're configured to care about taints,
+ * decrease timeouts in use if there's a taint,
+ * or kill the test if no timeouts have been requested.
*/
if (settings->abort_mask & ABORT_TAINT &&
- is_tainted(taints))
- return "Killing the test because the kernel is tainted.\n";
+ is_tainted(taints)) {
+ /* list of timeouts that may postpone immediate kill on taint */
+ if (settings->per_test_timeout || settings->inactivity_timeout)
+ decrease = 10;
+ else
+ return "Killing the test because the kernel is tainted.\n";
+ }
if (settings->per_test_timeout != 0 &&
- time_since_subtest > settings->per_test_timeout)
+ time_since_subtest > settings->per_test_timeout / decrease) {
+ if (decrease > 1)
+ return "Killing the test because the kernel is tainted.\n";
return show_kernel_task_state("Per-test timeout exceeded. Killing the current test with SIGQUIT.\n");
+ }
if (settings->inactivity_timeout != 0 &&
- time_since_activity > settings->inactivity_timeout)
+ time_since_activity > settings->inactivity_timeout / decrease ) {
+ if (decrease > 1)
+ return "Killing the test because the kernel is tainted.\n";
return show_kernel_task_state("Inactivity timeout exceeded. Killing the current test with SIGQUIT.\n");
+ }
if (disk_usage_limit_exceeded(settings, disk_usage))
return "Disk usage limit exceeded.\n";
--
2.21.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 15+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for runner: Don't kill a test on taint if watching timeouts (rev2)
2020-12-04 19:50 [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts Janusz Krzysztofik
@ 2020-12-04 20:54 ` Patchwork
2020-12-05 0:13 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
` (3 subsequent siblings)
4 siblings, 0 replies; 15+ messages in thread
From: Patchwork @ 2020-12-04 20:54 UTC (permalink / raw)
To: Janusz Krzysztofik; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 3754 bytes --]
== Series Details ==
Series: runner: Don't kill a test on taint if watching timeouts (rev2)
URL : https://patchwork.freedesktop.org/series/84577/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9444 -> IGTPW_5250
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/index.html
Known issues
------------
Here are the changes found in IGTPW_5250 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/CI_DRM_9444/fi-tgl-u2/igt@gem_exec_suspend@basic-s3.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/fi-tgl-u2/igt@gem_exec_suspend@basic-s3.html
* igt@i915_selftest@live@execlists:
- fi-icl-y: [PASS][3] -> [INCOMPLETE][4] ([i915#1037] / [i915#2276])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/fi-icl-y/igt@i915_selftest@live@execlists.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/fi-icl-y/igt@i915_selftest@live@execlists.html
* igt@i915_selftest@live@gt_heartbeat:
- fi-cfl-8109u: [PASS][5] -> [DMESG-FAIL][6] ([i915#2291] / [i915#541])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/fi-cfl-8109u/igt@i915_selftest@live@gt_heartbeat.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/fi-cfl-8109u/igt@i915_selftest@live@gt_heartbeat.html
* igt@prime_vgem@basic-userptr:
- fi-tgl-y: [PASS][7] -> [DMESG-WARN][8] ([i915#402]) +2 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/fi-tgl-y/igt@prime_vgem@basic-userptr.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/fi-tgl-y/igt@prime_vgem@basic-userptr.html
#### Possible fixes ####
* igt@gem_exec_gttfill@basic:
- fi-kbl-8809g: [INCOMPLETE][9] ([i915#2405]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/fi-kbl-8809g/igt@gem_exec_gttfill@basic.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/fi-kbl-8809g/igt@gem_exec_gttfill@basic.html
* igt@prime_self_import@basic-with_one_bo_two_files:
- fi-tgl-y: [DMESG-WARN][11] ([i915#402]) -> [PASS][12] +2 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/fi-tgl-y/igt@prime_self_import@basic-with_one_bo_two_files.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/fi-tgl-y/igt@prime_self_import@basic-with_one_bo_two_files.html
[i915#1037]: https://gitlab.freedesktop.org/drm/intel/issues/1037
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#2276]: https://gitlab.freedesktop.org/drm/intel/issues/2276
[i915#2291]: https://gitlab.freedesktop.org/drm/intel/issues/2291
[i915#2405]: https://gitlab.freedesktop.org/drm/intel/issues/2405
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#541]: https://gitlab.freedesktop.org/drm/intel/issues/541
Participating hosts (43 -> 38)
------------------------------
Missing (5): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-dg1-1 fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5881 -> IGTPW_5250
CI-20190529: 20190529
CI_DRM_9444: cee8f6ace633b555c64b14938577e6da02710a0b @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5250: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/index.html
IGT_5881: 10d4e2e9177eb747b9f2ab9122e3ab60e91654fb @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/index.html
[-- Attachment #1.2: Type: text/html, Size: 4559 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 15+ messages in thread
* [igt-dev] ✗ Fi.CI.IGT: failure for runner: Don't kill a test on taint if watching timeouts (rev2)
2020-12-04 19:50 [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts Janusz Krzysztofik
2020-12-04 20:54 ` [igt-dev] ✓ Fi.CI.BAT: success for runner: Don't kill a test on taint if watching timeouts (rev2) Patchwork
@ 2020-12-05 0:13 ` Patchwork
2020-12-07 10:46 ` Janusz Krzysztofik
2020-12-07 13:09 ` [igt-dev] " Petri Latvala
` (2 subsequent siblings)
4 siblings, 1 reply; 15+ messages in thread
From: Patchwork @ 2020-12-05 0:13 UTC (permalink / raw)
To: Janusz Krzysztofik; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 21124 bytes --]
== Series Details ==
Series: runner: Don't kill a test on taint if watching timeouts (rev2)
URL : https://patchwork.freedesktop.org/series/84577/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9444_full -> IGTPW_5250_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_5250_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_5250_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_5250/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_5250_full:
### IGT changes ###
#### Possible regressions ####
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-edp:
- shard-iclb: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb7/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-edp.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb2/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-edp.html
- shard-tglb: [PASS][3] -> [FAIL][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb5/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-edp.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb2/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-edp.html
Known issues
------------
Here are the changes found in IGTPW_5250_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_whisper@basic-queues:
- shard-glk: [PASS][5] -> [DMESG-WARN][6] ([i915#118] / [i915#95]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk1/igt@gem_exec_whisper@basic-queues.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk3/igt@gem_exec_whisper@basic-queues.html
* igt@i915_pm_rpm@debugfs-forcewake-user:
- shard-hsw: [PASS][7] -> [SKIP][8] ([fdo#109271])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-hsw1/igt@i915_pm_rpm@debugfs-forcewake-user.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw1/igt@i915_pm_rpm@debugfs-forcewake-user.html
- shard-kbl: [PASS][9] -> [SKIP][10] ([fdo#109271])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl2/igt@i915_pm_rpm@debugfs-forcewake-user.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl3/igt@i915_pm_rpm@debugfs-forcewake-user.html
- shard-iclb: [PASS][11] -> [SKIP][12] ([i915#579])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb6/igt@i915_pm_rpm@debugfs-forcewake-user.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb5/igt@i915_pm_rpm@debugfs-forcewake-user.html
- shard-tglb: [PASS][13] -> [SKIP][14] ([i915#579])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb2/igt@i915_pm_rpm@debugfs-forcewake-user.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb8/igt@i915_pm_rpm@debugfs-forcewake-user.html
- shard-apl: [PASS][15] -> [SKIP][16] ([fdo#109271])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl4/igt@i915_pm_rpm@debugfs-forcewake-user.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl8/igt@i915_pm_rpm@debugfs-forcewake-user.html
- shard-glk: [PASS][17] -> [SKIP][18] ([fdo#109271])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk7/igt@i915_pm_rpm@debugfs-forcewake-user.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk3/igt@i915_pm_rpm@debugfs-forcewake-user.html
* igt@kms_async_flips@test-time-stamp:
- shard-tglb: [PASS][19] -> [FAIL][20] ([i915#2574])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb2/igt@kms_async_flips@test-time-stamp.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb1/igt@kms_async_flips@test-time-stamp.html
* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
- shard-hsw: [PASS][21] -> [FAIL][22] ([i915#96])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-hsw6/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw6/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-blt:
- shard-glk: [PASS][23] -> [FAIL][24] ([i915#49])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk5/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-blt.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk4/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-blt.html
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: [PASS][25] -> [SKIP][26] ([fdo#109441])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb8/igt@kms_psr@psr2_cursor_plane_move.html
* igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend:
- shard-tglb: [PASS][27] -> [INCOMPLETE][28] ([i915#1436] / [i915#1602] / [i915#1887] / [i915#1982] / [i915#2411])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb2/igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb8/igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend.html
* igt@perf@polling-parameterized:
- shard-glk: [PASS][29] -> [FAIL][30] ([i915#1542])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk8/igt@perf@polling-parameterized.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk5/igt@perf@polling-parameterized.html
#### Possible fixes ####
* igt@gem_ctx_isolation@preservation-s3@rcs0:
- shard-apl: [INCOMPLETE][31] ([i915#1602] / [i915#2635]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl3/igt@gem_ctx_isolation@preservation-s3@rcs0.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl3/igt@gem_ctx_isolation@preservation-s3@rcs0.html
- shard-kbl: [INCOMPLETE][33] ([i915#1602] / [i915#794]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl2/igt@gem_ctx_isolation@preservation-s3@rcs0.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl2/igt@gem_ctx_isolation@preservation-s3@rcs0.html
- shard-iclb: [INCOMPLETE][35] ([i915#1373] / [i915#1602]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb1/igt@gem_ctx_isolation@preservation-s3@rcs0.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb1/igt@gem_ctx_isolation@preservation-s3@rcs0.html
- shard-tglb: [INCOMPLETE][37] ([i915#1373] / [i915#1436] / [i915#1602] / [i915#1887] / [i915#2411]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb8/igt@gem_ctx_isolation@preservation-s3@rcs0.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb5/igt@gem_ctx_isolation@preservation-s3@rcs0.html
* igt@gem_exec_reloc@basic-many-active@rcs0:
- shard-glk: [FAIL][39] ([i915#2389]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk3/igt@gem_exec_reloc@basic-many-active@rcs0.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk2/igt@gem_exec_reloc@basic-many-active@rcs0.html
* igt@gem_softpin@noreloc-s3:
- shard-glk: [INCOMPLETE][41] ([i915#2199] / [i915#2405]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk6/igt@gem_softpin@noreloc-s3.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk8/igt@gem_softpin@noreloc-s3.html
* igt@i915_pm_dc@dc5-dpms:
- shard-iclb: [FAIL][43] ([i915#2745]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb7/igt@i915_pm_dc@dc5-dpms.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb3/igt@i915_pm_dc@dc5-dpms.html
- shard-glk: [FAIL][45] ([i915#2745]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk2/igt@i915_pm_dc@dc5-dpms.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk4/igt@i915_pm_dc@dc5-dpms.html
- shard-apl: [FAIL][47] ([i915#2745]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl1/igt@i915_pm_dc@dc5-dpms.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl1/igt@i915_pm_dc@dc5-dpms.html
- shard-kbl: [FAIL][49] ([i915#545]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl6/igt@i915_pm_dc@dc5-dpms.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl7/igt@i915_pm_dc@dc5-dpms.html
* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy:
- shard-hsw: [FAIL][51] ([i915#96]) -> [PASS][52] +1 similar issue
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-hsw1/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw2/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html
* igt@kms_flip@flip-vs-suspend@b-hdmi-a1:
- shard-hsw: [INCOMPLETE][53] ([i915#2055] / [i915#2295]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-hsw2/igt@kms_flip@flip-vs-suspend@b-hdmi-a1.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw6/igt@kms_flip@flip-vs-suspend@b-hdmi-a1.html
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-indfb-pgflip-blt:
- shard-glk: [FAIL][55] ([i915#49]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk7/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-indfb-pgflip-blt.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk3/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-indfb-pgflip-blt.html
* igt@kms_plane_lowres@pipe-b-tiling-yf:
- shard-kbl: [DMESG-WARN][57] ([i915#165] / [i915#180] / [i915#78]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl2/igt@kms_plane_lowres@pipe-b-tiling-yf.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl6/igt@kms_plane_lowres@pipe-b-tiling-yf.html
* igt@kms_psr@psr2_cursor_render:
- shard-iclb: [SKIP][59] ([fdo#109441]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb7/igt@kms_psr@psr2_cursor_render.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb2/igt@kms_psr@psr2_cursor_render.html
* igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend:
- shard-hsw: [INCOMPLETE][61] ([i915#2637]) -> [PASS][62] +1 similar issue
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-hsw6/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw2/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
- shard-kbl: [INCOMPLETE][63] ([i915#155]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl6/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl6/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
- shard-iclb: [INCOMPLETE][65] ([i915#1185]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb7/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb6/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
- shard-apl: [DMESG-WARN][67] ([i915#2635]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl1/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl6/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
- shard-glk: [INCOMPLETE][69] ([i915#2635]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk2/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk3/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
* igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
- shard-tglb: [DMESG-WARN][71] ([i915#1602] / [i915#2411]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb1/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb3/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
#### Warnings ####
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-iclb: [SKIP][73] ([i915#588]) -> [SKIP][74] ([i915#658])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb2/igt@i915_pm_dc@dc3co-vpb-simulation.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb6/igt@i915_pm_dc@dc3co-vpb-simulation.html
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: [WARN][75] ([i915#2681] / [i915#2684]) -> [WARN][76] ([i915#1804] / [i915#2684])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb8/igt@i915_pm_rc6_residency@rc6-fence.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb7/igt@i915_pm_rc6_residency@rc6-fence.html
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: [FAIL][77] ([i915#2680]) -> [WARN][78] ([i915#1804] / [i915#2684])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb2/igt@i915_pm_rc6_residency@rc6-idle.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb3/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@runner@aborted:
- shard-kbl: ([FAIL][79], [FAIL][80], [FAIL][81]) ([i915#1436] / [i915#1814] / [i915#2295] / [i915#2722] / [i915#483] / [i915#602]) -> [FAIL][82] ([i915#2295] / [i915#2722] / [i915#483])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl2/igt@runner@aborted.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl6/igt@runner@aborted.html
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl2/igt@runner@aborted.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl1/igt@runner@aborted.html
- shard-iclb: ([FAIL][83], [FAIL][84], [FAIL][85]) ([i915#1814] / [i915#2295] / [i915#2722] / [i915#483]) -> [FAIL][86] ([i915#2295] / [i915#2722])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb7/igt@runner@aborted.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb7/igt@runner@aborted.html
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb1/igt@runner@aborted.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb3/igt@runner@aborted.html
- shard-apl: ([FAIL][87], [FAIL][88], [FAIL][89]) ([i915#1814] / [i915#2295] / [i915#2722]) -> [FAIL][90] ([i915#2295] / [i915#2722])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl1/igt@runner@aborted.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl3/igt@runner@aborted.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl8/igt@runner@aborted.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl2/igt@runner@aborted.html
- shard-glk: ([FAIL][91], [FAIL][92], [FAIL][93], [FAIL][94]) ([i915#1814] / [i915#2295] / [i915#2722] / [i915#483] / [k.org#202321]) -> ([FAIL][95], [FAIL][96]) ([i915#2295] / [i915#2722] / [k.org#202321])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk2/igt@runner@aborted.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk7/igt@runner@aborted.html
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk3/igt@runner@aborted.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk5/igt@runner@aborted.html
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk9/igt@runner@aborted.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk2/igt@runner@aborted.html
- shard-tglb: ([FAIL][97], [FAIL][98], [FAIL][99]) ([i915#1602] / [i915#2295] / [i915#2722] / [i915#402]) -> ([FAIL][100], [FAIL][101]) ([i915#1602] / [i915#2295] / [i915#2722])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb1/igt@runner@aborted.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb8/igt@runner@aborted.html
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb2/igt@runner@aborted.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb8/igt@runner@aborted.html
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb1/igt@runner@aborted.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1185]: https://gitlab.freedesktop.org/drm/intel/issues/1185
[i915#1373]: https://gitlab.freedesktop.org/drm/intel/issues/1373
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1814]: https://gitlab.freedesktop.org/drm/intel/issues/1814
[i915#1887]: https://gitlab.freedesktop.org/drm/intel/issues/1887
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2055]: https://gitlab.freedesktop.org/drm/intel/issues/2055
[i915#2199]: https://gitlab.freedesktop.org/drm/intel/issues/2199
[i915#2295]: https://gitlab.freedesktop.org/drm/intel/issues/2295
[i915#2389]: https://gitlab.freedesktop.org/drm/intel/issues/2389
[i915#2405]: https://gitlab.freedesktop.org/drm/intel/issues/2405
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#2574]: https://gitlab.freedesktop.org/drm/intel/issues/2574
[i915#2635]: https://gitlab.freedesktop.org/drm/intel/issues/2635
[i915#2637]: https://gitlab.freedesktop.org/drm/intel/issues/2637
[i915#2680]: https://gitlab.freedesktop.org/drm/intel/issues/2680
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#2684]: https://gitlab.freedesktop.org/drm/intel/issues/2684
[i915#2722]: https://gitlab.freedesktop.org/drm/intel/issues/2722
[i915#2745]: https://gitlab.freedesktop.org/drm/intel/issues/2745
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#483]: https://gitlab.freedesktop.org/drm/intel/issues/483
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#545]: https://gitlab.freedesktop.org/drm/intel/issues/545
[i915#579]: https://gitlab.freedesktop.org/drm/intel/issues/579
[i915#588]: https://gitlab.freedesktop.org/drm/intel/issues/588
[i915#602]: https://gitlab.freedesktop.org/drm/intel/issues/602
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#78]: https://gitlab.freedesktop.org/drm/intel/issues/78
[i915#794]: https://gitlab.freedesktop.org/drm/intel/issues/794
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[i915#96]: https://gitlab.freedesktop.org/drm/intel/issues/96
[k.org#202321]: https://bugzilla.kernel.org/show_bug.cgi?id=202321
Participating hosts (10 -> 8)
------------------------------
Missing (2): pig-skl-6260u pig-glk-j5005
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5881 -> IGTPW_5250
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_9444: cee8f6ace633b555c64b14938577e6da02710a0b @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5250: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/index.html
IGT_5881: 10d4e2e9177eb747b9f2ab9122e3ab60e91654fb @ 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_5250/index.html
[-- Attachment #1.2: Type: text/html, Size: 26326 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [igt-dev] ✗ Fi.CI.IGT: failure for runner: Don't kill a test on taint if watching timeouts (rev2)
2020-12-05 0:13 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
@ 2020-12-07 10:46 ` Janusz Krzysztofik
0 siblings, 0 replies; 15+ messages in thread
From: Janusz Krzysztofik @ 2020-12-07 10:46 UTC (permalink / raw)
To: igt-dev; +Cc: Lakshminarayana Vudum, Petri Latvala
[-- Attachment #1.1: Type: text/plain, Size: 6360 bytes --]
On Sat, 2020-12-05 at 00:13 +0000, Patchwork wrote:
>
> Patch Details
>
> Series:runner: Don't kill a test on taint if watching timeouts (rev2)
> URL:https://patchwork.freedesktop.org/series/84577/
> State:failure
>
> Details:https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/index.html
>
>
>
>
> CI Bug Log - changes from CI_DRM_9444_full -> IGTPW_5250_full
> Summary
> FAILURE
> Serious unknown changes coming with IGTPW_5250_full absolutely need to be
>
> verified manually.
> If you think the reported changes have nothing to do with the changes
>
> introduced in IGTPW_5250_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_5250/index.html
> Possible new issues
> Here are the unknown changes that may have been introduced in IGTPW_5250_full:
> IGT changes
> Possible regressions
>
>
> igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-edp:
>
>
> shard-iclb: PASS -> FAIL
>
>
> shard-tglb: PASS -> FAIL
>
>
>
>
Looking at test execution time below 2s, dmesg free of kernel tainting, and IGT runner history free of issues in preceding tests, I can't see any relation of those fails to the change.That's a false positive, I believe.
Thanks,Janusz
> Known issues
> Here are the changes found in IGTPW_5250_full that come from known issues:
> IGT changes
> Issues hit
>
>
> igt@gem_exec_whisper@basic-queues:
>
> shard-glk: PASS -> DMESG-WARN (i915#118 / i915#95) +1 similar issue
>
>
>
> igt@i915_pm_rpm@debugfs-forcewake-user:
>
>
> shard-hsw: PASS -> SKIP (fdo#109271)
>
>
> shard-kbl: PASS -> SKIP (fdo#109271)
>
>
> shard-iclb: PASS -> SKIP (i915#579)
>
>
> shard-tglb: PASS -> SKIP (i915#579)
>
>
> shard-apl: PASS -> SKIP (fdo#109271)
>
>
> shard-glk: PASS -> SKIP (fdo#109271)
>
>
>
>
> igt@kms_async_flips@test-time-stamp:
>
> shard-tglb: PASS -> FAIL (i915#2574)
>
>
>
> igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
>
> shard-hsw: PASS -> FAIL (i915#96)
>
>
>
> igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-blt:
>
> shard-glk: PASS -> FAIL (i915#49)
>
>
>
> igt@kms_psr@psr2_cursor_plane_move:
>
> shard-iclb: PASS -> SKIP (fdo#109441)
>
>
>
> igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend:
>
> shard-tglb: PASS -> INCOMPLETE (i915#1436 / i915#1602 / i915#1887 / i915#1982 / i915#2411)
>
>
>
> igt@perf@polling-parameterized:
>
> shard-glk: PASS -> FAIL (i915#1542)
>
>
>
> Possible fixes
>
>
> igt@gem_ctx_isolation@preservation-s3@rcs0:
>
>
> shard-apl: INCOMPLETE (i915#1602 / i915#2635) -> PASS
>
>
> shard-kbl: INCOMPLETE (i915#1602 / i915#794) -> PASS
>
>
> shard-iclb: INCOMPLETE (i915#1373 / i915#1602) -> PASS
>
>
> shard-tglb: INCOMPLETE (i915#1373 / i915#1436 / i915#1602 / i915#1887 / i915#2411) -> PASS
>
>
>
>
> igt@gem_exec_reloc@basic-many-active@rcs0:
>
> shard-glk: FAIL (i915#2389) -> PASS
>
>
>
> igt@gem_softpin@noreloc-s3:
>
> shard-glk: INCOMPLETE (i915#2199 / i915#2405) -> PASS
>
>
>
> igt@i915_pm_dc@dc5-dpms:
>
>
> shard-iclb: FAIL (i915#2745) -> PASS
>
>
> shard-glk: FAIL (i915#2745) -> PASS
>
>
> shard-apl: FAIL (i915#2745) -> PASS
>
>
> shard-kbl: FAIL (i915#545) -> PASS
>
>
>
>
> igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy:
>
> shard-hsw: FAIL (i915#96) -> PASS +1 similar issue
>
>
>
> igt@kms_flip@flip-vs-suspend@b-hdmi-a1:
>
> shard-hsw: INCOMPLETE (i915#2055 / i915#2295) -> PASS
>
>
>
> igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-indfb-pgflip-blt:
>
> shard-glk: FAIL (i915#49) -> PASS
>
>
>
> igt@kms_plane_lowres@pipe-b-tiling-yf:
>
> shard-kbl: DMESG-WARN (i915#165 / i915#180 / i915#78) -> PASS
>
>
>
> igt@kms_psr@psr2_cursor_render:
>
> shard-iclb: SKIP (fdo#109441) -> PASS
>
>
>
> igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend:
>
>
> shard-hsw: INCOMPLETE (i915#2637) -> PASS +1 similar issue
>
>
> shard-kbl: INCOMPLETE (i915#155) -> PASS
>
>
> shard-iclb: INCOMPLETE (i915#1185) -> PASS
>
>
> shard-apl: DMESG-WARN (i915#2635) -> PASS
>
>
> shard-glk: INCOMPLETE (i915#2635) -> PASS
>
>
>
>
> igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
>
> shard-tglb: DMESG-WARN (i915#1602 / i915#2411) -> PASS
>
>
>
> Warnings
>
>
> igt@i915_pm_dc@dc3co-vpb-simulation:
>
> shard-iclb: SKIP (i915#588) -> SKIP (i915#658)
>
>
>
> igt@i915_pm_rc6_residency@rc6-fence:
>
> shard-iclb: WARN (i915#2681 / i915#2684) -> WARN (i915#1804 / i915#2684)
>
>
>
> igt@i915_pm_rc6_residency@rc6-idle:
>
> shard-iclb: FAIL (i915#2680) -> WARN (i915#1804 / i915#2684)
>
>
>
> igt@runner@aborted:
>
>
> shard-kbl: (FAIL, FAIL, FAIL) (i915#1436 / i915#1814 / i915#2295 / i915#2722 / i915#483 / i915#602) -> FAIL (i915#2295 / i915#2722 / i915#483)
>
>
> shard-iclb: (FAIL, FAIL, FAIL) (i915#1814 / i915#2295 / i915#2722 / i915#483) -> FAIL (i915#2295 / i915#2722)
>
>
> shard-apl: (FAIL, FAIL, FAIL) (i915#1814 / i915#2295 / i915#2722) -> FAIL (i915#2295 / i915#2722)
>
>
> shard-glk: (FAIL, FAIL, FAIL, FAIL) (i915#1814 / i915#2295 / i915#2722 / i915#483 / k.org#202321) -> (FAIL, FAIL) (i915#2295 / i915#2722 / k.org#202321)
>
>
> shard-tglb: (FAIL, FAIL, FAIL) (i915#1602 / i915#2295 / i915#2722 / i915#402) -> (FAIL, FAIL) (i915#1602 / i915#2295 / i915#2722)
>
>
>
>
> Participating hosts (10 -> 8)
> Missing (2): pig-skl-6260u pig-glk-j5005
> Build changes
>
> CI: CI-20190529 -> None
> IGT: IGT_5881 -> IGTPW_5250
> Piglit: piglit_4509 -> None
>
> CI-20190529: 20190529
>
> CI_DRM_9444: cee8f6ace633b555c64b14938577e6da02710a0b @ git://anongit.freedesktop.org/gfx-ci/linux
>
> IGTPW_5250: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/index.html
>
> IGT_5881: 10d4e2e9177eb747b9f2ab9122e3ab60e91654fb @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
>
> piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 26974 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts
2020-12-04 19:50 [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts Janusz Krzysztofik
@ 2020-12-07 13:09 ` Petri Latvala
2020-12-05 0:13 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
` (3 subsequent siblings)
4 siblings, 0 replies; 15+ messages in thread
From: Petri Latvala @ 2020-12-07 13:09 UTC (permalink / raw)
To: Janusz Krzysztofik; +Cc: igt-dev, intel-gfx, Chris Wilson
On Fri, Dec 04, 2020 at 08:50:07PM +0100, Janusz Krzysztofik wrote:
> We may still be interested in results of a test even if it has tainted
> the kernel. On the other hand, we need to kill the test on taint if no
> other means of killing it on a jam is active.
>
> If abort on both kernel taint or a timeout is requested, decrease all
> potential timeouts significantly while the taint is detected instead of
> aborting immediately. However, report the taint as the reason of the
> abort if a timeout decreased by the taint expires.
>
> v2: Fix missing show_kernel_task_state() lost on rebase conflict
> resolution (Chris - thanks!)
>
> Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
The effects of this is that we sometimes now get more logs from a test
at the cost of it not directly showing up as an incomplete. We would
still get the igt@runner@aborted result for it so overall we still
catch tainting cases.
Chris's comments have been clarified off-list not to mean directly
opposing this patch, so
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
> ---
> runner/executor.c | 26 ++++++++++++++++++++------
> 1 file changed, 20 insertions(+), 6 deletions(-)
>
> diff --git a/runner/executor.c b/runner/executor.c
> index 1688ae41d..faf272d85 100644
> --- a/runner/executor.c
> +++ b/runner/executor.c
> @@ -726,6 +726,8 @@ static const char *need_to_timeout(struct settings *settings,
> double time_since_kill,
> size_t disk_usage)
> {
> + int decrease = 1;
> +
> if (killed) {
> /*
> * Timeout after being killed is a hardcoded amount
> @@ -753,20 +755,32 @@ static const char *need_to_timeout(struct settings *settings,
> }
>
> /*
> - * If we're configured to care about taints, kill the
> - * test if there's a taint.
> + * If we're configured to care about taints,
> + * decrease timeouts in use if there's a taint,
> + * or kill the test if no timeouts have been requested.
> */
> if (settings->abort_mask & ABORT_TAINT &&
> - is_tainted(taints))
> - return "Killing the test because the kernel is tainted.\n";
> + is_tainted(taints)) {
> + /* list of timeouts that may postpone immediate kill on taint */
> + if (settings->per_test_timeout || settings->inactivity_timeout)
> + decrease = 10;
> + else
> + return "Killing the test because the kernel is tainted.\n";
> + }
>
> if (settings->per_test_timeout != 0 &&
> - time_since_subtest > settings->per_test_timeout)
> + time_since_subtest > settings->per_test_timeout / decrease) {
> + if (decrease > 1)
> + return "Killing the test because the kernel is tainted.\n";
> return show_kernel_task_state("Per-test timeout exceeded. Killing the current test with SIGQUIT.\n");
> + }
>
> if (settings->inactivity_timeout != 0 &&
> - time_since_activity > settings->inactivity_timeout)
> + time_since_activity > settings->inactivity_timeout / decrease ) {
> + if (decrease > 1)
> + return "Killing the test because the kernel is tainted.\n";
> return show_kernel_task_state("Inactivity timeout exceeded. Killing the current test with SIGQUIT.\n");
> + }
>
> if (disk_usage_limit_exceeded(settings, disk_usage))
> return "Disk usage limit exceeded.\n";
> --
> 2.21.1
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts
@ 2020-12-07 13:09 ` Petri Latvala
0 siblings, 0 replies; 15+ messages in thread
From: Petri Latvala @ 2020-12-07 13:09 UTC (permalink / raw)
To: Janusz Krzysztofik; +Cc: igt-dev, intel-gfx, Chris Wilson
On Fri, Dec 04, 2020 at 08:50:07PM +0100, Janusz Krzysztofik wrote:
> We may still be interested in results of a test even if it has tainted
> the kernel. On the other hand, we need to kill the test on taint if no
> other means of killing it on a jam is active.
>
> If abort on both kernel taint or a timeout is requested, decrease all
> potential timeouts significantly while the taint is detected instead of
> aborting immediately. However, report the taint as the reason of the
> abort if a timeout decreased by the taint expires.
>
> v2: Fix missing show_kernel_task_state() lost on rebase conflict
> resolution (Chris - thanks!)
>
> Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
The effects of this is that we sometimes now get more logs from a test
at the cost of it not directly showing up as an incomplete. We would
still get the igt@runner@aborted result for it so overall we still
catch tainting cases.
Chris's comments have been clarified off-list not to mean directly
opposing this patch, so
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
> ---
> runner/executor.c | 26 ++++++++++++++++++++------
> 1 file changed, 20 insertions(+), 6 deletions(-)
>
> diff --git a/runner/executor.c b/runner/executor.c
> index 1688ae41d..faf272d85 100644
> --- a/runner/executor.c
> +++ b/runner/executor.c
> @@ -726,6 +726,8 @@ static const char *need_to_timeout(struct settings *settings,
> double time_since_kill,
> size_t disk_usage)
> {
> + int decrease = 1;
> +
> if (killed) {
> /*
> * Timeout after being killed is a hardcoded amount
> @@ -753,20 +755,32 @@ static const char *need_to_timeout(struct settings *settings,
> }
>
> /*
> - * If we're configured to care about taints, kill the
> - * test if there's a taint.
> + * If we're configured to care about taints,
> + * decrease timeouts in use if there's a taint,
> + * or kill the test if no timeouts have been requested.
> */
> if (settings->abort_mask & ABORT_TAINT &&
> - is_tainted(taints))
> - return "Killing the test because the kernel is tainted.\n";
> + is_tainted(taints)) {
> + /* list of timeouts that may postpone immediate kill on taint */
> + if (settings->per_test_timeout || settings->inactivity_timeout)
> + decrease = 10;
> + else
> + return "Killing the test because the kernel is tainted.\n";
> + }
>
> if (settings->per_test_timeout != 0 &&
> - time_since_subtest > settings->per_test_timeout)
> + time_since_subtest > settings->per_test_timeout / decrease) {
> + if (decrease > 1)
> + return "Killing the test because the kernel is tainted.\n";
> return show_kernel_task_state("Per-test timeout exceeded. Killing the current test with SIGQUIT.\n");
> + }
>
> if (settings->inactivity_timeout != 0 &&
> - time_since_activity > settings->inactivity_timeout)
> + time_since_activity > settings->inactivity_timeout / decrease ) {
> + if (decrease > 1)
> + return "Killing the test because the kernel is tainted.\n";
> return show_kernel_task_state("Inactivity timeout exceeded. Killing the current test with SIGQUIT.\n");
> + }
>
> if (disk_usage_limit_exceeded(settings, disk_usage))
> return "Disk usage limit exceeded.\n";
> --
> 2.21.1
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts
2020-12-07 13:09 ` [igt-dev] " Petri Latvala
@ 2020-12-07 13:18 ` Janusz Krzysztofik
-1 siblings, 0 replies; 15+ messages in thread
From: Janusz Krzysztofik @ 2020-12-07 13:18 UTC (permalink / raw)
To: Petri Latvala; +Cc: igt-dev, intel-gfx, Chris Wilson
On Mon, 2020-12-07 at 15:09 +0200, Petri Latvala wrote:
> On Fri, Dec 04, 2020 at 08:50:07PM +0100, Janusz Krzysztofik wrote:
> > We may still be interested in results of a test even if it has tainted
> > the kernel. On the other hand, we need to kill the test on taint if no
> > other means of killing it on a jam is active.
> >
> > If abort on both kernel taint or a timeout is requested, decrease all
> > potential timeouts significantly while the taint is detected instead of
> > aborting immediately. However, report the taint as the reason of the
> > abort if a timeout decreased by the taint expires.
> >
> > v2: Fix missing show_kernel_task_state() lost on rebase conflict
> > resolution (Chris - thanks!)
> >
> > Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
>
> The effects of this is that we sometimes now get more logs from a test
> at the cost of it not directly showing up as an incomplete. We would
> still get the igt@runner@aborted result for it so overall we still
> catch tainting cases.
>
> Chris's comments have been clarified off-list not to mean directly
> opposing this patch, so
>
>
> Reviewed-by: Petri Latvala <petri.latvala@intel.com>
Thanks, pushed.
Janusz
>
>
>
> > ---
> > runner/executor.c | 26 ++++++++++++++++++++------
> > 1 file changed, 20 insertions(+), 6 deletions(-)
> >
> > diff --git a/runner/executor.c b/runner/executor.c
> > index 1688ae41d..faf272d85 100644
> > --- a/runner/executor.c
> > +++ b/runner/executor.c
> > @@ -726,6 +726,8 @@ static const char *need_to_timeout(struct settings *settings,
> > double time_since_kill,
> > size_t disk_usage)
> > {
> > + int decrease = 1;
> > +
> > if (killed) {
> > /*
> > * Timeout after being killed is a hardcoded amount
> > @@ -753,20 +755,32 @@ static const char *need_to_timeout(struct settings *settings,
> > }
> >
> > /*
> > - * If we're configured to care about taints, kill the
> > - * test if there's a taint.
> > + * If we're configured to care about taints,
> > + * decrease timeouts in use if there's a taint,
> > + * or kill the test if no timeouts have been requested.
> > */
> > if (settings->abort_mask & ABORT_TAINT &&
> > - is_tainted(taints))
> > - return "Killing the test because the kernel is tainted.\n";
> > + is_tainted(taints)) {
> > + /* list of timeouts that may postpone immediate kill on taint */
> > + if (settings->per_test_timeout || settings->inactivity_timeout)
> > + decrease = 10;
> > + else
> > + return "Killing the test because the kernel is tainted.\n";
> > + }
> >
> > if (settings->per_test_timeout != 0 &&
> > - time_since_subtest > settings->per_test_timeout)
> > + time_since_subtest > settings->per_test_timeout / decrease) {
> > + if (decrease > 1)
> > + return "Killing the test because the kernel is tainted.\n";
> > return show_kernel_task_state("Per-test timeout exceeded. Killing the current test with SIGQUIT.\n");
> > + }
> >
> > if (settings->inactivity_timeout != 0 &&
> > - time_since_activity > settings->inactivity_timeout)
> > + time_since_activity > settings->inactivity_timeout / decrease ) {
> > + if (decrease > 1)
> > + return "Killing the test because the kernel is tainted.\n";
> > return show_kernel_task_state("Inactivity timeout exceeded. Killing the current test with SIGQUIT.\n");
> > + }
> >
> > if (disk_usage_limit_exceeded(settings, disk_usage))
> > return "Disk usage limit exceeded.\n";
> > --
> > 2.21.1
> >
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts
@ 2020-12-07 13:18 ` Janusz Krzysztofik
0 siblings, 0 replies; 15+ messages in thread
From: Janusz Krzysztofik @ 2020-12-07 13:18 UTC (permalink / raw)
To: Petri Latvala; +Cc: igt-dev, intel-gfx, Chris Wilson
On Mon, 2020-12-07 at 15:09 +0200, Petri Latvala wrote:
> On Fri, Dec 04, 2020 at 08:50:07PM +0100, Janusz Krzysztofik wrote:
> > We may still be interested in results of a test even if it has tainted
> > the kernel. On the other hand, we need to kill the test on taint if no
> > other means of killing it on a jam is active.
> >
> > If abort on both kernel taint or a timeout is requested, decrease all
> > potential timeouts significantly while the taint is detected instead of
> > aborting immediately. However, report the taint as the reason of the
> > abort if a timeout decreased by the taint expires.
> >
> > v2: Fix missing show_kernel_task_state() lost on rebase conflict
> > resolution (Chris - thanks!)
> >
> > Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
>
> The effects of this is that we sometimes now get more logs from a test
> at the cost of it not directly showing up as an incomplete. We would
> still get the igt@runner@aborted result for it so overall we still
> catch tainting cases.
>
> Chris's comments have been clarified off-list not to mean directly
> opposing this patch, so
>
>
> Reviewed-by: Petri Latvala <petri.latvala@intel.com>
Thanks, pushed.
Janusz
>
>
>
> > ---
> > runner/executor.c | 26 ++++++++++++++++++++------
> > 1 file changed, 20 insertions(+), 6 deletions(-)
> >
> > diff --git a/runner/executor.c b/runner/executor.c
> > index 1688ae41d..faf272d85 100644
> > --- a/runner/executor.c
> > +++ b/runner/executor.c
> > @@ -726,6 +726,8 @@ static const char *need_to_timeout(struct settings *settings,
> > double time_since_kill,
> > size_t disk_usage)
> > {
> > + int decrease = 1;
> > +
> > if (killed) {
> > /*
> > * Timeout after being killed is a hardcoded amount
> > @@ -753,20 +755,32 @@ static const char *need_to_timeout(struct settings *settings,
> > }
> >
> > /*
> > - * If we're configured to care about taints, kill the
> > - * test if there's a taint.
> > + * If we're configured to care about taints,
> > + * decrease timeouts in use if there's a taint,
> > + * or kill the test if no timeouts have been requested.
> > */
> > if (settings->abort_mask & ABORT_TAINT &&
> > - is_tainted(taints))
> > - return "Killing the test because the kernel is tainted.\n";
> > + is_tainted(taints)) {
> > + /* list of timeouts that may postpone immediate kill on taint */
> > + if (settings->per_test_timeout || settings->inactivity_timeout)
> > + decrease = 10;
> > + else
> > + return "Killing the test because the kernel is tainted.\n";
> > + }
> >
> > if (settings->per_test_timeout != 0 &&
> > - time_since_subtest > settings->per_test_timeout)
> > + time_since_subtest > settings->per_test_timeout / decrease) {
> > + if (decrease > 1)
> > + return "Killing the test because the kernel is tainted.\n";
> > return show_kernel_task_state("Per-test timeout exceeded. Killing the current test with SIGQUIT.\n");
> > + }
> >
> > if (settings->inactivity_timeout != 0 &&
> > - time_since_activity > settings->inactivity_timeout)
> > + time_since_activity > settings->inactivity_timeout / decrease ) {
> > + if (decrease > 1)
> > + return "Killing the test because the kernel is tainted.\n";
> > return show_kernel_task_state("Inactivity timeout exceeded. Killing the current test with SIGQUIT.\n");
> > + }
> >
> > if (disk_usage_limit_exceeded(settings, disk_usage))
> > return "Disk usage limit exceeded.\n";
> > --
> > 2.21.1
> >
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 15+ messages in thread
* [igt-dev] ✓ Fi.CI.IGT: success for runner: Don't kill a test on taint if watching timeouts (rev2)
2020-12-04 19:50 [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts Janusz Krzysztofik
` (2 preceding siblings ...)
2020-12-07 13:09 ` [igt-dev] " Petri Latvala
@ 2020-12-08 17:39 ` Patchwork
2021-01-06 9:41 ` [igt-dev] " Chris Wilson
4 siblings, 0 replies; 15+ messages in thread
From: Patchwork @ 2020-12-08 17:39 UTC (permalink / raw)
To: Janusz Krzysztofik; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 30280 bytes --]
== Series Details ==
Series: runner: Don't kill a test on taint if watching timeouts (rev2)
URL : https://patchwork.freedesktop.org/series/84577/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9444_full -> IGTPW_5250_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/index.html
Known issues
------------
Here are the changes found in IGTPW_5250_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@engines-hostile-preempt:
- shard-hsw: NOTRUN -> [SKIP][1] ([fdo#109271] / [i915#1099])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw1/igt@gem_ctx_persistence@engines-hostile-preempt.html
* igt@gem_exec_params@rsvd2-dirt:
- shard-tglb: NOTRUN -> [SKIP][2] ([fdo#109283])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb5/igt@gem_exec_params@rsvd2-dirt.html
- shard-iclb: NOTRUN -> [SKIP][3] ([fdo#109283])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb8/igt@gem_exec_params@rsvd2-dirt.html
* igt@gem_exec_reloc@basic-wide-active@vcs1:
- shard-iclb: NOTRUN -> [FAIL][4] ([i915#2389])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb4/igt@gem_exec_reloc@basic-wide-active@vcs1.html
* igt@gem_exec_whisper@basic-queues:
- shard-glk: [PASS][5] -> [DMESG-WARN][6] ([i915#118] / [i915#95]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk1/igt@gem_exec_whisper@basic-queues.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk3/igt@gem_exec_whisper@basic-queues.html
* igt@gem_softpin@evict-snoop:
- shard-iclb: NOTRUN -> [SKIP][7] ([fdo#109312])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb5/igt@gem_softpin@evict-snoop.html
* igt@gem_userptr_blits@mmap-offset-invalidate-idle@gtt:
- shard-tglb: NOTRUN -> [SKIP][8] ([i915#1317]) +3 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb6/igt@gem_userptr_blits@mmap-offset-invalidate-idle@gtt.html
* igt@gen9_exec_parse@bb-start-out:
- shard-tglb: NOTRUN -> [SKIP][9] ([fdo#112306])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb5/igt@gen9_exec_parse@bb-start-out.html
- shard-iclb: NOTRUN -> [SKIP][10] ([fdo#112306])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb3/igt@gen9_exec_parse@bb-start-out.html
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-edp:
- shard-iclb: [PASS][11] -> [FAIL][12] ([i915#2768])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb7/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-edp.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb2/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-edp.html
- shard-tglb: [PASS][13] -> [FAIL][14] ([i915#2768])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb5/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-edp.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb2/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-edp.html
* igt@i915_pm_rpm@debugfs-forcewake-user:
- shard-hsw: [PASS][15] -> [SKIP][16] ([fdo#109271])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-hsw1/igt@i915_pm_rpm@debugfs-forcewake-user.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw1/igt@i915_pm_rpm@debugfs-forcewake-user.html
- shard-kbl: [PASS][17] -> [SKIP][18] ([fdo#109271])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl2/igt@i915_pm_rpm@debugfs-forcewake-user.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl3/igt@i915_pm_rpm@debugfs-forcewake-user.html
- shard-iclb: [PASS][19] -> [SKIP][20] ([i915#579])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb6/igt@i915_pm_rpm@debugfs-forcewake-user.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb5/igt@i915_pm_rpm@debugfs-forcewake-user.html
- shard-tglb: [PASS][21] -> [SKIP][22] ([i915#579])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb2/igt@i915_pm_rpm@debugfs-forcewake-user.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb8/igt@i915_pm_rpm@debugfs-forcewake-user.html
- shard-apl: [PASS][23] -> [SKIP][24] ([fdo#109271])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl4/igt@i915_pm_rpm@debugfs-forcewake-user.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl8/igt@i915_pm_rpm@debugfs-forcewake-user.html
- shard-glk: [PASS][25] -> [SKIP][26] ([fdo#109271])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk7/igt@i915_pm_rpm@debugfs-forcewake-user.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk3/igt@i915_pm_rpm@debugfs-forcewake-user.html
* igt@i915_pm_rpm@modeset-non-lpsp-stress-no-wait:
- shard-tglb: NOTRUN -> [SKIP][27] ([fdo#111644] / [i915#1397] / [i915#2411])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb3/igt@i915_pm_rpm@modeset-non-lpsp-stress-no-wait.html
* igt@kms_async_flips@test-time-stamp:
- shard-tglb: [PASS][28] -> [FAIL][29] ([i915#2574])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb2/igt@kms_async_flips@test-time-stamp.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb1/igt@kms_async_flips@test-time-stamp.html
* igt@kms_atomic_transition@5x-modeset-transitions:
- shard-tglb: NOTRUN -> [SKIP][30] ([fdo#112025])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb6/igt@kms_atomic_transition@5x-modeset-transitions.html
* igt@kms_big_fb@x-tiled-16bpp-rotate-270:
- shard-iclb: NOTRUN -> [SKIP][31] ([fdo#110725] / [fdo#111614]) +2 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb6/igt@kms_big_fb@x-tiled-16bpp-rotate-270.html
* igt@kms_big_fb@y-tiled-64bpp-rotate-90:
- shard-apl: NOTRUN -> [SKIP][32] ([fdo#109271]) +44 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl3/igt@kms_big_fb@y-tiled-64bpp-rotate-90.html
- shard-tglb: NOTRUN -> [SKIP][33] ([fdo#111614]) +1 similar issue
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb1/igt@kms_big_fb@y-tiled-64bpp-rotate-90.html
* igt@kms_chamelium@dp-mode-timings:
- shard-apl: NOTRUN -> [SKIP][34] ([fdo#109271] / [fdo#111827]) +6 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl7/igt@kms_chamelium@dp-mode-timings.html
- shard-glk: NOTRUN -> [SKIP][35] ([fdo#109271] / [fdo#111827]) +8 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk1/igt@kms_chamelium@dp-mode-timings.html
* igt@kms_chamelium@hdmi-hpd-enable-disable-mode:
- shard-iclb: NOTRUN -> [SKIP][36] ([fdo#109284] / [fdo#111827]) +6 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb7/igt@kms_chamelium@hdmi-hpd-enable-disable-mode.html
* igt@kms_chamelium@hdmi-mode-timings:
- shard-kbl: NOTRUN -> [SKIP][37] ([fdo#109271] / [fdo#111827]) +6 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl2/igt@kms_chamelium@hdmi-mode-timings.html
- shard-hsw: NOTRUN -> [SKIP][38] ([fdo#109271] / [fdo#111827]) +4 similar issues
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw2/igt@kms_chamelium@hdmi-mode-timings.html
* igt@kms_chamelium@vga-hpd-fast:
- shard-tglb: NOTRUN -> [SKIP][39] ([fdo#109284] / [fdo#111827]) +7 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb7/igt@kms_chamelium@vga-hpd-fast.html
* igt@kms_cursor_crc@pipe-a-cursor-512x170-sliding:
- shard-kbl: NOTRUN -> [SKIP][40] ([fdo#109271]) +44 similar issues
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl4/igt@kms_cursor_crc@pipe-a-cursor-512x170-sliding.html
- shard-iclb: NOTRUN -> [SKIP][41] ([fdo#109278] / [fdo#109279])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb4/igt@kms_cursor_crc@pipe-a-cursor-512x170-sliding.html
* igt@kms_cursor_crc@pipe-d-cursor-256x85-random:
- shard-glk: NOTRUN -> [SKIP][42] ([fdo#109271]) +54 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk3/igt@kms_cursor_crc@pipe-d-cursor-256x85-random.html
* igt@kms_cursor_crc@pipe-d-cursor-512x170-random:
- shard-tglb: NOTRUN -> [SKIP][43] ([fdo#109279]) +1 similar issue
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb2/igt@kms_cursor_crc@pipe-d-cursor-512x170-random.html
* igt@kms_cursor_crc@pipe-d-cursor-64x64-rapid-movement:
- shard-iclb: NOTRUN -> [SKIP][44] ([fdo#109278]) +7 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb5/igt@kms_cursor_crc@pipe-d-cursor-64x64-rapid-movement.html
* igt@kms_cursor_legacy@2x-flip-vs-cursor-atomic:
- shard-iclb: NOTRUN -> [SKIP][45] ([fdo#109274] / [fdo#109278])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb3/igt@kms_cursor_legacy@2x-flip-vs-cursor-atomic.html
* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
- shard-hsw: [PASS][46] -> [FAIL][47] ([i915#96])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-hsw6/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw6/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
* igt@kms_flip@2x-flip-vs-dpms:
- shard-iclb: NOTRUN -> [SKIP][48] ([fdo#109274]) +2 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb5/igt@kms_flip@2x-flip-vs-dpms.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile:
- shard-apl: NOTRUN -> [FAIL][49] ([i915#2641])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl1/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile.html
- shard-kbl: NOTRUN -> [FAIL][50] ([i915#2641])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl7/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-blt:
- shard-glk: [PASS][51] -> [FAIL][52] ([i915#49])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk5/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-blt.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk4/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-pgflip-blt:
- shard-iclb: NOTRUN -> [SKIP][53] ([fdo#109280]) +9 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb8/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-pgflip-blt.html
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-mmap-gtt:
- shard-tglb: NOTRUN -> [SKIP][54] ([fdo#111825]) +21 similar issues
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb1/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-mmap-gtt.html
* igt@kms_hdr@static-toggle-suspend:
- shard-tglb: NOTRUN -> [SKIP][55] ([i915#1187])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb8/igt@kms_hdr@static-toggle-suspend.html
* igt@kms_pipe_crc_basic@read-crc-pipe-d:
- shard-kbl: NOTRUN -> [SKIP][56] ([fdo#109271] / [i915#533])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl4/igt@kms_pipe_crc_basic@read-crc-pipe-d.html
- shard-glk: NOTRUN -> [SKIP][57] ([fdo#109271] / [i915#533])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk5/igt@kms_pipe_crc_basic@read-crc-pipe-d.html
- shard-apl: NOTRUN -> [SKIP][58] ([fdo#109271] / [i915#533])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl6/igt@kms_pipe_crc_basic@read-crc-pipe-d.html
* igt@kms_plane_alpha_blend@pipe-b-alpha-7efc:
- shard-apl: NOTRUN -> [FAIL][59] ([fdo#108145] / [i915#265])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl4/igt@kms_plane_alpha_blend@pipe-b-alpha-7efc.html
- shard-kbl: NOTRUN -> [FAIL][60] ([fdo#108145] / [i915#265])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl7/igt@kms_plane_alpha_blend@pipe-b-alpha-7efc.html
* igt@kms_plane_multiple@atomic-pipe-d-tiling-yf:
- shard-tglb: NOTRUN -> [SKIP][61] ([fdo#112054])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb5/igt@kms_plane_multiple@atomic-pipe-d-tiling-yf.html
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: [PASS][62] -> [SKIP][63] ([fdo#109441])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb8/igt@kms_psr@psr2_cursor_plane_move.html
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: NOTRUN -> [SKIP][64] ([fdo#109441])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb4/igt@kms_psr@psr2_no_drrs.html
* igt@kms_tv_load_detect@load-detect:
- shard-tglb: NOTRUN -> [SKIP][65] ([fdo#109309])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb5/igt@kms_tv_load_detect@load-detect.html
* igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend:
- shard-tglb: [PASS][66] -> [INCOMPLETE][67] ([i915#1436] / [i915#1602] / [i915#1887] / [i915#1982] / [i915#2411])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb2/igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb8/igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend.html
* igt@kms_writeback@writeback-check-output:
- shard-apl: NOTRUN -> [SKIP][68] ([fdo#109271] / [i915#2437])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl2/igt@kms_writeback@writeback-check-output.html
- shard-iclb: NOTRUN -> [SKIP][69] ([i915#2437])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb7/igt@kms_writeback@writeback-check-output.html
- shard-kbl: NOTRUN -> [SKIP][70] ([fdo#109271] / [i915#2437])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl1/igt@kms_writeback@writeback-check-output.html
- shard-glk: NOTRUN -> [SKIP][71] ([fdo#109271] / [i915#2437])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk6/igt@kms_writeback@writeback-check-output.html
* igt@nouveau_crc@pipe-b-ctx-flip-skip-current-frame:
- shard-tglb: NOTRUN -> [SKIP][72] ([i915#2530]) +3 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb1/igt@nouveau_crc@pipe-b-ctx-flip-skip-current-frame.html
* igt@nouveau_crc@pipe-b-source-rg:
- shard-iclb: NOTRUN -> [SKIP][73] ([i915#2530]) +2 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb2/igt@nouveau_crc@pipe-b-source-rg.html
* igt@nouveau_crc@pipe-c-source-rg:
- shard-hsw: NOTRUN -> [SKIP][74] ([fdo#109271]) +47 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw2/igt@nouveau_crc@pipe-c-source-rg.html
* igt@perf@polling-parameterized:
- shard-glk: [PASS][75] -> [FAIL][76] ([i915#1542])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk8/igt@perf@polling-parameterized.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk5/igt@perf@polling-parameterized.html
* igt@perf@unprivileged-single-ctx-counters:
- shard-iclb: NOTRUN -> [SKIP][77] ([fdo#109289])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb6/igt@perf@unprivileged-single-ctx-counters.html
- shard-tglb: NOTRUN -> [SKIP][78] ([fdo#109289])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb1/igt@perf@unprivileged-single-ctx-counters.html
* igt@prime_nv_api@i915_self_import:
- shard-tglb: NOTRUN -> [SKIP][79] ([fdo#109291]) +2 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb1/igt@prime_nv_api@i915_self_import.html
- shard-iclb: NOTRUN -> [SKIP][80] ([fdo#109291]) +1 similar issue
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb4/igt@prime_nv_api@i915_self_import.html
#### Possible fixes ####
* igt@gem_ctx_isolation@preservation-s3@rcs0:
- shard-apl: [INCOMPLETE][81] ([i915#1602] / [i915#2635]) -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl3/igt@gem_ctx_isolation@preservation-s3@rcs0.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl3/igt@gem_ctx_isolation@preservation-s3@rcs0.html
- shard-kbl: [INCOMPLETE][83] ([i915#1602] / [i915#794]) -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl2/igt@gem_ctx_isolation@preservation-s3@rcs0.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl2/igt@gem_ctx_isolation@preservation-s3@rcs0.html
- shard-iclb: [INCOMPLETE][85] ([i915#1373] / [i915#1602]) -> [PASS][86]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb1/igt@gem_ctx_isolation@preservation-s3@rcs0.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb1/igt@gem_ctx_isolation@preservation-s3@rcs0.html
- shard-tglb: [INCOMPLETE][87] ([i915#1373] / [i915#1436] / [i915#1602] / [i915#1887] / [i915#2411]) -> [PASS][88]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb8/igt@gem_ctx_isolation@preservation-s3@rcs0.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb5/igt@gem_ctx_isolation@preservation-s3@rcs0.html
* igt@gem_exec_reloc@basic-many-active@rcs0:
- shard-glk: [FAIL][89] ([i915#2389]) -> [PASS][90]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk3/igt@gem_exec_reloc@basic-many-active@rcs0.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk2/igt@gem_exec_reloc@basic-many-active@rcs0.html
* igt@gem_softpin@noreloc-s3:
- shard-glk: [INCOMPLETE][91] ([i915#2199] / [i915#2405]) -> [PASS][92]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk6/igt@gem_softpin@noreloc-s3.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk8/igt@gem_softpin@noreloc-s3.html
* igt@i915_pm_dc@dc5-dpms:
- shard-iclb: [FAIL][93] ([i915#2745]) -> [PASS][94]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb7/igt@i915_pm_dc@dc5-dpms.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb3/igt@i915_pm_dc@dc5-dpms.html
- shard-glk: [FAIL][95] ([i915#2745]) -> [PASS][96]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk2/igt@i915_pm_dc@dc5-dpms.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk4/igt@i915_pm_dc@dc5-dpms.html
- shard-apl: [FAIL][97] ([i915#2745]) -> [PASS][98]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl1/igt@i915_pm_dc@dc5-dpms.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl1/igt@i915_pm_dc@dc5-dpms.html
- shard-kbl: [FAIL][99] ([i915#545]) -> [PASS][100]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl6/igt@i915_pm_dc@dc5-dpms.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl7/igt@i915_pm_dc@dc5-dpms.html
* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy:
- shard-hsw: [FAIL][101] ([i915#96]) -> [PASS][102] +1 similar issue
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-hsw1/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw2/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html
* igt@kms_flip@flip-vs-suspend@b-hdmi-a1:
- shard-hsw: [INCOMPLETE][103] ([i915#2055] / [i915#2295]) -> [PASS][104]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-hsw2/igt@kms_flip@flip-vs-suspend@b-hdmi-a1.html
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw6/igt@kms_flip@flip-vs-suspend@b-hdmi-a1.html
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-indfb-pgflip-blt:
- shard-glk: [FAIL][105] ([i915#49]) -> [PASS][106]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk7/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-indfb-pgflip-blt.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk3/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-indfb-pgflip-blt.html
* igt@kms_plane_lowres@pipe-b-tiling-yf:
- shard-kbl: [DMESG-WARN][107] ([i915#165] / [i915#180] / [i915#78]) -> [PASS][108]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl2/igt@kms_plane_lowres@pipe-b-tiling-yf.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl6/igt@kms_plane_lowres@pipe-b-tiling-yf.html
* igt@kms_psr@psr2_cursor_render:
- shard-iclb: [SKIP][109] ([fdo#109441]) -> [PASS][110]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb7/igt@kms_psr@psr2_cursor_render.html
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb2/igt@kms_psr@psr2_cursor_render.html
* igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend:
- shard-hsw: [INCOMPLETE][111] ([i915#2637]) -> [PASS][112] +1 similar issue
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-hsw6/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-hsw2/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
- shard-kbl: [INCOMPLETE][113] ([i915#155]) -> [PASS][114]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl6/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl6/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
- shard-iclb: [INCOMPLETE][115] ([i915#1185]) -> [PASS][116]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb7/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb6/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
- shard-apl: [DMESG-WARN][117] ([i915#2635]) -> [PASS][118]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl1/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl6/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
- shard-glk: [INCOMPLETE][119] ([i915#2635]) -> [PASS][120]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk2/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk3/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
* igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
- shard-tglb: [DMESG-WARN][121] ([i915#1602] / [i915#2411]) -> [PASS][122]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb1/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb3/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
#### Warnings ####
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-iclb: [SKIP][123] ([i915#588]) -> [SKIP][124] ([i915#658])
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb2/igt@i915_pm_dc@dc3co-vpb-simulation.html
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb6/igt@i915_pm_dc@dc3co-vpb-simulation.html
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: [WARN][125] ([i915#2681] / [i915#2684]) -> [WARN][126] ([i915#1804] / [i915#2684])
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb8/igt@i915_pm_rc6_residency@rc6-fence.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb7/igt@i915_pm_rc6_residency@rc6-fence.html
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: [FAIL][127] ([i915#2680]) -> [WARN][128] ([i915#1804] / [i915#2684])
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb2/igt@i915_pm_rc6_residency@rc6-idle.html
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb3/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@runner@aborted:
- shard-kbl: ([FAIL][129], [FAIL][130], [FAIL][131]) ([i915#1436] / [i915#1814] / [i915#2295] / [i915#2722] / [i915#483] / [i915#602]) -> [FAIL][132] ([i915#2295] / [i915#2722] / [i915#483])
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl2/igt@runner@aborted.html
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl6/igt@runner@aborted.html
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-kbl2/igt@runner@aborted.html
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-kbl1/igt@runner@aborted.html
- shard-iclb: ([FAIL][133], [FAIL][134], [FAIL][135]) ([i915#1814] / [i915#2295] / [i915#2722] / [i915#483]) -> [FAIL][136] ([i915#2295] / [i915#2722])
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb7/igt@runner@aborted.html
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb7/igt@runner@aborted.html
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-iclb1/igt@runner@aborted.html
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-iclb3/igt@runner@aborted.html
- shard-apl: ([FAIL][137], [FAIL][138], [FAIL][139]) ([i915#1814] / [i915#2295] / [i915#2722]) -> [FAIL][140] ([i915#2295] / [i915#2722])
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl1/igt@runner@aborted.html
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl3/igt@runner@aborted.html
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-apl8/igt@runner@aborted.html
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-apl2/igt@runner@aborted.html
- shard-glk: ([FAIL][141], [FAIL][142], [FAIL][143], [FAIL][144]) ([i915#1814] / [i915#2295] / [i915#2722] / [i915#483] / [k.org#202321]) -> ([FAIL][145], [FAIL][146]) ([i915#2295] / [i915#2722] / [k.org#202321])
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk2/igt@runner@aborted.html
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk7/igt@runner@aborted.html
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk3/igt@runner@aborted.html
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-glk5/igt@runner@aborted.html
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk9/igt@runner@aborted.html
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-glk2/igt@runner@aborted.html
- shard-tglb: ([FAIL][147], [FAIL][148], [FAIL][149]) ([i915#1602] / [i915#2295] / [i915#2722] / [i915#402]) -> ([FAIL][150], [FAIL][151]) ([i915#1602] / [i915#2295] / [i915#2722])
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb1/igt@runner@aborted.html
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb8/igt@runner@aborted.html
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9444/shard-tglb2/igt@runner@aborted.html
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb8/igt@runner@aborted.html
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/shard-tglb1/igt@runner@aborted.html
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109279]: https://bugs.freedesktop.org/show_bug.cgi?id=109279
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109283]: https://bugs.freedesktop.org/show_bug.cgi?id=109283
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109291]: https://bugs.freedesktop.org/show_bug.cgi?id=109291
[fdo#109309]: https://bugs.freedesktop.org/show_bug.cgi?id=109309
[fdo#109312]: https://bugs.freedesktop.org/show_bug.cgi?id=109312
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110725]: https://bugs.freedesktop.org/show_bug.cgi?id=110725
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111644]: https://bugs.freedesktop.org/show_bug.cgi?id=111644
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[fdo#112025]: https://bugs.freedesktop.org/show_bug.cgi?id=112025
[fdo#112054]: https://bugs.freedesktop.org/show_bug.cgi?id=112054
[fdo#112306]: https://bugs.freedesktop.org/show_bug.cgi?id=112306
[i915#1099]: https://gitlab.freedesktop.org/drm/intel/issues/1099
[i915#118]: https://gitlab.freedesktop.o
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5250/index.html
[-- Attachment #1.2: Type: text/html, Size: 35271 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts
2020-12-04 19:50 [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts Janusz Krzysztofik
@ 2021-01-06 9:41 ` Chris Wilson
2020-12-05 0:13 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
` (3 subsequent siblings)
4 siblings, 0 replies; 15+ messages in thread
From: Chris Wilson @ 2021-01-06 9:41 UTC (permalink / raw)
To: Janusz Krzysztofik, igt-dev; +Cc: intel-gfx
Quoting Janusz Krzysztofik (2020-12-04 19:50:07)
> We may still be interested in results of a test even if it has tainted
> the kernel. On the other hand, we need to kill the test on taint if no
> other means of killing it on a jam is active.
>
> If abort on both kernel taint or a timeout is requested, decrease all
> potential timeouts significantly while the taint is detected instead of
> aborting immediately. However, report the taint as the reason of the
> abort if a timeout decreased by the taint expires.
This has the nasty side effect of not stopping the test run after a
kernel taint. Instead the next test inherits the tainted condition from
the previous test and usually ends up being declared incomplete.
False positives are frustrating.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts
@ 2021-01-06 9:41 ` Chris Wilson
0 siblings, 0 replies; 15+ messages in thread
From: Chris Wilson @ 2021-01-06 9:41 UTC (permalink / raw)
To: Janusz Krzysztofik, igt-dev; +Cc: intel-gfx, Petri Latvala
Quoting Janusz Krzysztofik (2020-12-04 19:50:07)
> We may still be interested in results of a test even if it has tainted
> the kernel. On the other hand, we need to kill the test on taint if no
> other means of killing it on a jam is active.
>
> If abort on both kernel taint or a timeout is requested, decrease all
> potential timeouts significantly while the taint is detected instead of
> aborting immediately. However, report the taint as the reason of the
> abort if a timeout decreased by the taint expires.
This has the nasty side effect of not stopping the test run after a
kernel taint. Instead the next test inherits the tainted condition from
the previous test and usually ends up being declared incomplete.
False positives are frustrating.
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts
2021-01-06 9:41 ` [igt-dev] " Chris Wilson
(?)
@ 2021-01-07 9:40 ` Petri Latvala
2021-01-07 9:49 ` [igt-dev] " Chris Wilson
-1 siblings, 1 reply; 15+ messages in thread
From: Petri Latvala @ 2021-01-07 9:40 UTC (permalink / raw)
To: Chris Wilson; +Cc: igt-dev, intel-gfx
On Wed, Jan 06, 2021 at 09:41:37AM +0000, Chris Wilson wrote:
> Quoting Janusz Krzysztofik (2020-12-04 19:50:07)
> > We may still be interested in results of a test even if it has tainted
> > the kernel. On the other hand, we need to kill the test on taint if no
> > other means of killing it on a jam is active.
> >
> > If abort on both kernel taint or a timeout is requested, decrease all
> > potential timeouts significantly while the taint is detected instead of
> > aborting immediately. However, report the taint as the reason of the
> > abort if a timeout decreased by the taint expires.
>
> This has the nasty side effect of not stopping the test run after a
> kernel taint. Instead the next test inherits the tainted condition from
> the previous test and usually ends up being declared incomplete.
>
> False positives are frustrating.
> -Chris
Do you have a link to a test run where this happened? This patch
didn't change the between-tests abort checks.
--
Petri Latvala
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts
2021-01-07 9:40 ` [Intel-gfx] " Petri Latvala
@ 2021-01-07 9:49 ` Chris Wilson
0 siblings, 0 replies; 15+ messages in thread
From: Chris Wilson @ 2021-01-07 9:49 UTC (permalink / raw)
To: Petri Latvala; +Cc: igt-dev, intel-gfx
Quoting Petri Latvala (2021-01-07 09:40:02)
> On Wed, Jan 06, 2021 at 09:41:37AM +0000, Chris Wilson wrote:
> > Quoting Janusz Krzysztofik (2020-12-04 19:50:07)
> > > We may still be interested in results of a test even if it has tainted
> > > the kernel. On the other hand, we need to kill the test on taint if no
> > > other means of killing it on a jam is active.
> > >
> > > If abort on both kernel taint or a timeout is requested, decrease all
> > > potential timeouts significantly while the taint is detected instead of
> > > aborting immediately. However, report the taint as the reason of the
> > > abort if a timeout decreased by the taint expires.
> >
> > This has the nasty side effect of not stopping the test run after a
> > kernel taint. Instead the next test inherits the tainted condition from
> > the previous test and usually ends up being declared incomplete.
> >
> > False positives are frustrating.
> > -Chris
>
>
> Do you have a link to a test run where this happened? This patch
> didn't change the between-tests abort checks.
The taint is from the warnings in the penultimate test:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9550/shard-skl7/igt_runner20.txt
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [igt-dev] [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts
@ 2021-01-07 9:49 ` Chris Wilson
0 siblings, 0 replies; 15+ messages in thread
From: Chris Wilson @ 2021-01-07 9:49 UTC (permalink / raw)
To: Petri Latvala; +Cc: igt-dev, intel-gfx
Quoting Petri Latvala (2021-01-07 09:40:02)
> On Wed, Jan 06, 2021 at 09:41:37AM +0000, Chris Wilson wrote:
> > Quoting Janusz Krzysztofik (2020-12-04 19:50:07)
> > > We may still be interested in results of a test even if it has tainted
> > > the kernel. On the other hand, we need to kill the test on taint if no
> > > other means of killing it on a jam is active.
> > >
> > > If abort on both kernel taint or a timeout is requested, decrease all
> > > potential timeouts significantly while the taint is detected instead of
> > > aborting immediately. However, report the taint as the reason of the
> > > abort if a timeout decreased by the taint expires.
> >
> > This has the nasty side effect of not stopping the test run after a
> > kernel taint. Instead the next test inherits the tainted condition from
> > the previous test and usually ends up being declared incomplete.
> >
> > False positives are frustrating.
> > -Chris
>
>
> Do you have a link to a test run where this happened? This patch
> didn't change the between-tests abort checks.
The taint is from the warnings in the penultimate test:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9550/shard-skl7/igt_runner20.txt
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Intel-gfx] [igt-dev] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts
2021-01-07 9:49 ` [igt-dev] " Chris Wilson
(?)
@ 2021-01-07 10:06 ` Petri Latvala
-1 siblings, 0 replies; 15+ messages in thread
From: Petri Latvala @ 2021-01-07 10:06 UTC (permalink / raw)
To: Chris Wilson; +Cc: igt-dev, intel-gfx
On Thu, Jan 07, 2021 at 09:49:23AM +0000, Chris Wilson wrote:
> Quoting Petri Latvala (2021-01-07 09:40:02)
> > On Wed, Jan 06, 2021 at 09:41:37AM +0000, Chris Wilson wrote:
> > > Quoting Janusz Krzysztofik (2020-12-04 19:50:07)
> > > > We may still be interested in results of a test even if it has tainted
> > > > the kernel. On the other hand, we need to kill the test on taint if no
> > > > other means of killing it on a jam is active.
> > > >
> > > > If abort on both kernel taint or a timeout is requested, decrease all
> > > > potential timeouts significantly while the taint is detected instead of
> > > > aborting immediately. However, report the taint as the reason of the
> > > > abort if a timeout decreased by the taint expires.
> > >
> > > This has the nasty side effect of not stopping the test run after a
> > > kernel taint. Instead the next test inherits the tainted condition from
> > > the previous test and usually ends up being declared incomplete.
> > >
> > > False positives are frustrating.
> > > -Chris
> >
> >
> > Do you have a link to a test run where this happened? This patch
> > didn't change the between-tests abort checks.
>
> The taint is from the warnings in the penultimate test:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9550/shard-skl7/igt_runner20.txt
Ah, I see.
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9550/shard-skl7/dmesg20.txt
This is the tainting WARN I presume:
<4>[ 917.575173] Memory manager not clean during takedown.
<4>[ 917.575272] WARNING: CPU: 2 PID: 7 at drivers/gpu/drm/drm_mm.c:999 drm_mm_takedown+0x51/0x100
That happens after @gem, before @evict.
In other words, this is all in the same exec() of i915_selftest
--run-subtest live. Incorrect _dynamic_ subtest gets blamed.
Getting the killing right here is a bit tricky, possibly doable. Or
rather, getting the blame right is doable, killing will be inherently
racy...
--
Petri Latvala
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2021-01-07 10:06 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-04 19:50 [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts Janusz Krzysztofik
2020-12-04 20:54 ` [igt-dev] ✓ Fi.CI.BAT: success for runner: Don't kill a test on taint if watching timeouts (rev2) Patchwork
2020-12-05 0:13 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-12-07 10:46 ` Janusz Krzysztofik
2020-12-07 13:09 ` [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts Petri Latvala
2020-12-07 13:09 ` [igt-dev] " Petri Latvala
2020-12-07 13:18 ` [Intel-gfx] " Janusz Krzysztofik
2020-12-07 13:18 ` [igt-dev] " Janusz Krzysztofik
2020-12-08 17:39 ` [igt-dev] ✓ Fi.CI.IGT: success for runner: Don't kill a test on taint if watching timeouts (rev2) Patchwork
2021-01-06 9:41 ` [Intel-gfx] [PATCH i-g-t v2] runner: Don't kill a test on taint if watching timeouts Chris Wilson
2021-01-06 9:41 ` [igt-dev] " Chris Wilson
2021-01-07 9:40 ` [Intel-gfx] " Petri Latvala
2021-01-07 9:49 ` Chris Wilson
2021-01-07 9:49 ` [igt-dev] " Chris Wilson
2021-01-07 10:06 ` [Intel-gfx] [igt-dev] " Petri Latvala
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.