[igt-dev] [PATCH i-g-t 1/2] runner: Actually ping watchdogs every interval

[igt-dev] [PATCH i-g-t 1/2] runner: Actually ping watchdogs every interval

[Petri Latvala]

The split to timeout intervals was made to accomodate for watchdogs
that cannot use a timeout as high as we wanted. Actually using that
feature requires us to ping the watchdog every interval even though we
handle actual timeouting after all intervals are used up.

Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
---
 runner/executor.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/runner/executor.c b/runner/executor.c
index ba58fb17..e6086772 100644
--- a/runner/executor.c
+++ b/runner/executor.c
@@ -734,6 +734,8 @@ static int monitor_output(pid_t child,
 			FD_SET(sigfd, &set);
 
 		n = select(nfds, &set, NULL, NULL, timeout == 0 ? NULL : &tv);
+		ping_watchdogs();
+
 		if (n < 0) {
 			/* TODO */
 			return -1;
@@ -743,8 +745,6 @@ static int monitor_output(pid_t child,
 			if (--intervals_left)
 				continue;
 
-			ping_watchdogs();
-
 			switch (killed) {
 			case 0:
 				show_kernel_task_state();
@@ -807,7 +807,6 @@ static int monitor_output(pid_t child,
 		}
 
 		intervals_left = timeout_intervals;
-		ping_watchdogs();
 
 		/* TODO: Refactor these handlers to their own functions */
 		if (outfd >= 0 && FD_ISSET(outfd, &set)) {
-- 
2.19.1

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

[igt-dev] [PATCH i-g-t 2/2] runner: Don't wait forever for processes to die

[Petri Latvala]

While the originally written timeout for process killing (2 seconds)
was way too short, waiting indefinitely is suboptimal as well. We're
seeing cases where the test is stuck for possibly hours in
uninterruptible sleep (IO). Wait a fairly longer selected time period
of 2 minutes, because even making progress for that long means the
machine is in bad enough state to require a good kicking and booting.

Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
---
 runner/executor.c | 28 ++++++++++++++++------------
 1 file changed, 16 insertions(+), 12 deletions(-)

diff --git a/runner/executor.c b/runner/executor.c
index e6086772..b58c98e6 100644
--- a/runner/executor.c
+++ b/runner/executor.c
@@ -776,25 +776,29 @@ static int monitor_output(pid_t child,
 				if (!kill_child(killed, child))
 					return -1;
 
-				intervals_left = timeout_intervals = 1;
-				break;
-			case SIGKILL:
 				/*
-				 * If the child still exists, and the kernel
-				 * hasn't oopsed, assume it is still making
-				 * forward progress towards exiting (i.e. still
-				 * freeing all of its resources).
+				 * Allow the test two minutes to die
+				 * on SIGKILL. If it takes more than
+				 * that, we're quite likely in a
+				 * scenario where we want to reboot
+				 * the machine anyway.
 				 */
-				if (kill(child, 0) == 0 && !tainted(&taints)) {
-					intervals_left =  1;
-					break;
-				}
-
+				watchdogs_set_timeout(120);
+				timeout = 20;
+				intervals_left = timeout_intervals = 120 / timeout;
+				break;
+			case SIGKILL:
 				/* Nothing that can be done, really. Let's tell the caller we want to abort. */
+
 				if (settings->log_level >= LOG_LEVEL_NORMAL) {
+					tainted(&taints);
 					errf("Child refuses to die, tainted %lx. Aborting.\n",
 					     taints);
+					if (kill(child, 0) == 0)
+						errf("The test process no longer exists, "
+						     "but we didn't get informed of its demise...\n");
 				}
+
 				close_watchdogs(settings);
 				free(outbuf);
 				close(outfd);
-- 
2.19.1

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

Re: [igt-dev] [PATCH i-g-t 2/2] runner: Don't wait forever for processes to die

[Chris Wilson]

Quoting Petri Latvala (2019-12-03 10:44:57)
> While the originally written timeout for process killing (2 seconds)
> was way too short, waiting indefinitely is suboptimal as well. We're
> seeing cases where the test is stuck for possibly hours in
> uninterruptible sleep (IO). Wait a fairly longer selected time period
> of 2 minutes, because even making progress for that long means the
> machine is in bad enough state to require a good kicking and booting.

I'd still vote for a fast exit if we know we have oopsed. No point
waiting 2 minutes for children we know can't die.
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t 2/2] runner: Don't wait forever for processes to die

[Petri Latvala]

On Tue, Dec 03, 2019 at 10:53:51AM +0000, Chris Wilson wrote:
> Quoting Petri Latvala (2019-12-03 10:44:57)
> > While the originally written timeout for process killing (2 seconds)
> > was way too short, waiting indefinitely is suboptimal as well. We're
> > seeing cases where the test is stuck for possibly hours in
> > uninterruptible sleep (IO). Wait a fairly longer selected time period
> > of 2 minutes, because even making progress for that long means the
> > machine is in bad enough state to require a good kicking and booting.
> 
> I'd still vote for a fast exit if we know we have oopsed. No point
> waiting 2 minutes for children we know can't die.

Yes, good point. v2 coming up.


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

[igt-dev] [PATCH i-g-t v2 2/2] runner: Don't wait forever for processes to die

[Petri Latvala]

While the originally written timeout for process killing (2 seconds)
was way too short, waiting indefinitely is suboptimal as well. We're
seeing cases where the test is stuck for possibly hours in
uninterruptible sleep (IO). Wait a fairly longer selected time period
of 2 minutes, because even making progress for that long means the
machine is in bad enough state to require a good kicking and booting.

v2:
 - Abort quicker if kernel is tainted (Chris)
 - Correctly convert process-exists check with kill() to process-does-not-exist

Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
---
 runner/executor.c | 29 ++++++++++++++++++++---------
 1 file changed, 20 insertions(+), 9 deletions(-)

diff --git a/runner/executor.c b/runner/executor.c
index e6086772..f36bfd3d 100644
--- a/runner/executor.c
+++ b/runner/executor.c
@@ -682,6 +682,9 @@ static int monitor_output(pid_t child,
 	int timeout_intervals = 1, intervals_left;
 	int wd_extra = 10;
 	int killed = 0; /* 0 if not killed, signal number otherwise */
+	int sigkill_timeout = 120;
+	int sigkill_interval = 20;
+	int sigkill_intervals_left = sigkill_timeout / sigkill_interval;
 	struct timespec time_beg, time_end;
 	unsigned long taints = 0;
 	bool aborting = false;
@@ -776,25 +779,33 @@ static int monitor_output(pid_t child,
 				if (!kill_child(killed, child))
 					return -1;
 
-				intervals_left = timeout_intervals = 1;
-				break;
-			case SIGKILL:
 				/*
-				 * If the child still exists, and the kernel
-				 * hasn't oopsed, assume it is still making
-				 * forward progress towards exiting (i.e. still
-				 * freeing all of its resources).
+				 * Allow the test two minutes to die
+				 * on SIGKILL. If it takes more than
+				 * that, we're quite likely in a
+				 * scenario where we want to reboot
+				 * the machine anyway.
 				 */
-				if (kill(child, 0) == 0 && !tainted(&taints)) {
-					intervals_left =  1;
+				watchdogs_set_timeout(sigkill_timeout);
+				timeout = sigkill_interval;
+				intervals_left = 1; /* Intervals handled separately for sigkill */
+				break;
+			case SIGKILL:
+				if (!tainted(&taints) && --sigkill_intervals_left) {
+					intervals_left = 1;
 					break;
 				}
 
 				/* Nothing that can be done, really. Let's tell the caller we want to abort. */
+
 				if (settings->log_level >= LOG_LEVEL_NORMAL) {
 					errf("Child refuses to die, tainted %lx. Aborting.\n",
 					     taints);
+					if (kill(child, 0) && errno == ESRCH)
+						errf("The test process no longer exists, "
+						     "but we didn't get informed of its demise...\n");
 				}
+
 				close_watchdogs(settings);
 				free(outbuf);
 				close(outfd);
-- 
2.19.1

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

Re: [igt-dev] [PATCH i-g-t v2 2/2] runner: Don't wait forever for processes to die

[Chris Wilson]

Quoting Petri Latvala (2019-12-03 11:15:37)
> While the originally written timeout for process killing (2 seconds)
> was way too short, waiting indefinitely is suboptimal as well. We're
> seeing cases where the test is stuck for possibly hours in
> uninterruptible sleep (IO). Wait a fairly longer selected time period
> of 2 minutes, because even making progress for that long means the
> machine is in bad enough state to require a good kicking and booting.
> 
> v2:
>  - Abort quicker if kernel is tainted (Chris)
>  - Correctly convert process-exists check with kill() to process-does-not-exist
> 
> Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>

Reads like it does what you say on the tin.
Reviewed-by Cc: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Re: [igt-dev] [PATCH i-g-t 1/2] runner: Actually ping watchdogs every interval

[Chris Wilson]

Quoting Petri Latvala (2019-12-03 10:44:56)
> The split to timeout intervals was made to accomodate for watchdogs
> that cannot use a timeout as high as we wanted. Actually using that
> feature requires us to ping the watchdog every interval even though we
> handle actual timeouting after all intervals are used up.
> 
> Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>

Doesn't look harmful. The implication is that we ping the watchdog for
some cases where we did not previously, but for as long as the runner
remains in controls, that should not be an issue.

Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

[igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] runner: Actually ping watchdogs every interval (rev2)

[Patchwork]

== Series Details ==

Series: series starting with [i-g-t,1/2] runner: Actually ping watchdogs every interval (rev2)
URL   : https://patchwork.freedesktop.org/series/70350/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_7469 -> IGTPW_3801
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

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

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

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

### IGT changes ###

#### Issues hit ####

  * igt@i915_pm_rpm@module-reload:
    - fi-skl-6770hq:      [PASS][1] -> [FAIL][2] ([i915#178])
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html
    - fi-skl-lmem:        [PASS][3] -> [DMESG-WARN][4] ([i915#592])
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/fi-skl-lmem/igt@i915_pm_rpm@module-reload.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/fi-skl-lmem/igt@i915_pm_rpm@module-reload.html

  * igt@i915_selftest@live_blt:
    - fi-ivb-3770:        [PASS][5] -> [DMESG-FAIL][6] ([i915#563])
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/fi-ivb-3770/igt@i915_selftest@live_blt.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/fi-ivb-3770/igt@i915_selftest@live_blt.html

  
#### Possible fixes ####

  * igt@i915_module_load@reload:
    - fi-bwr-2160:        [INCOMPLETE][7] ([i915#695]) -> [PASS][8]
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/fi-bwr-2160/igt@i915_module_load@reload.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/fi-bwr-2160/igt@i915_module_load@reload.html

  * igt@i915_pm_rpm@basic-pci-d3-state:
    - fi-hsw-4770:        [SKIP][9] ([fdo#109271]) -> [PASS][10] +1 similar issue
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/fi-hsw-4770/igt@i915_pm_rpm@basic-pci-d3-state.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/fi-hsw-4770/igt@i915_pm_rpm@basic-pci-d3-state.html

  * igt@i915_selftest@live_blt:
    - fi-hsw-4770r:       [DMESG-FAIL][11] ([i915#683]) -> [PASS][12]
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/fi-hsw-4770r/igt@i915_selftest@live_blt.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/fi-hsw-4770r/igt@i915_selftest@live_blt.html

  * igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size:
    - fi-icl-dsi:         [DMESG-WARN][13] ([i915#109]) -> [PASS][14]
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/fi-icl-dsi/igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/fi-icl-dsi/igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size.html

  
#### Warnings ####

  * igt@gem_exec_suspend@basic-s3:
    - fi-kbl-x1275:       [DMESG-WARN][15] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][16] ([i915#62] / [i915#92]) +2 similar issues
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/fi-kbl-x1275/igt@gem_exec_suspend@basic-s3.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/fi-kbl-x1275/igt@gem_exec_suspend@basic-s3.html

  * igt@kms_chamelium@vga-edid-read:
    - fi-icl-u2:          [FAIL][17] ([i915#217]) -> [SKIP][18] ([fdo#109309])
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/fi-icl-u2/igt@kms_chamelium@vga-edid-read.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/fi-icl-u2/igt@kms_chamelium@vga-edid-read.html

  * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
    - fi-kbl-x1275:       [DMESG-WARN][19] ([i915#62] / [i915#92]) -> [DMESG-WARN][20] ([i915#62] / [i915#92] / [i915#95]) +5 similar issues
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/fi-kbl-x1275/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/fi-kbl-x1275/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html

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

  [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
  [fdo#109309]: https://bugs.freedesktop.org/show_bug.cgi?id=109309
  [i915#109]: https://gitlab.freedesktop.org/drm/intel/issues/109
  [i915#178]: https://gitlab.freedesktop.org/drm/intel/issues/178
  [i915#192]: https://gitlab.freedesktop.org/drm/intel/issues/192
  [i915#193]: https://gitlab.freedesktop.org/drm/intel/issues/193
  [i915#194]: https://gitlab.freedesktop.org/drm/intel/issues/194
  [i915#217]: https://gitlab.freedesktop.org/drm/intel/issues/217
  [i915#563]: https://gitlab.freedesktop.org/drm/intel/issues/563
  [i915#592]: https://gitlab.freedesktop.org/drm/intel/issues/592
  [i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
  [i915#683]: https://gitlab.freedesktop.org/drm/intel/issues/683
  [i915#695]: https://gitlab.freedesktop.org/drm/intel/issues/695
  [i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
  [i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95


Participating hosts (49 -> 45)
------------------------------

  Missing    (4): fi-ctg-p8600 fi-ilk-m540 fi-bsw-cyan fi-bdw-samus 


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

  * CI: CI-20190529 -> None
  * IGT: IGT_5322 -> IGTPW_3801

  CI-20190529: 20190529
  CI_DRM_7469: 5259c8ac714368fcfb009a79f3adb4a1217cfc63 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_3801: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/index.html
  IGT_5322: c7cb730383baae21f9dab4319f51a7e9dce0a843 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

[igt-dev] ✗ Fi.CI.IGT: failure for series starting with [i-g-t,1/2] runner: Actually ping watchdogs every interval (rev2)

[Patchwork]

== Series Details ==

Series: series starting with [i-g-t,1/2] runner: Actually ping watchdogs every interval (rev2)
URL   : https://patchwork.freedesktop.org/series/70350/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_7469_full -> IGTPW_3801_full
====================================================

Summary
-------

  **FAILURE**

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

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

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

### IGT changes ###

#### Possible regressions ####

  * igt@runner@aborted:
    - shard-apl:          NOTRUN -> [FAIL][1]
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-apl2/igt@runner@aborted.html

  
#### Suppressed ####

  The following results come from untrusted machines, tests, or statuses.
  They do not affect the overall result.

  * {igt@gem_exec_parse_blt@allowed-single}:
    - shard-apl:          [PASS][2] -> [DMESG-WARN][3]
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-apl8/igt@gem_exec_parse_blt@allowed-single.html
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-apl2/igt@gem_exec_parse_blt@allowed-single.html

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

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

### IGT changes ###

#### Issues hit ####

  * igt@gem_ctx_shared@q-promotion-bsd2:
    - shard-iclb:         [PASS][4] -> [SKIP][5] ([fdo#109276]) +1 similar issue
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-iclb4/igt@gem_ctx_shared@q-promotion-bsd2.html
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-iclb6/igt@gem_ctx_shared@q-promotion-bsd2.html

  * igt@gem_eio@kms:
    - shard-hsw:          [PASS][6] -> [DMESG-WARN][7] ([i915#44])
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-hsw4/igt@gem_eio@kms.html
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-hsw5/igt@gem_eio@kms.html

  * igt@gem_exec_parallel@bcs0-contexts:
    - shard-hsw:          [PASS][8] -> [FAIL][9] ([i915#676])
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-hsw2/igt@gem_exec_parallel@bcs0-contexts.html
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-hsw5/igt@gem_exec_parallel@bcs0-contexts.html

  * igt@gem_exec_parallel@vcs1:
    - shard-iclb:         [PASS][10] -> [SKIP][11] ([fdo#112080]) +2 similar issues
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-iclb2/igt@gem_exec_parallel@vcs1.html
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-iclb5/igt@gem_exec_parallel@vcs1.html

  * igt@gem_exec_reuse@single:
    - shard-tglb:         [PASS][12] -> [INCOMPLETE][13] ([i915#435])
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-tglb9/igt@gem_exec_reuse@single.html
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-tglb4/igt@gem_exec_reuse@single.html

  * igt@gem_exec_schedule@preempt-queue-chain-bsd2:
    - shard-tglb:         [PASS][14] -> [INCOMPLETE][15] ([fdo#111677])
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-tglb3/igt@gem_exec_schedule@preempt-queue-chain-bsd2.html
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-tglb6/igt@gem_exec_schedule@preempt-queue-chain-bsd2.html

  * igt@gem_exec_schedule@reorder-wide-bsd:
    - shard-iclb:         [PASS][16] -> [SKIP][17] ([fdo#112146]) +1 similar issue
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-iclb7/igt@gem_exec_schedule@reorder-wide-bsd.html
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-iclb2/igt@gem_exec_schedule@reorder-wide-bsd.html

  * igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing:
    - shard-kbl:          [PASS][18] -> [TIMEOUT][19] ([i915#530])
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-kbl7/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-kbl6/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html

  * igt@gem_sync@basic-each:
    - shard-tglb:         [PASS][20] -> [INCOMPLETE][21] ([fdo#111998] / [i915#472])
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-tglb7/igt@gem_sync@basic-each.html
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-tglb5/igt@gem_sync@basic-each.html

  * igt@gem_sync@basic-store-all:
    - shard-tglb:         [PASS][22] -> [INCOMPLETE][23] ([i915#472])
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-tglb4/igt@gem_sync@basic-store-all.html
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-tglb6/igt@gem_sync@basic-store-all.html

  * igt@gem_userptr_blits@dmabuf-sync:
    - shard-snb:          [PASS][24] -> [DMESG-WARN][25] ([fdo#111870]) +1 similar issue
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-snb4/igt@gem_userptr_blits@dmabuf-sync.html
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-snb5/igt@gem_userptr_blits@dmabuf-sync.html

  * igt@i915_selftest@live_blt:
    - shard-hsw:          [PASS][26] -> [DMESG-FAIL][27] ([i915#553])
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-hsw6/igt@i915_selftest@live_blt.html
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-hsw1/igt@i915_selftest@live_blt.html

  * igt@kms_cursor_crc@pipe-b-cursor-suspend:
    - shard-iclb:         [PASS][28] -> [DMESG-WARN][29] ([fdo#111764])
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-iclb8/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-iclb6/igt@kms_cursor_crc@pipe-b-cursor-suspend.html

  * igt@kms_flip@flip-vs-suspend-interruptible:
    - shard-apl:          [PASS][30] -> [DMESG-WARN][31] ([i915#180]) +1 similar issue
   [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-apl2/igt@kms_flip@flip-vs-suspend-interruptible.html
   [31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-apl6/igt@kms_flip@flip-vs-suspend-interruptible.html

  * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render:
    - shard-kbl:          [PASS][32] -> [INCOMPLETE][33] ([fdo#103665]) +1 similar issue
   [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render.html
   [33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render.html

  * igt@kms_frontbuffer_tracking@fbc-indfb-scaledprimary:
    - shard-kbl:          [PASS][34] -> [INCOMPLETE][35] ([fdo#103665] / [i915#634])
   [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-kbl3/igt@kms_frontbuffer_tracking@fbc-indfb-scaledprimary.html
   [35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-kbl3/igt@kms_frontbuffer_tracking@fbc-indfb-scaledprimary.html

  * igt@kms_frontbuffer_tracking@fbc-suspend:
    - shard-kbl:          [PASS][36] -> [DMESG-WARN][37] ([i915#180]) +3 similar issues
   [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-kbl2/igt@kms_frontbuffer_tracking@fbc-suspend.html
   [37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-kbl7/igt@kms_frontbuffer_tracking@fbc-suspend.html
    - shard-tglb:         [PASS][38] -> [INCOMPLETE][39] ([i915#456] / [i915#460] / [i915#474])
   [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-tglb9/igt@kms_frontbuffer_tracking@fbc-suspend.html
   [39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-tglb4/igt@kms_frontbuffer_tracking@fbc-suspend.html

  * igt@kms_frontbuffer_tracking@fbcpsr-1p-pri-indfb-multidraw:
    - shard-tglb:         [PASS][40] -> [INCOMPLETE][41] ([i915#474])
   [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-tglb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-pri-indfb-multidraw.html
   [41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-tglb3/igt@kms_frontbuffer_tracking@fbcpsr-1p-pri-indfb-multidraw.html

  * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render:
    - shard-iclb:         [PASS][42] -> [FAIL][43] ([i915#49]) +7 similar issues
   [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-iclb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render.html
   [43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-iclb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render.html

  * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-cpu:
    - shard-tglb:         [PASS][44] -> [FAIL][45] ([i915#49])
   [44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-tglb7/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-cpu.html
   [45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-tglb3/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-cpu.html

  
#### Possible fixes ####

  * igt@gem_ctx_isolation@vcs1-dirty-switch:
    - shard-iclb:         [SKIP][46] ([fdo#109276] / [fdo#112080]) -> [PASS][47]
   [46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-iclb3/igt@gem_ctx_isolation@vcs1-dirty-switch.html
   [47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-iclb2/igt@gem_ctx_isolation@vcs1-dirty-switch.html

  * igt@gem_exec_flush@basic-wb-pro-default:
    - shard-tglb:         [FAIL][48] ([fdo#111597]) -> [PASS][49]
   [48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-tglb8/igt@gem_exec_flush@basic-wb-pro-default.html
   [49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-tglb9/igt@gem_exec_flush@basic-wb-pro-default.html

  * igt@gem_exec_parallel@vcs0-contexts:
    - shard-hsw:          [FAIL][50] ([i915#676]) -> [PASS][51]
   [50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-hsw4/igt@gem_exec_parallel@vcs0-contexts.html
   [51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-hsw2/igt@gem_exec_parallel@vcs0-contexts.html

  * igt@gem_exec_schedule@independent-bsd2:
    - shard-iclb:         [SKIP][52] ([fdo#109276]) -> [PASS][53] +8 similar issues
   [52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-iclb3/igt@gem_exec_schedule@independent-bsd2.html
   [53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-iclb4/igt@gem_exec_schedule@independent-bsd2.html

  * {igt@gem_exec_schedule@pi-distinct-iova-bsd}:
    - shard-iclb:         [SKIP][54] ([i915#677]) -> [PASS][55]
   [54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-iclb1/igt@gem_exec_schedule@pi-distinct-iova-bsd.html
   [55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-iclb3/igt@gem_exec_schedule@pi-distinct-iova-bsd.html

  * igt@gem_exec_schedule@preempt-queue-chain-vebox:
    - shard-glk:          [INCOMPLETE][56] ([i915#58] / [k.org#198133]) -> [PASS][57]
   [56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-glk9/igt@gem_exec_schedule@preempt-queue-chain-vebox.html
   [57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-glk4/igt@gem_exec_schedule@preempt-queue-chain-vebox.html

  * igt@gem_mmap_gtt@hang:
    - shard-snb:          [INCOMPLETE][58] ([i915#82]) -> [PASS][59]
   [58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-snb6/igt@gem_mmap_gtt@hang.html
   [59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-snb5/igt@gem_mmap_gtt@hang.html

  * igt@gem_userptr_blits@map-fixed-invalidate-busy-gup:
    - shard-snb:          [DMESG-WARN][60] ([fdo#111870]) -> [PASS][61] +2 similar issues
   [60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
   [61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html

  * igt@kms_cursor_crc@pipe-a-cursor-128x128-sliding:
    - shard-apl:          [FAIL][62] ([i915#54]) -> [PASS][63]
   [62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-apl8/igt@kms_cursor_crc@pipe-a-cursor-128x128-sliding.html
   [63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-apl6/igt@kms_cursor_crc@pipe-a-cursor-128x128-sliding.html
    - shard-glk:          [FAIL][64] ([i915#54]) -> [PASS][65]
   [64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-glk5/igt@kms_cursor_crc@pipe-a-cursor-128x128-sliding.html
   [65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-glk1/igt@kms_cursor_crc@pipe-a-cursor-128x128-sliding.html
    - shard-kbl:          [FAIL][66] ([i915#54]) -> [PASS][67]
   [66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-128x128-sliding.html
   [67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-kbl7/igt@kms_cursor_crc@pipe-a-cursor-128x128-sliding.html

  * igt@kms_cursor_crc@pipe-c-cursor-suspend:
    - shard-kbl:          [DMESG-WARN][68] ([i915#180]) -> [PASS][69] +2 similar issues
   [68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-kbl1/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
   [69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-kbl2/igt@kms_cursor_crc@pipe-c-cursor-suspend.html

  * igt@kms_frontbuffer_tracking@fbc-rgb565-draw-pwrite:
    - shard-iclb:         [FAIL][70] ([i915#49]) -> [PASS][71] +1 similar issue
   [70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-iclb2/igt@kms_frontbuffer_tracking@fbc-rgb565-draw-pwrite.html
   [71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-rgb565-draw-pwrite.html
    - shard-tglb:         [FAIL][72] ([i915#49]) -> [PASS][73]
   [72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-tglb3/igt@kms_frontbuffer_tracking@fbc-rgb565-draw-pwrite.html
   [73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-tglb3/igt@kms_frontbuffer_tracking@fbc-rgb565-draw-pwrite.html

  * igt@kms_plane@pixel-format-pipe-b-planes:
    - shard-kbl:          [INCOMPLETE][74] ([fdo#103665]) -> [PASS][75] +3 similar issues
   [74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-kbl6/igt@kms_plane@pixel-format-pipe-b-planes.html
   [75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-kbl1/igt@kms_plane@pixel-format-pipe-b-planes.html

  * igt@kms_psr@psr2_cursor_render:
    - shard-iclb:         [SKIP][76] ([fdo#109441]) -> [PASS][77] +1 similar issue
   [76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-iclb3/igt@kms_psr@psr2_cursor_render.html
   [77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-iclb2/igt@kms_psr@psr2_cursor_render.html

  * igt@kms_setmode@basic:
    - shard-hsw:          [FAIL][78] ([i915#31]) -> [PASS][79]
   [78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-hsw8/igt@kms_setmode@basic.html
   [79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-hsw6/igt@kms_setmode@basic.html

  * igt@perf_pmu@busy-check-all-vcs1:
    - shard-iclb:         [SKIP][80] ([fdo#112080]) -> [PASS][81] +7 similar issues
   [80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-iclb7/igt@perf_pmu@busy-check-all-vcs1.html
   [81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-iclb4/igt@perf_pmu@busy-check-all-vcs1.html

  
#### Warnings ####

  * igt@gem_ctx_isolation@vcs2-dirty-switch:
    - shard-tglb:         [SKIP][82] ([fdo#111912] / [fdo#112080]) -> [SKIP][83] ([fdo#112080])
   [82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-tglb6/igt@gem_ctx_isolation@vcs2-dirty-switch.html
   [83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-tglb9/igt@gem_ctx_isolation@vcs2-dirty-switch.html

  * igt@gem_exec_parallel@contexts:
    - shard-hsw:          [TIMEOUT][84] ([i915#676]) -> [FAIL][85] ([i915#676])
   [84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7469/shard-hsw5/igt@gem_exec_parallel@contexts.html
   [85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/shard-hsw1/igt@gem_exec_parallel@contexts.html

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

  [fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
  [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
  [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
  [fdo#111597]: https://bugs.freedesktop.org/show_bug.cgi?id=111597
  [fdo#111677]: https://bugs.freedesktop.org/show_bug.cgi?id=111677
  [fdo#111764]: https://bugs.freedesktop.org/show_bug.cgi?id=111764
  [fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
  [fdo#111912]: https://bugs.freedesktop.org/show_bug.cgi?id=111912
  [fdo#111998]: https://bugs.freedesktop.org/show_bug.cgi?id=111998
  [fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
  [fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146
  [fdo#112271]: https://bugs.freedesktop.org/show_bug.cgi?id=112271
  [i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
  [i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
  [i915#435]: https://gitlab.freedesktop.org/drm/intel/issues/435
  [i915#44]: https://gitlab.freedesktop.org/drm/intel/issues/44
  [i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456
  [i915#460]: https://gitlab.freedesktop.org/drm/intel/issues/460
  [i915#472]: https://gitlab.freedesktop.org/drm/intel/issues/472
  [i915#474]: https://gitlab.freedesktop.org/drm/intel/issues/474
  [i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
  [i915#530]: https://gitlab.freedesktop.org/drm/intel/issues/530
  [i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
  [i915#553]: https://gitlab.freedesktop.org/drm/intel/issues/553
  [i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58
  [i915#634]: https://gitlab.freedesktop.org/drm/intel/issues/634
  [i915#676]: https://gitlab.freedesktop.org/drm/intel/issues/676
  [i915#677]: https://gitlab.freedesktop.org/drm/intel/issues/677
  [i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
  [k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133


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

  Missing    (3): pig-skl-6260u pig-glk-j5005 pig-hsw-4770r 


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

  * CI: CI-20190529 -> None
  * IGT: IGT_5322 -> IGTPW_3801
  * Piglit: piglit_4509 -> None

  CI-20190529: 20190529
  CI_DRM_7469: 5259c8ac714368fcfb009a79f3adb4a1217cfc63 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_3801: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3801/index.html
  IGT_5322: c7cb730383baae21f9dab4319f51a7e9dce0a843 @ 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_3801/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev