* [Intel-gfx] [PATCH] drm/i915: Use the i915_device name for identifying our request fences
@ 2019-12-11 15:02 Chris Wilson
2019-12-11 15:59 ` Venkata Sandeep Dhanalakota
` (3 more replies)
0 siblings, 4 replies; 7+ messages in thread
From: Chris Wilson @ 2019-12-11 15:02 UTC (permalink / raw)
To: intel-gfx
Use the dev_name(i915) to identify the requests for debugging, so we can
tell different device timelines apart.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Venkata Sandeep Dhanalakota <venkata.s.dhanalakota@intel.com>
---
drivers/gpu/drm/i915/i915_request.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
index a6238c626a16..9646e02edea3 100644
--- a/drivers/gpu/drm/i915/i915_request.c
+++ b/drivers/gpu/drm/i915/i915_request.c
@@ -57,7 +57,7 @@ static struct i915_global_request {
static const char *i915_fence_get_driver_name(struct dma_fence *fence)
{
- return "i915";
+ return dev_name(to_request(fence)->i915->drm.dev);
}
static const char *i915_fence_get_timeline_name(struct dma_fence *fence)
--
2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915: Use the i915_device name for identifying our request fences
2019-12-11 15:02 [Intel-gfx] [PATCH] drm/i915: Use the i915_device name for identifying our request fences Chris Wilson
@ 2019-12-11 15:59 ` Venkata Sandeep Dhanalakota
2019-12-11 16:07 ` Chris Wilson
2019-12-11 21:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
` (2 subsequent siblings)
3 siblings, 1 reply; 7+ messages in thread
From: Venkata Sandeep Dhanalakota @ 2019-12-11 15:59 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
On 19/12/11 03:02, Chris Wilson wrote:
> Use the dev_name(i915) to identify the requests for debugging, so we can
> tell different device timelines apart.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Venkata Sandeep Dhanalakota <venkata.s.dhanalakota@intel.com>
> ---
> drivers/gpu/drm/i915/i915_request.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
> index a6238c626a16..9646e02edea3 100644
> --- a/drivers/gpu/drm/i915/i915_request.c
> +++ b/drivers/gpu/drm/i915/i915_request.c
> @@ -57,7 +57,7 @@ static struct i915_global_request {
>
> static const char *i915_fence_get_driver_name(struct dma_fence *fence)
> {
> - return "i915";
> + return dev_name(to_request(fence)->i915->drm.dev);
> }
>
Sure, should we also update i915_fence_get_timeline_name()
return to_request(fence)->gem_context->name ?:
i915_fence_get_driver_name(fence);
> static const char *i915_fence_get_timeline_name(struct dma_fence *fence)
> --
> 2.24.0
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915: Use the i915_device name for identifying our request fences
2019-12-11 15:59 ` Venkata Sandeep Dhanalakota
@ 2019-12-11 16:07 ` Chris Wilson
2019-12-11 16:12 ` Venkata Sandeep Dhanalakota
0 siblings, 1 reply; 7+ messages in thread
From: Chris Wilson @ 2019-12-11 16:07 UTC (permalink / raw)
To: Venkata Sandeep Dhanalakota; +Cc: intel-gfx
Quoting Venkata Sandeep Dhanalakota (2019-12-11 15:59:09)
> On 19/12/11 03:02, Chris Wilson wrote:
> > Use the dev_name(i915) to identify the requests for debugging, so we can
> > tell different device timelines apart.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Venkata Sandeep Dhanalakota <venkata.s.dhanalakota@intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_request.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
> > index a6238c626a16..9646e02edea3 100644
> > --- a/drivers/gpu/drm/i915/i915_request.c
> > +++ b/drivers/gpu/drm/i915/i915_request.c
> > @@ -57,7 +57,7 @@ static struct i915_global_request {
> >
> > static const char *i915_fence_get_driver_name(struct dma_fence *fence)
> > {
> > - return "i915";
> > + return dev_name(to_request(fence)->i915->drm.dev);
> > }
> >
> Sure, should we also update i915_fence_get_timeline_name()
> return to_request(fence)->gem_context->name ?:
> i915_fence_get_driver_name(fence);
No need really. It's either a user context or a kernel context, the less
said to userspace about internals the better. It will be presented as
00:00:02.00 i915::[i915] (or something like that)
If you would rather that "[i915]" be "[k]" or probably better yet "["
DRIVER_NAME "]"
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915: Use the i915_device name for identifying our request fences
2019-12-11 16:07 ` Chris Wilson
@ 2019-12-11 16:12 ` Venkata Sandeep Dhanalakota
0 siblings, 0 replies; 7+ messages in thread
From: Venkata Sandeep Dhanalakota @ 2019-12-11 16:12 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
On 19/12/11 04:07, Chris Wilson wrote:
> Quoting Venkata Sandeep Dhanalakota (2019-12-11 15:59:09)
> > On 19/12/11 03:02, Chris Wilson wrote:
> > > Use the dev_name(i915) to identify the requests for debugging, so we can
> > > tell different device timelines apart.
> > >
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Venkata Sandeep Dhanalakota <venkata.s.dhanalakota@intel.com>
> > > ---
> > > drivers/gpu/drm/i915/i915_request.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
> > > index a6238c626a16..9646e02edea3 100644
> > > --- a/drivers/gpu/drm/i915/i915_request.c
> > > +++ b/drivers/gpu/drm/i915/i915_request.c
> > > @@ -57,7 +57,7 @@ static struct i915_global_request {
> > >
> > > static const char *i915_fence_get_driver_name(struct dma_fence *fence)
> > > {
> > > - return "i915";
> > > + return dev_name(to_request(fence)->i915->drm.dev);
> > > }
> > >
> > Sure, should we also update i915_fence_get_timeline_name()
> > return to_request(fence)->gem_context->name ?:
> > i915_fence_get_driver_name(fence);
>
> No need really. It's either a user context or a kernel context, the less
> said to userspace about internals the better. It will be presented as
>
> 00:00:02.00 i915::[i915] (or something like that)
>
> If you would rather that "[i915]" be "[k]" or probably better yet "["
> DRIVER_NAME "]"
got it, having "[i915]" makes sense.
Reviewed-by: Venkata Sandeep Dhanalakota
<venkata.s.dhanalakota@intel.com>
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Use the i915_device name for identifying our request fences
2019-12-11 15:02 [Intel-gfx] [PATCH] drm/i915: Use the i915_device name for identifying our request fences Chris Wilson
2019-12-11 15:59 ` Venkata Sandeep Dhanalakota
@ 2019-12-11 21:18 ` Patchwork
2019-12-11 22:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2019-12-12 8:17 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
3 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2019-12-11 21:18 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915: Use the i915_device name for identifying our request fences
URL : https://patchwork.freedesktop.org/series/70761/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
856e7af5a09b drm/i915: Use the i915_device name for identifying our request fences
-:12: ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Venkata Sandeep Dhanalakota'
#12:
Reviewed-by: Venkata Sandeep Dhanalakota
total: 1 errors, 0 warnings, 0 checks, 8 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Use the i915_device name for identifying our request fences
2019-12-11 15:02 [Intel-gfx] [PATCH] drm/i915: Use the i915_device name for identifying our request fences Chris Wilson
2019-12-11 15:59 ` Venkata Sandeep Dhanalakota
2019-12-11 21:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
@ 2019-12-11 22:02 ` Patchwork
2019-12-12 8:17 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
3 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2019-12-11 22:02 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915: Use the i915_device name for identifying our request fences
URL : https://patchwork.freedesktop.org/series/70761/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7543 -> Patchwork_15694
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/index.html
Known issues
------------
Here are the changes found in Patchwork_15694 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live_blt:
- fi-byt-j1900: [PASS][1] -> [DMESG-FAIL][2] ([i915#725])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/fi-byt-j1900/igt@i915_selftest@live_blt.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/fi-byt-j1900/igt@i915_selftest@live_blt.html
* igt@i915_selftest@live_gem_contexts:
- fi-hsw-peppy: [PASS][3] -> [INCOMPLETE][4] ([i915#694])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/fi-hsw-peppy/igt@i915_selftest@live_gem_contexts.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/fi-hsw-peppy/igt@i915_selftest@live_gem_contexts.html
* igt@kms_chamelium@dp-crc-fast:
- fi-kbl-7500u: [PASS][5] -> [FAIL][6] ([fdo#109635] / [i915#217])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/fi-kbl-7500u/igt@kms_chamelium@dp-crc-fast.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/fi-kbl-7500u/igt@kms_chamelium@dp-crc-fast.html
#### Possible fixes ####
* igt@gem_exec_gttfill@basic:
- {fi-tgl-u}: [INCOMPLETE][7] ([fdo#111593]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/fi-tgl-u/igt@gem_exec_gttfill@basic.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/fi-tgl-u/igt@gem_exec_gttfill@basic.html
* igt@i915_pm_rpm@module-reload:
- fi-skl-6770hq: [FAIL][9] ([i915#178]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html
* igt@i915_selftest@live_requests:
- fi-ivb-3770: [INCOMPLETE][11] ([i915#773]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/fi-ivb-3770/igt@i915_selftest@live_requests.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/fi-ivb-3770/igt@i915_selftest@live_requests.html
- fi-hsw-4770: [INCOMPLETE][13] ([i915#773]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/fi-hsw-4770/igt@i915_selftest@live_requests.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/fi-hsw-4770/igt@i915_selftest@live_requests.html
* igt@kms_busy@basic-flip-pipe-a:
- fi-kbl-soraka: [DMESG-WARN][15] ([i915#95]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/fi-kbl-soraka/igt@kms_busy@basic-flip-pipe-a.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/fi-kbl-soraka/igt@kms_busy@basic-flip-pipe-a.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][17] ([fdo#111096] / [i915#323]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
#### Warnings ####
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-kbl-x1275: [DMESG-WARN][19] ([i915#62] / [i915#92]) -> [DMESG-WARN][20] ([i915#62] / [i915#92] / [i915#95]) +3 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/fi-kbl-x1275/igt@i915_pm_rpm@basic-pci-d3-state.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/fi-kbl-x1275/igt@i915_pm_rpm@basic-pci-d3-state.html
* igt@i915_selftest@live_gem_contexts:
- fi-byt-n2820: [DMESG-FAIL][21] ([i915#722]) -> [INCOMPLETE][22] ([i915#45])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/fi-byt-n2820/igt@i915_selftest@live_gem_contexts.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/fi-byt-n2820/igt@i915_selftest@live_gem_contexts.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-kbl-x1275: [DMESG-WARN][23] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][24] ([i915#62] / [i915#92]) +4 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/fi-kbl-x1275/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/fi-kbl-x1275/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109635]: https://bugs.freedesktop.org/show_bug.cgi?id=109635
[fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
[fdo#111593]: https://bugs.freedesktop.org/show_bug.cgi?id=111593
[i915#178]: https://gitlab.freedesktop.org/drm/intel/issues/178
[i915#217]: https://gitlab.freedesktop.org/drm/intel/issues/217
[i915#323]: https://gitlab.freedesktop.org/drm/intel/issues/323
[i915#45]: https://gitlab.freedesktop.org/drm/intel/issues/45
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#694]: https://gitlab.freedesktop.org/drm/intel/issues/694
[i915#722]: https://gitlab.freedesktop.org/drm/intel/issues/722
[i915#725]: https://gitlab.freedesktop.org/drm/intel/issues/725
[i915#773]: https://gitlab.freedesktop.org/drm/intel/issues/773
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (51 -> 47)
------------------------------
Additional (3): fi-hsw-4770r fi-tgl-guc fi-tgl-y
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7543 -> Patchwork_15694
CI-20190529: 20190529
CI_DRM_7543: 91752f80df9b582561be6bbac12ef780b12f606c @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5345: 9e0c82b6d70065db894ececf2be8de372e983cf0 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15694: 856e7af5a09b6c6d1a68a8a06b2d997062f435b2 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
856e7af5a09b drm/i915: Use the i915_device name for identifying our request fences
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Use the i915_device name for identifying our request fences
2019-12-11 15:02 [Intel-gfx] [PATCH] drm/i915: Use the i915_device name for identifying our request fences Chris Wilson
` (2 preceding siblings ...)
2019-12-11 22:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
@ 2019-12-12 8:17 ` Patchwork
3 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2019-12-12 8:17 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915: Use the i915_device name for identifying our request fences
URL : https://patchwork.freedesktop.org/series/70761/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7543_full -> Patchwork_15694_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_15694_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_15694_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_15694_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_exec_balancer@bonded-slice:
- shard-tglb: NOTRUN -> [FAIL][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb7/igt@gem_exec_balancer@bonded-slice.html
Known issues
------------
Here are the changes found in Patchwork_15694_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_busy@busy-vcs1:
- shard-iclb: [PASS][2] -> [SKIP][3] ([fdo#112080]) +1 similar issue
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-iclb2/igt@gem_busy@busy-vcs1.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-iclb8/igt@gem_busy@busy-vcs1.html
* igt@gem_ctx_persistence@rcs0-mixed-process:
- shard-glk: [PASS][4] -> [FAIL][5] ([i915#679])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-glk3/igt@gem_ctx_persistence@rcs0-mixed-process.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-glk4/igt@gem_ctx_persistence@rcs0-mixed-process.html
* igt@gem_ctx_persistence@vcs0-mixed-process:
- shard-tglb: [PASS][6] -> [FAIL][7] ([i915#679])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb7/igt@gem_ctx_persistence@vcs0-mixed-process.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb3/igt@gem_ctx_persistence@vcs0-mixed-process.html
* igt@gem_ctx_shared@q-smoketest-all:
- shard-tglb: [PASS][8] -> [INCOMPLETE][9] ([fdo#111735]) +1 similar issue
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb7/igt@gem_ctx_shared@q-smoketest-all.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb3/igt@gem_ctx_shared@q-smoketest-all.html
* igt@gem_exec_gttfill@basic:
- shard-tglb: [PASS][10] -> [INCOMPLETE][11] ([fdo#111593])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb8/igt@gem_exec_gttfill@basic.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb8/igt@gem_exec_gttfill@basic.html
* igt@gem_exec_nop@basic-parallel:
- shard-tglb: [PASS][12] -> [INCOMPLETE][13] ([i915#435])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb1/igt@gem_exec_nop@basic-parallel.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb8/igt@gem_exec_nop@basic-parallel.html
* igt@gem_exec_parallel@vecs0:
- shard-tglb: [PASS][14] -> [INCOMPLETE][15] ([fdo#111736])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb2/igt@gem_exec_parallel@vecs0.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb1/igt@gem_exec_parallel@vecs0.html
* igt@gem_exec_parse_blt@allowed-single:
- shard-skl: [PASS][16] -> [DMESG-WARN][17] ([i915#716])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl5/igt@gem_exec_parse_blt@allowed-single.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl2/igt@gem_exec_parse_blt@allowed-single.html
* igt@gem_exec_reloc@basic-cpu-wc-active:
- shard-skl: [PASS][18] -> [DMESG-WARN][19] ([i915#109]) +2 similar issues
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl1/igt@gem_exec_reloc@basic-cpu-wc-active.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl10/igt@gem_exec_reloc@basic-cpu-wc-active.html
* igt@gem_exec_schedule@preempt-queue-bsd1:
- shard-iclb: [PASS][20] -> [SKIP][21] ([fdo#109276]) +2 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-iclb1/igt@gem_exec_schedule@preempt-queue-bsd1.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-iclb6/igt@gem_exec_schedule@preempt-queue-bsd1.html
* igt@gem_exec_schedule@smoketest-all:
- shard-tglb: [PASS][22] -> [INCOMPLETE][23] ([i915#463])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb1/igt@gem_exec_schedule@smoketest-all.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb6/igt@gem_exec_schedule@smoketest-all.html
* igt@gem_exec_schedule@wide-bsd:
- shard-iclb: [PASS][24] -> [SKIP][25] ([fdo#112146]) +1 similar issue
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-iclb3/igt@gem_exec_schedule@wide-bsd.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-iclb2/igt@gem_exec_schedule@wide-bsd.html
* igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrash-inactive:
- shard-tglb: [PASS][26] -> [TIMEOUT][27] ([fdo#112126] / [i915#530])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb3/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrash-inactive.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb4/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrash-inactive.html
* igt@gem_ppgtt@flink-and-close-vma-leak:
- shard-iclb: [PASS][28] -> [FAIL][29] ([i915#644])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-iclb5/igt@gem_ppgtt@flink-and-close-vma-leak.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-iclb5/igt@gem_ppgtt@flink-and-close-vma-leak.html
* igt@gem_softpin@noreloc-s3:
- shard-skl: [PASS][30] -> [INCOMPLETE][31] ([i915#69])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl9/igt@gem_softpin@noreloc-s3.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl3/igt@gem_softpin@noreloc-s3.html
* igt@gem_sync@basic-all:
- shard-tglb: [PASS][32] -> [INCOMPLETE][33] ([i915#470] / [i915#472])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb1/igt@gem_sync@basic-all.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb6/igt@gem_sync@basic-all.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy-gup:
- shard-snb: [PASS][34] -> [DMESG-WARN][35] ([fdo#111870])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-snb7/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
* igt@gem_workarounds@suspend-resume-fd:
- shard-kbl: [PASS][36] -> [DMESG-WARN][37] ([i915#180]) +2 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-kbl7/igt@gem_workarounds@suspend-resume-fd.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-kbl7/igt@gem_workarounds@suspend-resume-fd.html
* igt@i915_suspend@forcewake:
- shard-apl: [PASS][38] -> [DMESG-WARN][39] ([i915#180]) +1 similar issue
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-apl3/igt@i915_suspend@forcewake.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-apl2/igt@i915_suspend@forcewake.html
* igt@kms_cursor_crc@pipe-b-cursor-256x256-sliding:
- shard-skl: [PASS][40] -> [FAIL][41] ([i915#54]) +1 similar issue
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl4/igt@kms_cursor_crc@pipe-b-cursor-256x256-sliding.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl8/igt@kms_cursor_crc@pipe-b-cursor-256x256-sliding.html
* igt@kms_draw_crc@draw-method-xrgb2101010-render-xtiled:
- shard-tglb: [PASS][42] -> [INCOMPLETE][43] ([i915#667])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb2/igt@kms_draw_crc@draw-method-xrgb2101010-render-xtiled.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb1/igt@kms_draw_crc@draw-method-xrgb2101010-render-xtiled.html
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-tglb: [PASS][44] -> [INCOMPLETE][45] ([i915#435] / [i915#456] / [i915#460])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb9/igt@kms_fbcon_fbt@fbc-suspend.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb4/igt@kms_fbcon_fbt@fbc-suspend.html
* igt@kms_flip@flip-vs-suspend:
- shard-tglb: [PASS][46] -> [INCOMPLETE][47] ([i915#460] / [i915#516])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb6/igt@kms_flip@flip-vs-suspend.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb8/igt@kms_flip@flip-vs-suspend.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt:
- shard-tglb: [PASS][48] -> [FAIL][49] ([i915#49]) +1 similar issue
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-wc:
- shard-tglb: [PASS][50] -> [INCOMPLETE][51] ([i915#474] / [i915#667])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb3/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-wc.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-wc.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
- shard-tglb: [PASS][52] -> [INCOMPLETE][53] ([i915#456] / [i915#460])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb9/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb2/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html
* igt@kms_plane@pixel-format-pipe-b-planes-source-clamping:
- shard-kbl: [PASS][54] -> [INCOMPLETE][55] ([fdo#103665] / [i915#435] / [i915#648] / [i915#667])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-kbl4/igt@kms_plane@pixel-format-pipe-b-planes-source-clamping.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-kbl1/igt@kms_plane@pixel-format-pipe-b-planes-source-clamping.html
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [PASS][56] -> [FAIL][57] ([fdo#108145]) +1 similar issue
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl10/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl7/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html
#### Possible fixes ####
* igt@gem_ctx_persistence@processes:
- shard-skl: [FAIL][58] ([i915#570]) -> [PASS][59]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl8/igt@gem_ctx_persistence@processes.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl1/igt@gem_ctx_persistence@processes.html
* igt@gem_ctx_persistence@vcs1-queued:
- shard-iclb: [SKIP][60] ([fdo#109276] / [fdo#112080]) -> [PASS][61]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-iclb3/igt@gem_ctx_persistence@vcs1-queued.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-iclb4/igt@gem_ctx_persistence@vcs1-queued.html
* {igt@gem_exec_schedule@pi-shared-iova-bsd2}:
- shard-iclb: [SKIP][62] ([fdo#109276]) -> [PASS][63] +4 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-iclb3/igt@gem_exec_schedule@pi-shared-iova-bsd2.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-iclb2/igt@gem_exec_schedule@pi-shared-iova-bsd2.html
* igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd:
- shard-iclb: [SKIP][64] ([fdo#112146]) -> [PASS][65] +1 similar issue
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-iclb1/igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-iclb6/igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd.html
* igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrash-inactive:
- shard-snb: [TIMEOUT][66] ([i915#530]) -> [PASS][67]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-snb1/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrash-inactive.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-snb6/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrash-inactive.html
* igt@gem_ppgtt@flink-and-close-vma-leak:
- shard-glk: [FAIL][68] ([i915#644]) -> [PASS][69]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-glk7/igt@gem_ppgtt@flink-and-close-vma-leak.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-glk3/igt@gem_ppgtt@flink-and-close-vma-leak.html
* igt@gem_sync@basic-each:
- shard-tglb: [INCOMPLETE][70] ([i915#472] / [i915#707]) -> [PASS][71]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb8/igt@gem_sync@basic-each.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb8/igt@gem_sync@basic-each.html
* igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy:
- shard-snb: [DMESG-WARN][72] ([fdo#111870]) -> [PASS][73]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-snb6/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-snb2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
* igt@gem_wait@await-vecs0:
- shard-skl: [DMESG-WARN][74] ([i915#109]) -> [PASS][75] +1 similar issue
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl4/igt@gem_wait@await-vecs0.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl3/igt@gem_wait@await-vecs0.html
* igt@i915_pm_dc@dc5-dpms:
- shard-iclb: [FAIL][76] ([i915#447]) -> [PASS][77]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-iclb3/igt@i915_pm_dc@dc5-dpms.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-iclb4/igt@i915_pm_dc@dc5-dpms.html
* igt@i915_selftest@mock_sanitycheck:
- shard-skl: [DMESG-WARN][78] ([i915#747]) -> [PASS][79]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl8/igt@i915_selftest@mock_sanitycheck.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl2/igt@i915_selftest@mock_sanitycheck.html
* igt@i915_suspend@sysfs-reader:
- shard-apl: [DMESG-WARN][80] ([i915#180]) -> [PASS][81] +3 similar issues
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-apl6/igt@i915_suspend@sysfs-reader.html
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-apl7/igt@i915_suspend@sysfs-reader.html
* igt@kms_cursor_crc@pipe-c-cursor-256x85-sliding:
- shard-skl: [FAIL][82] ([i915#54]) -> [PASS][83] +2 similar issues
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl2/igt@kms_cursor_crc@pipe-c-cursor-256x85-sliding.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl9/igt@kms_cursor_crc@pipe-c-cursor-256x85-sliding.html
* igt@kms_draw_crc@draw-method-rgb565-blt-xtiled:
- shard-tglb: [INCOMPLETE][84] ([i915#667]) -> [PASS][85]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb9/igt@kms_draw_crc@draw-method-rgb565-blt-xtiled.html
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb4/igt@kms_draw_crc@draw-method-rgb565-blt-xtiled.html
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible:
- shard-glk: [FAIL][86] ([i915#79]) -> [PASS][87]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-glk8/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-glk6/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-skl: [FAIL][88] ([i915#79]) -> [PASS][89]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl7/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl8/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-gtt:
- shard-tglb: [INCOMPLETE][90] ([i915#474] / [i915#667]) -> [PASS][91]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-gtt.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-gtt.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-kbl: [DMESG-WARN][92] ([i915#180]) -> [PASS][93] +9 similar issues
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-kbl2/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-kbl6/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
* igt@kms_plane@pixel-format-pipe-a-planes-source-clamping:
- shard-skl: [INCOMPLETE][94] ([i915#648] / [i915#667]) -> [PASS][95]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl1/igt@kms_plane@pixel-format-pipe-a-planes-source-clamping.html
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl10/igt@kms_plane@pixel-format-pipe-a-planes-source-clamping.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-d-planes:
- shard-tglb: [INCOMPLETE][96] ([i915#460]) -> [PASS][97]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb1/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-d-planes.html
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb6/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-d-planes.html
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
- shard-skl: [FAIL][98] ([fdo#108145]) -> [PASS][99]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl5/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min.html
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl5/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min.html
* igt@kms_psr@psr2_suspend:
- shard-tglb: [DMESG-WARN][100] ([i915#402]) -> [PASS][101]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb4/igt@kms_psr@psr2_suspend.html
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb2/igt@kms_psr@psr2_suspend.html
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-tglb: [INCOMPLETE][102] ([i915#456] / [i915#460]) -> [PASS][103] +1 similar issue
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb1/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb3/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
* igt@perf_pmu@busy-idle-check-all-vcs1:
- shard-iclb: [SKIP][104] ([fdo#112080]) -> [PASS][105] +1 similar issue
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-iclb3/igt@perf_pmu@busy-idle-check-all-vcs1.html
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-iclb2/igt@perf_pmu@busy-idle-check-all-vcs1.html
#### Warnings ####
* igt@i915_pm_dc@dc6-dpms:
- shard-tglb: [FAIL][106] ([i915#454]) -> [SKIP][107] ([i915#468])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-tglb1/igt@i915_pm_dc@dc6-dpms.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-tglb6/igt@i915_pm_dc@dc6-dpms.html
* igt@kms_plane@pixel-format-pipe-b-planes-source-clamping:
- shard-skl: [INCOMPLETE][108] ([fdo#112391] / [i915#648] / [i915#667]) -> [INCOMPLETE][109] ([fdo#112347] / [fdo#112391] / [i915#648] / [i915#667])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl4/igt@kms_plane@pixel-format-pipe-b-planes-source-clamping.html
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl3/igt@kms_plane@pixel-format-pipe-b-planes-source-clamping.html
* igt@runner@aborted:
- shard-skl: [FAIL][110] ([i915#69] / [k.org#204565]) -> [FAIL][111] ([i915#69])
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7543/shard-skl8/igt@runner@aborted.html
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/shard-skl2/igt@runner@aborted.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#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#111593]: https://bugs.freedesktop.org/show_bug.cgi?id=111593
[fdo#111735]: https://bugs.freedesktop.org/show_bug.cgi?id=111735
[fdo#111736]: https://bugs.freedesktop.org/show_bug.cgi?id=111736
[fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
[fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
[fdo#112126]: https://bugs.freedesktop.org/show_bug.cgi?id=112126
[fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146
[fdo#112347]: https://bugs.freedesktop.org/show_bug.cgi?id=112347
[fdo#112391]: https://bugs.freedesktop.org/show_bug.cgi?id=112391
[i915#109]: https://gitlab.freedesktop.org/drm/intel/issues/109
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#435]: https://gitlab.freedesktop.org/drm/intel/issues/435
[i915#447]: https://gitlab.freedesktop.org/drm/intel/issues/447
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456
[i915#460]: https://gitlab.freedesktop.org/drm/intel/issues/460
[i915#463]: https://gitlab.freedesktop.org/drm/intel/issues/463
[i915#468]: https://gitlab.freedesktop.org/drm/intel/issues/468
[i915#470]: https://gitlab.freedesktop.org/drm/intel/issues/470
[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#516]: https://gitlab.freedesktop.org/drm/intel/issues/516
[i915#530]: https://gitlab.freedesktop.org/drm/intel/issues/530
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#570]: https://gitlab.freedesktop.org/drm/intel/issues/570
[i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644
[i915#648]: https://gitlab.freedesktop.org/drm/intel/issues/648
[i915#667]: https://gitlab.freedesktop.org/drm/intel/issues/667
[i915#679]: https://gitlab.freedesktop.org/drm/intel/issues/679
[i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69
[i915#707]: https://gitlab.freedesktop.org/drm/intel/issues/707
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#747]: https://gitlab.freedesktop.org/drm/intel/issues/747
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[k.org#204565]: https://bugzilla.kernel.org/show_bug.cgi?id=204565
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7543 -> Patchwork_15694
CI-20190529: 20190529
CI_DRM_7543: 91752f80df9b582561be6bbac12ef780b12f606c @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5345: 9e0c82b6d70065db894ececf2be8de372e983cf0 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15694: 856e7af5a09b6c6d1a68a8a06b2d997062f435b2 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15694/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2019-12-12 8:17 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-12-11 15:02 [Intel-gfx] [PATCH] drm/i915: Use the i915_device name for identifying our request fences Chris Wilson
2019-12-11 15:59 ` Venkata Sandeep Dhanalakota
2019-12-11 16:07 ` Chris Wilson
2019-12-11 16:12 ` Venkata Sandeep Dhanalakota
2019-12-11 21:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-12-11 22:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2019-12-12 8:17 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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.