[PATCH i-g-t] i915/gem_mmap_gtt: Run forked mmap tests on tgl

[PATCH i-g-t] i915/gem_mmap_gtt: Run forked mmap tests on tgl

[Chris Wilson]

Tigerlake does not seem to be suffering from the same fault as Icelake
did, so let the tests run as they should complete within the timeout.

Early tgl results:

basic-small-copy: SUCCESS (1,671s)
forked-basic-small-copy: SUCCESS (37,568s)

medium-copy: SUCCESS (3,307s)
forked-medium-copy: SUCCESS (76,614s)
forked-medium-copy-XY: SUCCESS (203,251s)
forked-medium-copy-odd: SUCCESS (204,265s)

Not great, but nowhere near as bad as icl,
       single      forked
glk:    2.15s       2.89s
icl:    2.50s     281.08s

References: https://bugs.freedesktop.org/show_bug.cgi?id=110882
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: Martin Peres <martin.peres@linux.intel.com>
---
 tests/i915/gem_mmap_gtt.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c
index ac439cdf8..e2c6ad9a0 100644
--- a/tests/i915/gem_mmap_gtt.c
+++ b/tests/i915/gem_mmap_gtt.c
@@ -792,7 +792,7 @@ test_huge_copy(int fd, int huge, int tiling_a, int tiling_b, int ncpus)
 	uint64_t huge_object_size, i;
 	unsigned mode = CHECK_RAM;
 
-	igt_fail_on_f(intel_gen(devid) >= 11 && ncpus > 1,
+	igt_fail_on_f(intel_gen(devid) == 11 && ncpus > 1,
 		      "Please adjust your expectations, https://bugs.freedesktop.org/show_bug.cgi?id=110882\n");
 
 	switch (huge) {
-- 
2.23.0

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [PATCH i-g-t] i915/gem_mmap_gtt: Run forked mmap tests on tgl

[Martin Peres]

On 17/09/2019 14:23, Chris Wilson wrote:
> Tigerlake does not seem to be suffering from the same fault as Icelake
> did, so let the tests run as they should complete within the timeout.
> 
> Early tgl results:
> 
> basic-small-copy: SUCCESS (1,671s)
> forked-basic-small-copy: SUCCESS (37,568s)
> 
> medium-copy: SUCCESS (3,307s)
> forked-medium-copy: SUCCESS (76,614s)
> forked-medium-copy-XY: SUCCESS (203,251s)
> forked-medium-copy-odd: SUCCESS (204,265s)

Thanks for checking this out!

3 minutes for a subtest is still an eternity... How much lost coverage
would it be if we did not execute the non-small forked test?

Martin

> 
> Not great, but nowhere near as bad as icl,
>        single      forked
> glk:    2.15s       2.89s
> icl:    2.50s     281.08s
> 
> References: https://bugs.freedesktop.org/show_bug.cgi?id=110882
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Cc: Martin Peres <martin.peres@linux.intel.com>
> ---
>  tests/i915/gem_mmap_gtt.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c
> index ac439cdf8..e2c6ad9a0 100644
> --- a/tests/i915/gem_mmap_gtt.c
> +++ b/tests/i915/gem_mmap_gtt.c
> @@ -792,7 +792,7 @@ test_huge_copy(int fd, int huge, int tiling_a, int tiling_b, int ncpus)
>  	uint64_t huge_object_size, i;
>  	unsigned mode = CHECK_RAM;
>  
> -	igt_fail_on_f(intel_gen(devid) >= 11 && ncpus > 1,
> +	igt_fail_on_f(intel_gen(devid) == 11 && ncpus > 1,
>  		      "Please adjust your expectations, https://bugs.freedesktop.org/show_bug.cgi?id=110882\n");
>  
>  	switch (huge) {
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [PATCH i-g-t] i915/gem_mmap_gtt: Run forked mmap tests on tgl

[Chris Wilson]

Quoting Martin Peres (2019-09-17 12:37:25)
> 
> 
> On 17/09/2019 14:23, Chris Wilson wrote:
> > Tigerlake does not seem to be suffering from the same fault as Icelake
> > did, so let the tests run as they should complete within the timeout.
> > 
> > Early tgl results:
> > 
> > basic-small-copy: SUCCESS (1,671s)
> > forked-basic-small-copy: SUCCESS (37,568s)
> > 
> > medium-copy: SUCCESS (3,307s)
> > forked-medium-copy: SUCCESS (76,614s)
> > forked-medium-copy-XY: SUCCESS (203,251s)
> > forked-medium-copy-odd: SUCCESS (204,265s)
> 
> Thanks for checking this out!
> 
> 3 minutes for a subtest is still an eternity... How much lost coverage
> would it be if we did not execute the non-small forked test?

The others check out the partial fencing, which in theory is checked
extensively in the selftests (live_mman). It shouldn't be an issue, but
it was the forked-medium-copy that hit the timeout and so warned us
about icl. ~o~

* starts playing on his tiny fiddle to the tune of EzBench
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [PATCH i-g-t] i915/gem_mmap_gtt: Run forked mmap tests on tgl

[Mika Kuoppala]

Chris Wilson <chris@chris-wilson.co.uk> writes:

> Tigerlake does not seem to be suffering from the same fault as Icelake
> did, so let the tests run as they should complete within the timeout.
>
> Early tgl results:
>
> basic-small-copy: SUCCESS (1,671s)
> forked-basic-small-copy: SUCCESS (37,568s)
>
> medium-copy: SUCCESS (3,307s)
> forked-medium-copy: SUCCESS (76,614s)
> forked-medium-copy-XY: SUCCESS (203,251s)
> forked-medium-copy-odd: SUCCESS (204,265s)
>
> Not great, but nowhere near as bad as icl,
>        single      forked
> glk:    2.15s       2.89s
> icl:    2.50s     281.08s
>
> References: https://bugs.freedesktop.org/show_bug.cgi?id=110882
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Cc: Martin Peres <martin.peres@linux.intel.com>
> ---
>  tests/i915/gem_mmap_gtt.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c
> index ac439cdf8..e2c6ad9a0 100644
> --- a/tests/i915/gem_mmap_gtt.c
> +++ b/tests/i915/gem_mmap_gtt.c
> @@ -792,7 +792,7 @@ test_huge_copy(int fd, int huge, int tiling_a, int tiling_b, int ncpus)
>  	uint64_t huge_object_size, i;
>  	unsigned mode = CHECK_RAM;
>  
> -	igt_fail_on_f(intel_gen(devid) >= 11 && ncpus > 1,
> +	igt_fail_on_f(intel_gen(devid) == 11 && ncpus > 1,
>  		      "Please adjust your expectations, https://bugs.freedesktop.org/show_bug.cgi?id=110882\n");

It seems to be still exponential so how about,

if (intel_gen(devid) >= 11)
   ncpus = max(2, (ncpus-1)/2);

Would drop the medium-odd to 14 seconds, without huge dent in coverage as
as odd number of cpus would be bouncing on it?

-Mika

>  
>  	switch (huge) {
> -- 
> 2.23.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [PATCH i-g-t] i915/gem_mmap_gtt: Run forked mmap tests on tgl

[Chris Wilson]

Quoting Mika Kuoppala (2019-09-17 13:04:32)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
> 
> > Tigerlake does not seem to be suffering from the same fault as Icelake
> > did, so let the tests run as they should complete within the timeout.
> >
> > Early tgl results:
> >
> > basic-small-copy: SUCCESS (1,671s)
> > forked-basic-small-copy: SUCCESS (37,568s)
> >
> > medium-copy: SUCCESS (3,307s)
> > forked-medium-copy: SUCCESS (76,614s)
> > forked-medium-copy-XY: SUCCESS (203,251s)
> > forked-medium-copy-odd: SUCCESS (204,265s)
> >
> > Not great, but nowhere near as bad as icl,
> >        single      forked
> > glk:    2.15s       2.89s
> > icl:    2.50s     281.08s
> >
> > References: https://bugs.freedesktop.org/show_bug.cgi?id=110882
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> > Cc: Martin Peres <martin.peres@linux.intel.com>
> > ---
> >  tests/i915/gem_mmap_gtt.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c
> > index ac439cdf8..e2c6ad9a0 100644
> > --- a/tests/i915/gem_mmap_gtt.c
> > +++ b/tests/i915/gem_mmap_gtt.c
> > @@ -792,7 +792,7 @@ test_huge_copy(int fd, int huge, int tiling_a, int tiling_b, int ncpus)
> >       uint64_t huge_object_size, i;
> >       unsigned mode = CHECK_RAM;
> >  
> > -     igt_fail_on_f(intel_gen(devid) >= 11 && ncpus > 1,
> > +     igt_fail_on_f(intel_gen(devid) == 11 && ncpus > 1,
> >                     "Please adjust your expectations, https://bugs.freedesktop.org/show_bug.cgi?id=110882\n");
> 
> It seems to be still exponential so how about,
> 
> if (intel_gen(devid) >= 11)
>    ncpus = max(2, (ncpus-1)/2);
> 
> Would drop the medium-odd to 14 seconds, without huge dent in coverage as
> as odd number of cpus would be bouncing on it?

My worry is that our discovery that they introduced this late change
into Icelake is pure serendipity, and so I hesitate deviating too far
from the test setup that originally found the problem. I'd rather extend
the testing to study the correlation between ncpus and time than reduce
it :(

Thinking about the effects worth investigating here, doing a cpuset to
bind the process to a single cpu, then forking two processes should
minimally cover the uabi behaviour.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

✓ Fi.CI.BAT: success for i915/gem_mmap_gtt: Run forked mmap tests on tgl

[Patchwork]

== Series Details ==

Series: i915/gem_mmap_gtt: Run forked mmap tests on tgl
URL   : https://patchwork.freedesktop.org/series/66809/
State : success

== Summary ==

CI Bug Log - changes from IGT_5189 -> IGTPW_3470
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://patchwork.freedesktop.org/api/1.0/series/66809/revisions/1/mbox/

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

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

### IGT changes ###

#### Issues hit ####

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

  
#### Possible fixes ####

  * igt@gem_flink_basic@double-flink:
    - fi-icl-u3:          [DMESG-WARN][3] ([fdo#107724]) -> [PASS][4] +2 similar issues
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/fi-icl-u3/igt@gem_flink_basic@double-flink.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/fi-icl-u3/igt@gem_flink_basic@double-flink.html

  * igt@i915_module_load@reload-no-display:
    - {fi-icl-u4}:        [DMESG-WARN][5] ([fdo#105602]) -> [PASS][6]
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/fi-icl-u4/igt@i915_module_load@reload-no-display.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/fi-icl-u4/igt@i915_module_load@reload-no-display.html

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

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

  [fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602
  [fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107
  [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
  [fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
  [fdo#111600]: https://bugs.freedesktop.org/show_bug.cgi?id=111600


Participating hosts (54 -> 47)
------------------------------

  Additional (1): fi-tgl-u 
  Missing    (8): fi-ilk-m540 fi-hsw-4200u fi-bsw-n3050 fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus 


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

  * CI: CI-20190529 -> None
  * IGT: IGT_5189 -> IGTPW_3470

  CI-20190529: 20190529
  CI_DRM_6908: c09b47830224c06546b73417085f7c6880a3995a @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_3470: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/
  IGT_5189: c78b9959fa4050725b16d55a5e56315884a2753d @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

✗ Fi.CI.IGT: failure for i915/gem_mmap_gtt: Run forked mmap tests on tgl

[Patchwork]

== Series Details ==

Series: i915/gem_mmap_gtt: Run forked mmap tests on tgl
URL   : https://patchwork.freedesktop.org/series/66809/
State : failure

== Summary ==

CI Bug Log - changes from IGT_5189_full -> IGTPW_3470_full
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with IGTPW_3470_full absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in IGTPW_3470_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://patchwork.freedesktop.org/api/1.0/series/66809/revisions/1/mbox/

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

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

### IGT changes ###

#### Possible regressions ####

  * igt@kms_color@pipe-b-ctm-max:
    - shard-apl:          [PASS][1] -> [FAIL][2]
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-apl2/igt@kms_color@pipe-b-ctm-max.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-apl8/igt@kms_color@pipe-b-ctm-max.html
    - shard-kbl:          [PASS][3] -> [FAIL][4]
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-kbl6/igt@kms_color@pipe-b-ctm-max.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-kbl4/igt@kms_color@pipe-b-ctm-max.html

  
#### Warnings ####

  * igt@gem_mmap_gtt@forked-medium-copy:
    - shard-iclb:         [FAIL][5] ([fdo#110882]) -> [FAIL][6] +8 similar issues
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-iclb5/igt@gem_mmap_gtt@forked-medium-copy.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-iclb3/igt@gem_mmap_gtt@forked-medium-copy.html

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

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

### IGT changes ###

#### Issues hit ####

  * igt@gem_exec_schedule@independent-bsd1:
    - shard-iclb:         [PASS][7] -> [SKIP][8] ([fdo#109276]) +19 similar issues
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-iclb4/igt@gem_exec_schedule@independent-bsd1.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-iclb7/igt@gem_exec_schedule@independent-bsd1.html

  * igt@gem_exec_schedule@preempt-other-chain-bsd:
    - shard-iclb:         [PASS][9] -> [SKIP][10] ([fdo#111325]) +4 similar issues
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-iclb3/igt@gem_exec_schedule@preempt-other-chain-bsd.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-iclb2/igt@gem_exec_schedule@preempt-other-chain-bsd.html

  * igt@i915_suspend@fence-restore-tiled2untiled:
    - shard-apl:          [PASS][11] -> [DMESG-WARN][12] ([fdo#108566]) +6 similar issues
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-apl2/igt@i915_suspend@fence-restore-tiled2untiled.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-apl6/igt@i915_suspend@fence-restore-tiled2untiled.html

  * igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy:
    - shard-hsw:          [PASS][13] -> [FAIL][14] ([fdo#105767])
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-hsw5/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-hsw6/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html

  * igt@kms_flip@flip-vs-suspend:
    - shard-hsw:          [PASS][15] -> [INCOMPLETE][16] ([fdo#103540])
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-hsw5/igt@kms_flip@flip-vs-suspend.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-hsw4/igt@kms_flip@flip-vs-suspend.html

  * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-render:
    - shard-iclb:         [PASS][17] -> [FAIL][18] ([fdo#103167]) +3 similar issues
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-iclb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-render.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-iclb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-render.html

  * igt@kms_psr@psr2_primary_mmap_cpu:
    - shard-iclb:         [PASS][19] -> [SKIP][20] ([fdo#109441]) +3 similar issues
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-iclb5/igt@kms_psr@psr2_primary_mmap_cpu.html

  * igt@kms_setmode@basic:
    - shard-apl:          [PASS][21] -> [FAIL][22] ([fdo#99912])
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-apl5/igt@kms_setmode@basic.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-apl5/igt@kms_setmode@basic.html

  
#### Possible fixes ####

  * igt@gem_bad_reloc@negative-reloc-bsd2:
    - shard-iclb:         [SKIP][23] ([fdo#109276]) -> [PASS][24] +21 similar issues
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-iclb3/igt@gem_bad_reloc@negative-reloc-bsd2.html
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-iclb2/igt@gem_bad_reloc@negative-reloc-bsd2.html

  * igt@gem_ctx_shared@exec-single-timeline-bsd:
    - shard-iclb:         [SKIP][25] ([fdo#110841]) -> [PASS][26]
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-iclb1/igt@gem_ctx_shared@exec-single-timeline-bsd.html
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-iclb7/igt@gem_ctx_shared@exec-single-timeline-bsd.html

  * igt@gem_exec_schedule@deep-bsd:
    - shard-iclb:         [SKIP][27] ([fdo#111325]) -> [PASS][28] +8 similar issues
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-iclb4/igt@gem_exec_schedule@deep-bsd.html
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-iclb8/igt@gem_exec_schedule@deep-bsd.html

  * igt@gem_workarounds@suspend-resume:
    - shard-apl:          [DMESG-WARN][29] ([fdo#108566]) -> [PASS][30] +4 similar issues
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-apl5/igt@gem_workarounds@suspend-resume.html
   [30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-apl4/igt@gem_workarounds@suspend-resume.html

  * igt@kms_color@pipe-b-ctm-green-to-red:
    - shard-kbl:          [FAIL][31] ([fdo#107201]) -> [PASS][32]
   [31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-kbl7/igt@kms_color@pipe-b-ctm-green-to-red.html
   [32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-kbl6/igt@kms_color@pipe-b-ctm-green-to-red.html
    - shard-apl:          [FAIL][33] ([fdo#107201]) -> [PASS][34]
   [33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-apl4/igt@kms_color@pipe-b-ctm-green-to-red.html
   [34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-apl7/igt@kms_color@pipe-b-ctm-green-to-red.html

  * igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
    - shard-hsw:          [FAIL][35] ([fdo#105767]) -> [PASS][36]
   [35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-hsw4/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
   [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-hsw1/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html

  * igt@kms_flip@dpms-vs-vblank-race:
    - shard-glk:          [FAIL][37] ([fdo#111609]) -> [PASS][38]
   [37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-glk5/igt@kms_flip@dpms-vs-vblank-race.html
   [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-glk2/igt@kms_flip@dpms-vs-vblank-race.html

  * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-pwrite:
    - shard-iclb:         [FAIL][39] ([fdo#103167]) -> [PASS][40] +6 similar issues
   [39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-iclb8/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-pwrite.html
   [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-iclb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-pwrite.html

  * igt@kms_psr2_su@page_flip:
    - shard-iclb:         [SKIP][41] ([fdo#109642] / [fdo#111068]) -> [PASS][42]
   [41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-iclb8/igt@kms_psr2_su@page_flip.html
   [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-iclb2/igt@kms_psr2_su@page_flip.html

  * igt@kms_psr@psr2_cursor_render:
    - shard-iclb:         [SKIP][43] ([fdo#109441]) -> [PASS][44] +2 similar issues
   [43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-iclb5/igt@kms_psr@psr2_cursor_render.html
   [44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-iclb2/igt@kms_psr@psr2_cursor_render.html

  * igt@kms_setmode@basic:
    - shard-kbl:          [FAIL][45] ([fdo#99912]) -> [PASS][46]
   [45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-kbl6/igt@kms_setmode@basic.html
   [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-kbl1/igt@kms_setmode@basic.html

  
#### Warnings ####

  * igt@gem_mocs_settings@mocs-settings-bsd2:
    - shard-iclb:         [FAIL][47] ([fdo#111330]) -> [SKIP][48] ([fdo#109276]) +1 similar issue
   [47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5189/shard-iclb1/igt@gem_mocs_settings@mocs-settings-bsd2.html
   [48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/shard-iclb6/igt@gem_mocs_settings@mocs-settings-bsd2.html

  
  [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
  [fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540
  [fdo#105767]: https://bugs.freedesktop.org/show_bug.cgi?id=105767
  [fdo#107201]: https://bugs.freedesktop.org/show_bug.cgi?id=107201
  [fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
  [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
  [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
  [fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
  [fdo#110841]: https://bugs.freedesktop.org/show_bug.cgi?id=110841
  [fdo#110882]: https://bugs.freedesktop.org/show_bug.cgi?id=110882
  [fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
  [fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325
  [fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330
  [fdo#111609]: https://bugs.freedesktop.org/show_bug.cgi?id=111609
  [fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912


Participating hosts (7 -> 6)
------------------------------

  Missing    (1): shard-skl 


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

  * CI: CI-20190529 -> None
  * IGT: IGT_5189 -> IGTPW_3470

  CI-20190529: 20190529
  CI_DRM_6908: c09b47830224c06546b73417085f7c6880a3995a @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_3470: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/
  IGT_5189: c78b9959fa4050725b16d55a5e56315884a2753d @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3470/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx