[igt-dev] [PATCH i-g-t] runner: Show kernel state on detecting test timeout

[igt-dev] [PATCH i-g-t] runner: Show kernel state on detecting test timeout

[Chris Wilson]

When our watchdog expires and we declare the test has timed out, we send
it a signal to terminate. The test will produce a backtrace upon receipt
of that signal, but often times (especially as we do test and debug the
kernel), the test is hung inside the kernel. So we need the kernel state
to see where the live/deadlock is occuring. Enter sysrq-t to show the
backtraces of all processes (as the one we are searching for may be
sleeping).

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Petri Latvala <petri.latvala@intel.com>
---
 runner/executor.c | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/runner/executor.c b/runner/executor.c
index 1a00237fc..cd3d3a7be 100644
--- a/runner/executor.c
+++ b/runner/executor.c
@@ -638,6 +638,14 @@ static const char *get_cmdline(pid_t pid, char *buf, ssize_t len)
 	return buf;
 }
 
+static void sysrq(char cmd)
+{
+	int fd = open("/proc/sysrq-trigger", O_WRONLY);
+
+	igt_ignore_warn(write(fd, cmd, 1));
+	close(fd);
+}
+
 /*
  * Returns:
  *  =0 - Success
@@ -728,6 +736,8 @@ static int monitor_output(pid_t child,
 
 			switch (killed) {
 			case 0:
+				sysrq('t'); /* show task state */
+
 				if (settings->log_level >= LOG_LEVEL_NORMAL) {
 					outf("Timeout. Killing the current test with SIGQUIT.\n");
 					fflush(stdout);
-- 
2.23.0

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

[igt-dev] [PATCH i-g-t v2] runner: Show kernel state on detecting test timeout

[Chris Wilson]

When our watchdog expires and we declare the test has timed out, we send
it a signal to terminate. The test will produce a backtrace upon receipt
of that signal, but often times (especially as we do test and debug the
kernel), the test is hung inside the kernel. So we need the kernel state
to see where the live/deadlock is occuring. Enter sysrq-t to show the
backtraces of all processes (as the one we are searching for may be
sleeping).

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

diff --git a/runner/executor.c b/runner/executor.c
index 1a00237fc..74102fab9 100644
--- a/runner/executor.c
+++ b/runner/executor.c
@@ -638,6 +638,20 @@ static const char *get_cmdline(pid_t pid, char *buf, ssize_t len)
 	return buf;
 }
 
+static bool sysrq(char cmd)
+{
+	bool success = false;
+	int fd;
+
+	fd = open("/proc/sysrq-trigger", O_WRONLY);
+	if (fd >= 0) {
+		success = write(fd, cmd, 1) == 1;
+		close(fd);
+	}
+
+	return success;
+}
+
 /*
  * Returns:
  *  =0 - Success
@@ -728,6 +742,8 @@ static int monitor_output(pid_t child,
 
 			switch (killed) {
 			case 0:
+				sysrq('t'); /* show task state */
+
 				if (settings->log_level >= LOG_LEVEL_NORMAL) {
 					outf("Timeout. Killing the current test with SIGQUIT.\n");
 					fflush(stdout);
-- 
2.23.0

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

[igt-dev] [PATCH i-g-t v3] runner: Show kernel state on detecting test timeout

[Chris Wilson]

When our watchdog expires and we declare the test has timed out, we send
it a signal to terminate. The test will produce a backtrace upon receipt
of that signal, but often times (especially as we do test and debug the
kernel), the test is hung inside the kernel. So we need the kernel state
to see where the live/deadlock is occuring. Enter sysrq-t to show the
backtraces of all processes (as the one we are searching for may be
sleeping).

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Petri Latvala <petri.latvala@intel.com>
---
 runner/executor.c | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/runner/executor.c b/runner/executor.c
index 1a00237fc..2bb828278 100644
--- a/runner/executor.c
+++ b/runner/executor.c
@@ -638,6 +638,25 @@ static const char *get_cmdline(pid_t pid, char *buf, ssize_t len)
 	return buf;
 }
 
+static bool sysrq(char cmd)
+{
+	bool success = false;
+	int fd;
+
+	fd = open("/proc/sysrq-trigger", O_WRONLY);
+	if (fd >= 0) {
+		success = write(fd, &cmd, 1) == 1;
+		close(fd);
+	}
+
+	return success;
+}
+
+static void show_kernel_task_state(void)
+{
+	sysrq('t');
+}
+
 /*
  * Returns:
  *  =0 - Success
@@ -728,6 +747,8 @@ static int monitor_output(pid_t child,
 
 			switch (killed) {
 			case 0:
+				show_kernel_task_state();
+
 				if (settings->log_level >= LOG_LEVEL_NORMAL) {
 					outf("Timeout. Killing the current test with SIGQUIT.\n");
 					fflush(stdout);
-- 
2.23.0

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

Re: [igt-dev] [PATCH i-g-t v3] runner: Show kernel state on detecting test timeout

[Petri Latvala]

On Fri, Oct 11, 2019 at 02:22:37PM +0100, Chris Wilson wrote:
> When our watchdog expires and we declare the test has timed out, we send
> it a signal to terminate. The test will produce a backtrace upon receipt
> of that signal, but often times (especially as we do test and debug the
> kernel), the test is hung inside the kernel. So we need the kernel state
> to see where the live/deadlock is occuring. Enter sysrq-t to show the
> backtraces of all processes (as the one we are searching for may be
> sleeping).
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Petri Latvala <petri.latvala@intel.com>
> ---
>  runner/executor.c | 21 +++++++++++++++++++++
>  1 file changed, 21 insertions(+)
> 
> diff --git a/runner/executor.c b/runner/executor.c
> index 1a00237fc..2bb828278 100644
> --- a/runner/executor.c
> +++ b/runner/executor.c
> @@ -638,6 +638,25 @@ static const char *get_cmdline(pid_t pid, char *buf, ssize_t len)
>  	return buf;
>  }
>  
> +static bool sysrq(char cmd)
> +{
> +	bool success = false;
> +	int fd;
> +
> +	fd = open("/proc/sysrq-trigger", O_WRONLY);
> +	if (fd >= 0) {
> +		success = write(fd, &cmd, 1) == 1;
> +		close(fd);
> +	}


Where does the dump go? Are we able to grab it in the test's dmesg?

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

Re: [igt-dev] [PATCH i-g-t v3] runner: Show kernel state on detecting test timeout

[Chris Wilson]

Quoting Petri Latvala (2019-10-14 07:58:35)
> On Fri, Oct 11, 2019 at 02:22:37PM +0100, Chris Wilson wrote:
> > When our watchdog expires and we declare the test has timed out, we send
> > it a signal to terminate. The test will produce a backtrace upon receipt
> > of that signal, but often times (especially as we do test and debug the
> > kernel), the test is hung inside the kernel. So we need the kernel state
> > to see where the live/deadlock is occuring. Enter sysrq-t to show the
> > backtraces of all processes (as the one we are searching for may be
> > sleeping).
> > 
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Petri Latvala <petri.latvala@intel.com>
> > ---
> >  runner/executor.c | 21 +++++++++++++++++++++
> >  1 file changed, 21 insertions(+)
> > 
> > diff --git a/runner/executor.c b/runner/executor.c
> > index 1a00237fc..2bb828278 100644
> > --- a/runner/executor.c
> > +++ b/runner/executor.c
> > @@ -638,6 +638,25 @@ static const char *get_cmdline(pid_t pid, char *buf, ssize_t len)
> >       return buf;
> >  }
> >  
> > +static bool sysrq(char cmd)
> > +{
> > +     bool success = false;
> > +     int fd;
> > +
> > +     fd = open("/proc/sysrq-trigger", O_WRONLY);
> > +     if (fd >= 0) {
> > +             success = write(fd, &cmd, 1) == 1;
> > +             close(fd);
> > +     }
> 
> 
> Where does the dump go? Are we able to grab it in the test's dmesg?

Into the dmesg.
-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 v3] runner: Show kernel state on detecting test timeout

[Petri Latvala]

On Mon, Oct 14, 2019 at 08:12:06AM +0100, Chris Wilson wrote:
> Quoting Petri Latvala (2019-10-14 07:58:35)
> > On Fri, Oct 11, 2019 at 02:22:37PM +0100, Chris Wilson wrote:
> > > When our watchdog expires and we declare the test has timed out, we send
> > > it a signal to terminate. The test will produce a backtrace upon receipt
> > > of that signal, but often times (especially as we do test and debug the
> > > kernel), the test is hung inside the kernel. So we need the kernel state
> > > to see where the live/deadlock is occuring. Enter sysrq-t to show the
> > > backtraces of all processes (as the one we are searching for may be
> > > sleeping).
> > > 
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Petri Latvala <petri.latvala@intel.com>
> > > ---
> > >  runner/executor.c | 21 +++++++++++++++++++++
> > >  1 file changed, 21 insertions(+)
> > > 
> > > diff --git a/runner/executor.c b/runner/executor.c
> > > index 1a00237fc..2bb828278 100644
> > > --- a/runner/executor.c
> > > +++ b/runner/executor.c
> > > @@ -638,6 +638,25 @@ static const char *get_cmdline(pid_t pid, char *buf, ssize_t len)
> > >       return buf;
> > >  }
> > >  
> > > +static bool sysrq(char cmd)
> > > +{
> > > +     bool success = false;
> > > +     int fd;
> > > +
> > > +     fd = open("/proc/sysrq-trigger", O_WRONLY);
> > > +     if (fd >= 0) {
> > > +             success = write(fd, &cmd, 1) == 1;
> > > +             close(fd);
> > > +     }
> > 
> > 
> > Where does the dump go? Are we able to grab it in the test's dmesg?
> 
> Into the dmesg.


Reviewed-by: Petri Latvala <petri.latvala@intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

[igt-dev] ✓ Fi.CI.BAT: success for runner: Show kernel state on detecting test timeout (rev3)

[Patchwork]

== Series Details ==

Series: runner: Show kernel state on detecting test timeout (rev3)
URL   : https://patchwork.freedesktop.org/series/67911/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_7064 -> IGTPW_3561
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

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

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

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

### IGT changes ###

#### Issues hit ####

  * igt@gem_exec_reloc@basic-cpu-read-noreloc:
    - fi-icl-u3:          [PASS][1] -> [DMESG-WARN][2] ([fdo#107724]) +1 similar issue
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/fi-icl-u3/igt@gem_exec_reloc@basic-cpu-read-noreloc.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/fi-icl-u3/igt@gem_exec_reloc@basic-cpu-read-noreloc.html

  
#### Possible fixes ####

  * igt@gem_exec_suspend@basic-s4-devices:
    - fi-blb-e6850:       [INCOMPLETE][3] ([fdo#107718]) -> [PASS][4]
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/fi-blb-e6850/igt@gem_exec_suspend@basic-s4-devices.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/fi-blb-e6850/igt@gem_exec_suspend@basic-s4-devices.html

  * igt@gem_mmap_gtt@basic-read:
    - {fi-icl-dsi}:       [DMESG-WARN][5] ([fdo#106107]) -> [PASS][6]
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/fi-icl-dsi/igt@gem_mmap_gtt@basic-read.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/fi-icl-dsi/igt@gem_mmap_gtt@basic-read.html

  * igt@i915_module_load@reload-with-fault-injection:
    - fi-cfl-8109u:       [INCOMPLETE][7] -> [PASS][8]
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/fi-cfl-8109u/igt@i915_module_load@reload-with-fault-injection.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/fi-cfl-8109u/igt@i915_module_load@reload-with-fault-injection.html

  * igt@i915_selftest@live_coherency:
    - fi-glk-dsi:         [TIMEOUT][9] ([fdo#111944]) -> [PASS][10]
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/fi-glk-dsi/igt@i915_selftest@live_coherency.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/fi-glk-dsi/igt@i915_selftest@live_coherency.html

  * igt@i915_selftest@live_workarounds:
    - fi-skl-6600u:       [DMESG-FAIL][11] -> [PASS][12]
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/fi-skl-6600u/igt@i915_selftest@live_workarounds.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/fi-skl-6600u/igt@i915_selftest@live_workarounds.html

  * igt@kms_chamelium@hdmi-hpd-fast:
    - fi-kbl-7500u:       [FAIL][13] ([fdo#111407]) -> [PASS][14]
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html

  * igt@prime_self_import@basic-llseek-size:
    - fi-icl-u3:          [DMESG-WARN][15] ([fdo#107724]) -> [PASS][16] +1 similar issue
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/fi-icl-u3/igt@prime_self_import@basic-llseek-size.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/fi-icl-u3/igt@prime_self_import@basic-llseek-size.html

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

  [fdo#102505]: https://bugs.freedesktop.org/show_bug.cgi?id=102505
  [fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107
  [fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
  [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
  [fdo#111049]: https://bugs.freedesktop.org/show_bug.cgi?id=111049
  [fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
  [fdo#111647]: https://bugs.freedesktop.org/show_bug.cgi?id=111647
  [fdo#111944]: https://bugs.freedesktop.org/show_bug.cgi?id=111944


Participating hosts (47 -> 43)
------------------------------

  Additional (2): fi-bsw-n3050 fi-pnv-d510 
  Missing    (6): fi-tgl-u fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-bdw-samus 


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

  * CI: CI-20190529 -> None
  * IGT: IGT_5221 -> IGTPW_3561

  CI-20190529: 20190529
  CI_DRM_7064: 8369232b3509a230b2d4cbd9548a8d5db444a3f2 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_3561: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/index.html
  IGT_5221: 280734ceacde4ff52c6bd5a9e3d664f77f76b85d @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

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

[igt-dev] ✓ Fi.CI.IGT: success for runner: Show kernel state on detecting test timeout (rev3)

[Patchwork]

== Series Details ==

Series: runner: Show kernel state on detecting test timeout (rev3)
URL   : https://patchwork.freedesktop.org/series/67911/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_7064_full -> IGTPW_3561_full
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

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

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

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

### IGT changes ###

#### Suppressed ####

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

  * igt@kms_busy@basic-modeset-b:
    - {shard-tglb}:       [PASS][1] -> [INCOMPLETE][2]
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-tglb7/igt@kms_busy@basic-modeset-b.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-tglb1/igt@kms_busy@basic-modeset-b.html

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

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

### IGT changes ###

#### Issues hit ####

  * igt@gem_ctx_isolation@rcs0-s3:
    - shard-apl:          [PASS][3] -> [DMESG-WARN][4] ([fdo#108566]) +5 similar issues
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-apl2/igt@gem_ctx_isolation@rcs0-s3.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-apl7/igt@gem_ctx_isolation@rcs0-s3.html

  * igt@gem_exec_schedule@preempt-other-chain-bsd:
    - shard-iclb:         [PASS][5] -> [SKIP][6] ([fdo#111325]) +3 similar issues
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb3/igt@gem_exec_schedule@preempt-other-chain-bsd.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb2/igt@gem_exec_schedule@preempt-other-chain-bsd.html

  * igt@gem_exec_schedule@preempt-queue-bsd1:
    - shard-iclb:         [PASS][7] -> [SKIP][8] ([fdo#109276]) +30 similar issues
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb4/igt@gem_exec_schedule@preempt-queue-bsd1.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb8/igt@gem_exec_schedule@preempt-queue-bsd1.html

  * igt@gem_userptr_blits@sync-unmap-cycles:
    - shard-snb:          [PASS][9] -> [DMESG-WARN][10] ([fdo#111870]) +1 similar issue
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-snb2/igt@gem_userptr_blits@sync-unmap-cycles.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-snb6/igt@gem_userptr_blits@sync-unmap-cycles.html
    - shard-hsw:          [PASS][11] -> [DMESG-WARN][12] ([fdo#111870])
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-hsw1/igt@gem_userptr_blits@sync-unmap-cycles.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-hsw1/igt@gem_userptr_blits@sync-unmap-cycles.html

  * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt:
    - shard-iclb:         [PASS][13] -> [FAIL][14] ([fdo#103167]) +4 similar issues
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt.html

  * igt@kms_psr@psr2_no_drrs:
    - shard-iclb:         [PASS][15] -> [SKIP][16] ([fdo#109441]) +1 similar issue
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb5/igt@kms_psr@psr2_no_drrs.html

  * igt@kms_setmode@basic:
    - shard-kbl:          [PASS][17] -> [FAIL][18] ([fdo#99912])
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-kbl2/igt@kms_setmode@basic.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-kbl3/igt@kms_setmode@basic.html

  
#### Possible fixes ####

  * igt@gem_ctx_shared@exec-single-timeline-bsd:
    - shard-iclb:         [SKIP][19] ([fdo#110841]) -> [PASS][20]
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb4/igt@gem_ctx_shared@exec-single-timeline-bsd.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb6/igt@gem_ctx_shared@exec-single-timeline-bsd.html

  * igt@gem_exec_schedule@reorder-wide-bsd:
    - shard-iclb:         [SKIP][21] ([fdo#111325]) -> [PASS][22] +6 similar issues
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb4/igt@gem_exec_schedule@reorder-wide-bsd.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb7/igt@gem_exec_schedule@reorder-wide-bsd.html

  * igt@gem_userptr_blits@map-fixed-invalidate-busy:
    - shard-snb:          [DMESG-WARN][23] ([fdo#111870]) -> [PASS][24] +1 similar issue
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-snb2/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-snb2/igt@gem_userptr_blits@map-fixed-invalidate-busy.html

  * igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy:
    - shard-hsw:          [DMESG-WARN][25] ([fdo#111870]) -> [PASS][26] +4 similar issues
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-hsw1/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-hsw7/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html

  * igt@i915_suspend@sysfs-reader:
    - shard-apl:          [INCOMPLETE][27] ([fdo#103927]) -> [PASS][28] +6 similar issues
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-apl3/igt@i915_suspend@sysfs-reader.html
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-apl6/igt@i915_suspend@sysfs-reader.html

  * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt:
    - shard-iclb:         [FAIL][29] ([fdo#103167]) -> [PASS][30] +8 similar issues
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt.html
   [30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt.html

  * igt@kms_frontbuffer_tracking@fbc-suspend:
    - shard-apl:          [DMESG-WARN][31] ([fdo#108566]) -> [PASS][32] +1 similar issue
   [31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-apl4/igt@kms_frontbuffer_tracking@fbc-suspend.html
   [32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-apl7/igt@kms_frontbuffer_tracking@fbc-suspend.html

  * igt@kms_plane_lowres@pipe-a-tiling-y:
    - shard-iclb:         [FAIL][33] ([fdo#103166]) -> [PASS][34]
   [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb6/igt@kms_plane_lowres@pipe-a-tiling-y.html
   [34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb2/igt@kms_plane_lowres@pipe-a-tiling-y.html

  * igt@kms_psr@no_drrs:
    - shard-iclb:         [FAIL][35] ([fdo#108341]) -> [PASS][36]
   [35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb1/igt@kms_psr@no_drrs.html
   [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb2/igt@kms_psr@no_drrs.html

  * igt@kms_psr@psr2_cursor_render:
    - shard-iclb:         [SKIP][37] ([fdo#109441]) -> [PASS][38]
   [37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb8/igt@kms_psr@psr2_cursor_render.html
   [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb2/igt@kms_psr@psr2_cursor_render.html

  * igt@kms_setmode@basic:
    - shard-hsw:          [FAIL][39] ([fdo#99912]) -> [PASS][40]
   [39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-hsw5/igt@kms_setmode@basic.html
   [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-hsw7/igt@kms_setmode@basic.html

  * igt@prime_busy@hang-bsd2:
    - shard-iclb:         [SKIP][41] ([fdo#109276]) -> [PASS][42] +16 similar issues
   [41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb6/igt@prime_busy@hang-bsd2.html
   [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb4/igt@prime_busy@hang-bsd2.html

  
#### Warnings ####

  * igt@gem_ctx_isolation@vcs1-nonpriv:
    - shard-iclb:         [FAIL][43] ([fdo#111329]) -> [SKIP][44] ([fdo#109276])
   [43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb2/igt@gem_ctx_isolation@vcs1-nonpriv.html
   [44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb7/igt@gem_ctx_isolation@vcs1-nonpriv.html

  * igt@kms_dp_dsc@basic-dsc-enable-edp:
    - shard-iclb:         [SKIP][45] ([fdo#109349]) -> [DMESG-WARN][46] ([fdo#107724])
   [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7064/shard-iclb5/igt@kms_dp_dsc@basic-dsc-enable-edp.html
   [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/shard-iclb2/igt@kms_dp_dsc@basic-dsc-enable-edp.html

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

  [fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
  [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
  [fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
  [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
  [fdo#108341]: https://bugs.freedesktop.org/show_bug.cgi?id=108341
  [fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
  [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
  [fdo#109349]: https://bugs.freedesktop.org/show_bug.cgi?id=109349
  [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
  [fdo#110841]: https://bugs.freedesktop.org/show_bug.cgi?id=110841
  [fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325
  [fdo#111329]: https://bugs.freedesktop.org/show_bug.cgi?id=111329
  [fdo#111830 ]: https://bugs.freedesktop.org/show_bug.cgi?id=111830 
  [fdo#111865]: https://bugs.freedesktop.org/show_bug.cgi?id=111865
  [fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
  [fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912


Participating hosts (11 -> 7)
------------------------------

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


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

  * CI: CI-20190529 -> None
  * IGT: IGT_5221 -> IGTPW_3561
  * Piglit: piglit_4509 -> None

  CI-20190529: 20190529
  CI_DRM_7064: 8369232b3509a230b2d4cbd9548a8d5db444a3f2 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_3561: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3561/index.html
  IGT_5221: 280734ceacde4ff52c6bd5a9e3d664f77f76b85d @ 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_3561/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev