* [Intel-gfx] [PATCH] tests/gem_exec_params: test overly large batch
@ 2020-10-13 12:11 ` Matthew Auld
0 siblings, 0 replies; 9+ messages in thread
From: Matthew Auld @ 2020-10-13 12:11 UTC (permalink / raw)
To: igt-dev; +Cc: intel-gfx
See if can make something explode with too large batch (1ULL << 32),
while also making the batch_len implicit. We should also try each engine
since batch_len seems to have different interactions related to that.
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
---
tests/i915/gem_exec_params.c | 31 ++++++++++++++++++++++++++++++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/tests/i915/gem_exec_params.c b/tests/i915/gem_exec_params.c
index f8a94074..e00bbd04 100644
--- a/tests/i915/gem_exec_params.c
+++ b/tests/i915/gem_exec_params.c
@@ -273,7 +273,7 @@ static void mmapped(int i915)
gem_close(i915, buf);
}
-static uint32_t batch_create_size(int fd, uint32_t size)
+static uint32_t batch_create_size(int fd, uint64_t size)
{
const uint32_t bbe = MI_BATCH_BUFFER_END;
uint32_t handle;
@@ -317,6 +317,32 @@ static void test_invalid_batch_start(int fd)
gem_close(fd, exec.handle);
}
+static void test_larger_than_life_batch(int fd)
+{
+ uint64_t size = 1ULL << 32; /* batch_len is __u32 as per the ABI */
+ struct drm_i915_gem_exec_object2 exec = {
+ .handle = batch_create_size(fd, size),
+ };
+ struct drm_i915_gem_execbuffer2 execbuf = {
+ .buffers_ptr = to_user_pointer(&exec),
+ .buffer_count = 1,
+ };
+
+ /*
+ * batch_len seems like it can have different interaction depending on
+ * the engine and HW.
+ */
+ for_each_engine(e, fd) {
+ execbuf.flags = eb_ring(e);
+ /* Make the batch_len implicit */
+ __gem_execbuf(fd, &execbuf);
+
+ gem_sync(fd, exec.handle);
+ }
+
+ gem_close(fd, exec.handle);
+}
+
struct drm_i915_gem_execbuffer2 execbuf;
struct drm_i915_gem_exec_object2 gem_exec[1];
uint32_t batch[2] = {MI_BATCH_BUFFER_END};
@@ -586,6 +612,9 @@ igt_main
igt_subtest("invalid-batch-start-offset")
test_invalid_batch_start(fd);
+ igt_subtest("larger-than-life-batch")
+ test_larger_than_life_batch(fd);
+
#define DIRT(name) \
igt_subtest(#name "-dirt") { \
execbuf.flags = 0; \
--
2.26.2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [igt-dev] [PATCH] tests/gem_exec_params: test overly large batch
@ 2020-10-13 12:11 ` Matthew Auld
0 siblings, 0 replies; 9+ messages in thread
From: Matthew Auld @ 2020-10-13 12:11 UTC (permalink / raw)
To: igt-dev; +Cc: intel-gfx
See if can make something explode with too large batch (1ULL << 32),
while also making the batch_len implicit. We should also try each engine
since batch_len seems to have different interactions related to that.
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
---
tests/i915/gem_exec_params.c | 31 ++++++++++++++++++++++++++++++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/tests/i915/gem_exec_params.c b/tests/i915/gem_exec_params.c
index f8a94074..e00bbd04 100644
--- a/tests/i915/gem_exec_params.c
+++ b/tests/i915/gem_exec_params.c
@@ -273,7 +273,7 @@ static void mmapped(int i915)
gem_close(i915, buf);
}
-static uint32_t batch_create_size(int fd, uint32_t size)
+static uint32_t batch_create_size(int fd, uint64_t size)
{
const uint32_t bbe = MI_BATCH_BUFFER_END;
uint32_t handle;
@@ -317,6 +317,32 @@ static void test_invalid_batch_start(int fd)
gem_close(fd, exec.handle);
}
+static void test_larger_than_life_batch(int fd)
+{
+ uint64_t size = 1ULL << 32; /* batch_len is __u32 as per the ABI */
+ struct drm_i915_gem_exec_object2 exec = {
+ .handle = batch_create_size(fd, size),
+ };
+ struct drm_i915_gem_execbuffer2 execbuf = {
+ .buffers_ptr = to_user_pointer(&exec),
+ .buffer_count = 1,
+ };
+
+ /*
+ * batch_len seems like it can have different interaction depending on
+ * the engine and HW.
+ */
+ for_each_engine(e, fd) {
+ execbuf.flags = eb_ring(e);
+ /* Make the batch_len implicit */
+ __gem_execbuf(fd, &execbuf);
+
+ gem_sync(fd, exec.handle);
+ }
+
+ gem_close(fd, exec.handle);
+}
+
struct drm_i915_gem_execbuffer2 execbuf;
struct drm_i915_gem_exec_object2 gem_exec[1];
uint32_t batch[2] = {MI_BATCH_BUFFER_END};
@@ -586,6 +612,9 @@ igt_main
igt_subtest("invalid-batch-start-offset")
test_invalid_batch_start(fd);
+ igt_subtest("larger-than-life-batch")
+ test_larger_than_life_batch(fd);
+
#define DIRT(name) \
igt_subtest(#name "-dirt") { \
execbuf.flags = 0; \
--
2.26.2
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [Intel-gfx] [igt-dev] [PATCH] tests/gem_exec_params: test overly large batch
2020-10-13 12:11 ` [igt-dev] " Matthew Auld
@ 2020-10-13 12:21 ` Chris Wilson
-1 siblings, 0 replies; 9+ messages in thread
From: Chris Wilson @ 2020-10-13 12:21 UTC (permalink / raw)
To: Matthew Auld, igt-dev; +Cc: intel-gfx
Quoting Matthew Auld (2020-10-13 13:11:39)
> See if can make something explode with too large batch (1ULL << 32),
> while also making the batch_len implicit. We should also try each engine
> since batch_len seems to have different interactions related to that.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> ---
> tests/i915/gem_exec_params.c | 31 ++++++++++++++++++++++++++++++-
> 1 file changed, 30 insertions(+), 1 deletion(-)
>
> diff --git a/tests/i915/gem_exec_params.c b/tests/i915/gem_exec_params.c
> index f8a94074..e00bbd04 100644
> --- a/tests/i915/gem_exec_params.c
> +++ b/tests/i915/gem_exec_params.c
> @@ -273,7 +273,7 @@ static void mmapped(int i915)
> gem_close(i915, buf);
> }
>
> -static uint32_t batch_create_size(int fd, uint32_t size)
> +static uint32_t batch_create_size(int fd, uint64_t size)
> {
> const uint32_t bbe = MI_BATCH_BUFFER_END;
> uint32_t handle;
> @@ -317,6 +317,32 @@ static void test_invalid_batch_start(int fd)
> gem_close(fd, exec.handle);
> }
>
> +static void test_larger_than_life_batch(int fd)
> +{
> + uint64_t size = 1ULL << 32; /* batch_len is __u32 as per the ABI */
> + struct drm_i915_gem_exec_object2 exec = {
> + .handle = batch_create_size(fd, size),
> + };
> + struct drm_i915_gem_execbuffer2 execbuf = {
> + .buffers_ptr = to_user_pointer(&exec),
> + .buffer_count = 1,
> + };
Needs intel_require_memory(2, size, CHECK_RAM)
> +
> + /*
> + * batch_len seems like it can have different interaction depending on
> + * the engine and HW.
> + */
> + for_each_engine(e, fd) {
> + execbuf.flags = eb_ring(e);
> + /* Make the batch_len implicit */
> + __gem_execbuf(fd, &execbuf);
Expect success.
> +
> + gem_sync(fd, exec.handle);
?
If you just want to be sure the system is idle, put it after the loop.
Otherwise it doesn't/shouldn't affect the interpretation of the params
(if paranoid, do both, though to ensure it is active at the time, you
would need a spinner).
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [igt-dev] [PATCH] tests/gem_exec_params: test overly large batch
@ 2020-10-13 12:21 ` Chris Wilson
0 siblings, 0 replies; 9+ messages in thread
From: Chris Wilson @ 2020-10-13 12:21 UTC (permalink / raw)
To: Matthew Auld, igt-dev; +Cc: intel-gfx
Quoting Matthew Auld (2020-10-13 13:11:39)
> See if can make something explode with too large batch (1ULL << 32),
> while also making the batch_len implicit. We should also try each engine
> since batch_len seems to have different interactions related to that.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> ---
> tests/i915/gem_exec_params.c | 31 ++++++++++++++++++++++++++++++-
> 1 file changed, 30 insertions(+), 1 deletion(-)
>
> diff --git a/tests/i915/gem_exec_params.c b/tests/i915/gem_exec_params.c
> index f8a94074..e00bbd04 100644
> --- a/tests/i915/gem_exec_params.c
> +++ b/tests/i915/gem_exec_params.c
> @@ -273,7 +273,7 @@ static void mmapped(int i915)
> gem_close(i915, buf);
> }
>
> -static uint32_t batch_create_size(int fd, uint32_t size)
> +static uint32_t batch_create_size(int fd, uint64_t size)
> {
> const uint32_t bbe = MI_BATCH_BUFFER_END;
> uint32_t handle;
> @@ -317,6 +317,32 @@ static void test_invalid_batch_start(int fd)
> gem_close(fd, exec.handle);
> }
>
> +static void test_larger_than_life_batch(int fd)
> +{
> + uint64_t size = 1ULL << 32; /* batch_len is __u32 as per the ABI */
> + struct drm_i915_gem_exec_object2 exec = {
> + .handle = batch_create_size(fd, size),
> + };
> + struct drm_i915_gem_execbuffer2 execbuf = {
> + .buffers_ptr = to_user_pointer(&exec),
> + .buffer_count = 1,
> + };
Needs intel_require_memory(2, size, CHECK_RAM)
> +
> + /*
> + * batch_len seems like it can have different interaction depending on
> + * the engine and HW.
> + */
> + for_each_engine(e, fd) {
> + execbuf.flags = eb_ring(e);
> + /* Make the batch_len implicit */
> + __gem_execbuf(fd, &execbuf);
Expect success.
> +
> + gem_sync(fd, exec.handle);
?
If you just want to be sure the system is idle, put it after the loop.
Otherwise it doesn't/shouldn't affect the interpretation of the params
(if paranoid, do both, though to ensure it is active at the time, you
would need a spinner).
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for tests/gem_exec_params: test overly large batch
2020-10-13 12:11 ` [igt-dev] " Matthew Auld
(?)
(?)
@ 2020-10-13 12:53 ` Patchwork
-1 siblings, 0 replies; 9+ messages in thread
From: Patchwork @ 2020-10-13 12:53 UTC (permalink / raw)
To: Matthew Auld; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 6632 bytes --]
== Series Details ==
Series: tests/gem_exec_params: test overly large batch
URL : https://patchwork.freedesktop.org/series/82625/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9135 -> IGTPW_5063
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/index.html
Known issues
------------
Here are the changes found in IGTPW_5063 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ringfill@basic-all:
- fi-tgl-y: [PASS][1] -> [DMESG-WARN][2] ([i915#402]) +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-tgl-y/igt@gem_ringfill@basic-all.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-tgl-y/igt@gem_ringfill@basic-all.html
* igt@i915_module_load@reload:
- fi-tgl-u2: [PASS][3] -> [DMESG-WARN][4] ([i915#1982] / [k.org#205379])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-tgl-u2/igt@i915_module_load@reload.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-tgl-u2/igt@i915_module_load@reload.html
- fi-tgl-y: [PASS][5] -> [DMESG-WARN][6] ([i915#1982] / [k.org#205379])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-tgl-y/igt@i915_module_load@reload.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-tgl-y/igt@i915_module_load@reload.html
* igt@i915_selftest@live@coherency:
- fi-gdg-551: [PASS][7] -> [DMESG-FAIL][8] ([i915#1748])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-gdg-551/igt@i915_selftest@live@coherency.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-gdg-551/igt@i915_selftest@live@coherency.html
* igt@kms_flip@basic-flip-vs-dpms@d-edp1:
- fi-tgl-y: [PASS][9] -> [DMESG-WARN][10] ([i915#1982])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-tgl-y/igt@kms_flip@basic-flip-vs-dpms@d-edp1.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-tgl-y/igt@kms_flip@basic-flip-vs-dpms@d-edp1.html
#### Possible fixes ####
* igt@gem_flink_basic@bad-flink:
- fi-tgl-y: [DMESG-WARN][11] ([i915#402]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-tgl-y/igt@gem_flink_basic@bad-flink.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-tgl-y/igt@gem_flink_basic@bad-flink.html
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-byt-j1900: [DMESG-WARN][13] ([i915#1982]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-byt-j1900/igt@i915_pm_rpm@basic-pci-d3-state.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-byt-j1900/igt@i915_pm_rpm@basic-pci-d3-state.html
- fi-bsw-n3050: [DMESG-WARN][15] ([i915#1982]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-bsw-n3050/igt@i915_pm_rpm@basic-pci-d3-state.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-bsw-n3050/igt@i915_pm_rpm@basic-pci-d3-state.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-icl-u2: [DMESG-WARN][17] ([i915#1982]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-icl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-icl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
- fi-bsw-kefka: [DMESG-WARN][19] ([i915#1982]) -> [PASS][20]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
- fi-apl-guc: [DMESG-WARN][21] ([i915#1635] / [i915#1982]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-apl-guc/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-apl-guc/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
* igt@kms_pipe_crc_basic@read-crc-pipe-c:
- {fi-tgl-dsi}: [DMESG-WARN][23] ([i915#1982]) -> [PASS][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-tgl-dsi/igt@kms_pipe_crc_basic@read-crc-pipe-c.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-tgl-dsi/igt@kms_pipe_crc_basic@read-crc-pipe-c.html
#### Warnings ####
* igt@gem_exec_suspend@basic-s3:
- fi-tgl-y: [DMESG-WARN][25] ([i915#2411]) -> [DMESG-WARN][26] ([i915#2411] / [i915#402])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-tgl-y/igt@gem_exec_suspend@basic-s3.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-tgl-y/igt@gem_exec_suspend@basic-s3.html
* igt@i915_pm_rpm@module-reload:
- fi-tgl-y: [DMESG-WARN][27] ([i915#2411]) -> [DMESG-WARN][28] ([i915#1982] / [i915#2411])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/fi-tgl-y/igt@i915_pm_rpm@module-reload.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/fi-tgl-y/igt@i915_pm_rpm@module-reload.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#1748]: https://gitlab.freedesktop.org/drm/intel/issues/1748
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[k.org#205379]: https://bugzilla.kernel.org/show_bug.cgi?id=205379
Participating hosts (47 -> 41)
------------------------------
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5813 -> IGTPW_5063
CI-20190529: 20190529
CI_DRM_9135: eb70ad33fcc91d3464b07679391fb477927ad4c7 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5063: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/index.html
IGT_5813: d4e6dd955a1dad02271aa41c9389f5097ee17765 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Testlist changes ==
+igt@gem_exec_params@larger-than-life-batch
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/index.html
[-- Attachment #1.2: Type: text/html, Size: 8556 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Intel-gfx] ✗ Fi.CI.BUILD: failure for tests/gem_exec_params: test overly large batch
2020-10-13 12:11 ` [igt-dev] " Matthew Auld
` (2 preceding siblings ...)
(?)
@ 2020-10-13 13:54 ` Patchwork
-1 siblings, 0 replies; 9+ messages in thread
From: Patchwork @ 2020-10-13 13:54 UTC (permalink / raw)
To: Matthew Auld; +Cc: intel-gfx
== Series Details ==
Series: tests/gem_exec_params: test overly large batch
URL : https://patchwork.freedesktop.org/series/82626/
State : failure
== Summary ==
Applying: tests/gem_exec_params: test overly large batch
error: sha1 information is lacking or useless (tests/i915/gem_exec_params.c).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 tests/gem_exec_params: test overly large batch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Intel-gfx] [igt-dev] [PATCH] tests/gem_exec_params: test overly large batch
2020-10-13 12:21 ` Chris Wilson
@ 2020-10-13 14:40 ` Chris Wilson
-1 siblings, 0 replies; 9+ messages in thread
From: Chris Wilson @ 2020-10-13 14:40 UTC (permalink / raw)
To: Matthew Auld, igt-dev; +Cc: intel-gfx
Quoting Chris Wilson (2020-10-13 13:21:55)
> > +
> > + /*
> > + * batch_len seems like it can have different interaction depending on
> > + * the engine and HW.
> > + */
> > + for_each_engine(e, fd) {
> > + execbuf.flags = eb_ring(e);
> > + /* Make the batch_len implicit */
> > + __gem_execbuf(fd, &execbuf);
>
> Expect success.
Except for when batch > GTT size. igt_require(gem_gtt_size() > 4G) ?
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [igt-dev] [PATCH] tests/gem_exec_params: test overly large batch
@ 2020-10-13 14:40 ` Chris Wilson
0 siblings, 0 replies; 9+ messages in thread
From: Chris Wilson @ 2020-10-13 14:40 UTC (permalink / raw)
To: Matthew Auld, igt-dev; +Cc: intel-gfx
Quoting Chris Wilson (2020-10-13 13:21:55)
> > +
> > + /*
> > + * batch_len seems like it can have different interaction depending on
> > + * the engine and HW.
> > + */
> > + for_each_engine(e, fd) {
> > + execbuf.flags = eb_ring(e);
> > + /* Make the batch_len implicit */
> > + __gem_execbuf(fd, &execbuf);
>
> Expect success.
Except for when batch > GTT size. igt_require(gem_gtt_size() > 4G) ?
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
* [igt-dev] ✗ Fi.CI.IGT: failure for tests/gem_exec_params: test overly large batch
2020-10-13 12:11 ` [igt-dev] " Matthew Auld
` (3 preceding siblings ...)
(?)
@ 2020-10-14 6:58 ` Patchwork
-1 siblings, 0 replies; 9+ messages in thread
From: Patchwork @ 2020-10-14 6:58 UTC (permalink / raw)
To: Matthew Auld; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 21831 bytes --]
== Series Details ==
Series: tests/gem_exec_params: test overly large batch
URL : https://patchwork.freedesktop.org/series/82625/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9135_full -> IGTPW_5063_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_5063_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_5063_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_5063/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_5063_full:
### IGT changes ###
#### Possible regressions ####
* {igt@gem_exec_params@larger-than-life-batch} (NEW):
- shard-kbl: NOTRUN -> [INCOMPLETE][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-kbl1/igt@gem_exec_params@larger-than-life-batch.html
- shard-glk: NOTRUN -> [INCOMPLETE][2]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-glk5/igt@gem_exec_params@larger-than-life-batch.html
* igt@gem_partial_pwrite_pread@write-uncached:
- shard-hsw: [PASS][3] -> [INCOMPLETE][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-hsw2/igt@gem_partial_pwrite_pread@write-uncached.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-hsw2/igt@gem_partial_pwrite_pread@write-uncached.html
* igt@kms_flip@plain-flip-ts-check@a-dp1:
- shard-kbl: [PASS][5] -> [INCOMPLETE][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-kbl6/igt@kms_flip@plain-flip-ts-check@a-dp1.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-kbl7/igt@kms_flip@plain-flip-ts-check@a-dp1.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-render:
- shard-tglb: [PASS][7] -> [FAIL][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-tglb5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-render.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-tglb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-render.html
#### Warnings ####
* igt@kms_frontbuffer_tracking@fbcpsr-tiling-y:
- shard-tglb: [DMESG-FAIL][9] ([i915#1982]) -> [FAIL][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-tglb8/igt@kms_frontbuffer_tracking@fbcpsr-tiling-y.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-tglb1/igt@kms_frontbuffer_tracking@fbcpsr-tiling-y.html
New tests
---------
New tests have been introduced between CI_DRM_9135_full and IGTPW_5063_full:
### New IGT tests (1) ###
* igt@gem_exec_params@larger-than-life-batch:
- Statuses : 3 incomplete(s) 3 pass(s)
- Exec time: [0.0, 3.55] s
Known issues
------------
Here are the changes found in IGTPW_5063_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@feature_discovery@psr2:
- shard-iclb: [PASS][11] -> [SKIP][12] ([i915#658])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-iclb2/igt@feature_discovery@psr2.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-iclb4/igt@feature_discovery@psr2.html
* igt@gem_eio@in-flight-suspend:
- shard-kbl: [PASS][13] -> [INCOMPLETE][14] ([i915#155])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-kbl2/igt@gem_eio@in-flight-suspend.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-kbl1/igt@gem_eio@in-flight-suspend.html
* igt@gem_exec_reloc@basic-many-active@vecs0:
- shard-glk: [PASS][15] -> [FAIL][16] ([i915#2389]) +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-glk1/igt@gem_exec_reloc@basic-many-active@vecs0.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-glk9/igt@gem_exec_reloc@basic-many-active@vecs0.html
* igt@gem_exec_whisper@basic-contexts-forked-all:
- shard-glk: [PASS][17] -> [DMESG-WARN][18] ([i915#118] / [i915#95])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-glk7/igt@gem_exec_whisper@basic-contexts-forked-all.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-glk5/igt@gem_exec_whisper@basic-contexts-forked-all.html
* igt@gem_mmap_wc@copy:
- shard-iclb: [PASS][19] -> [DMESG-WARN][20] ([i915#1982])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-iclb2/igt@gem_mmap_wc@copy.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-iclb2/igt@gem_mmap_wc@copy.html
* igt@kms_big_fb@x-tiled-8bpp-rotate-180:
- shard-apl: [PASS][21] -> [DMESG-WARN][22] ([i915#1635] / [i915#1982])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-apl3/igt@kms_big_fb@x-tiled-8bpp-rotate-180.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-apl6/igt@kms_big_fb@x-tiled-8bpp-rotate-180.html
* igt@kms_flip@flip-vs-expired-vblank@b-dp1:
- shard-apl: [PASS][23] -> [FAIL][24] ([i915#1635] / [i915#79])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-apl1/igt@kms_flip@flip-vs-expired-vblank@b-dp1.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-apl2/igt@kms_flip@flip-vs-expired-vblank@b-dp1.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-render:
- shard-kbl: [PASS][25] -> [DMESG-WARN][26] ([i915#1982]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-render.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-kbl4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-render.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-fullscreen:
- shard-glk: [PASS][27] -> [FAIL][28] ([i915#49])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-glk6/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-fullscreen.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-glk4/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-fullscreen.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-cpu:
- shard-tglb: [PASS][29] -> [DMESG-WARN][30] ([i915#1982]) +3 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-tglb6/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-cpu.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-tglb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-cpu.html
* igt@kms_prime@basic-crc@first-to-second:
- shard-iclb: [PASS][31] -> [SKIP][32] ([i915#1836])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-iclb7/igt@kms_prime@basic-crc@first-to-second.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-iclb2/igt@kms_prime@basic-crc@first-to-second.html
- shard-snb: [PASS][33] -> [SKIP][34] ([fdo#109271])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-snb6/igt@kms_prime@basic-crc@first-to-second.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-snb5/igt@kms_prime@basic-crc@first-to-second.html
- shard-hsw: [PASS][35] -> [SKIP][36] ([fdo#109271])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-hsw2/igt@kms_prime@basic-crc@first-to-second.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-hsw2/igt@kms_prime@basic-crc@first-to-second.html
- shard-kbl: [PASS][37] -> [SKIP][38] ([fdo#109271])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-kbl1/igt@kms_prime@basic-crc@first-to-second.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-kbl1/igt@kms_prime@basic-crc@first-to-second.html
- shard-apl: [PASS][39] -> [SKIP][40] ([fdo#109271] / [i915#1635])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-apl1/igt@kms_prime@basic-crc@first-to-second.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-apl3/igt@kms_prime@basic-crc@first-to-second.html
- shard-tglb: [PASS][41] -> [SKIP][42] ([i915#1836])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-tglb6/igt@kms_prime@basic-crc@first-to-second.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-tglb5/igt@kms_prime@basic-crc@first-to-second.html
- shard-glk: [PASS][43] -> [SKIP][44] ([fdo#109271])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-glk7/igt@kms_prime@basic-crc@first-to-second.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-glk6/igt@kms_prime@basic-crc@first-to-second.html
* igt@kms_psr@psr2_sprite_plane_onoff:
- shard-iclb: [PASS][45] -> [SKIP][46] ([fdo#109441]) +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-iclb2/igt@kms_psr@psr2_sprite_plane_onoff.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-iclb5/igt@kms_psr@psr2_sprite_plane_onoff.html
#### Possible fixes ####
* {igt@gem_exec_capture@pi@bcs0}:
- shard-glk: [INCOMPLETE][47] -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-glk1/igt@gem_exec_capture@pi@bcs0.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-glk6/igt@gem_exec_capture@pi@bcs0.html
* igt@gem_exec_reloc@basic-many-active@rcs0:
- shard-glk: [FAIL][49] ([i915#2389]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-glk1/igt@gem_exec_reloc@basic-many-active@rcs0.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-glk9/igt@gem_exec_reloc@basic-many-active@rcs0.html
* {igt@kms_async_flips@async-flip-with-page-flip-events}:
- shard-kbl: [FAIL][51] ([i915#2521]) -> [PASS][52] +1 similar issue
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-kbl2/igt@kms_async_flips@async-flip-with-page-flip-events.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-kbl4/igt@kms_async_flips@async-flip-with-page-flip-events.html
- shard-iclb: [FAIL][53] ([i915#2521]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-iclb6/igt@kms_async_flips@async-flip-with-page-flip-events.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-iclb4/igt@kms_async_flips@async-flip-with-page-flip-events.html
* igt@kms_cursor_legacy@basic-flip-before-cursor-legacy:
- shard-tglb: [DMESG-WARN][55] ([i915#1982]) -> [PASS][56] +1 similar issue
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-tglb1/igt@kms_cursor_legacy@basic-flip-before-cursor-legacy.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-tglb1/igt@kms_cursor_legacy@basic-flip-before-cursor-legacy.html
* igt@kms_cursor_legacy@pipe-b-torture-move:
- shard-tglb: [DMESG-WARN][57] ([i915#128]) -> [PASS][58] +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-tglb7/igt@kms_cursor_legacy@pipe-b-torture-move.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-tglb1/igt@kms_cursor_legacy@pipe-b-torture-move.html
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-glk: [DMESG-FAIL][59] ([i915#118] / [i915#95]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-glk3/igt@kms_fbcon_fbt@fbc-suspend.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-glk6/igt@kms_fbcon_fbt@fbc-suspend.html
* igt@kms_flip@basic-flip-vs-wf_vblank@a-dp1:
- shard-kbl: [DMESG-WARN][61] ([i915#1982]) -> [PASS][62] +1 similar issue
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-kbl4/igt@kms_flip@basic-flip-vs-wf_vblank@a-dp1.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-kbl2/igt@kms_flip@basic-flip-vs-wf_vblank@a-dp1.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-dp1:
- shard-apl: [FAIL][63] ([i915#1635] / [i915#79]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-apl8/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-dp1.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-apl7/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-dp1.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt:
- shard-tglb: [FAIL][65] -> [PASS][66] +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-tglb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt.html
* igt@kms_frontbuffer_tracking@psr-shrfb-scaledprimary:
- shard-iclb: [DMESG-WARN][67] ([i915#1982]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-iclb8/igt@kms_frontbuffer_tracking@psr-shrfb-scaledprimary.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-iclb8/igt@kms_frontbuffer_tracking@psr-shrfb-scaledprimary.html
* igt@kms_plane@plane-position-covered-pipe-c-planes:
- shard-apl: [FAIL][69] ([i915#1635] / [i915#247]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-apl2/igt@kms_plane@plane-position-covered-pipe-c-planes.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-apl1/igt@kms_plane@plane-position-covered-pipe-c-planes.html
- shard-kbl: [FAIL][71] ([i915#247]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-kbl6/igt@kms_plane@plane-position-covered-pipe-c-planes.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-kbl7/igt@kms_plane@plane-position-covered-pipe-c-planes.html
* igt@kms_prime@basic-crc@second-to-first:
- shard-apl: [SKIP][73] ([fdo#109271] / [i915#1635]) -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-apl1/igt@kms_prime@basic-crc@second-to-first.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-apl3/igt@kms_prime@basic-crc@second-to-first.html
- shard-kbl: [SKIP][75] ([fdo#109271]) -> [PASS][76]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-kbl1/igt@kms_prime@basic-crc@second-to-first.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-kbl1/igt@kms_prime@basic-crc@second-to-first.html
- shard-hsw: [SKIP][77] ([fdo#109271]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-hsw2/igt@kms_prime@basic-crc@second-to-first.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-hsw2/igt@kms_prime@basic-crc@second-to-first.html
- shard-iclb: [SKIP][79] ([i915#1836]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-iclb7/igt@kms_prime@basic-crc@second-to-first.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-iclb2/igt@kms_prime@basic-crc@second-to-first.html
- shard-snb: [SKIP][81] ([fdo#109271]) -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-snb6/igt@kms_prime@basic-crc@second-to-first.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-snb5/igt@kms_prime@basic-crc@second-to-first.html
- shard-tglb: [SKIP][83] ([i915#1836]) -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-tglb6/igt@kms_prime@basic-crc@second-to-first.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-tglb5/igt@kms_prime@basic-crc@second-to-first.html
- shard-glk: [SKIP][85] ([fdo#109271]) -> [PASS][86]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-glk7/igt@kms_prime@basic-crc@second-to-first.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-glk6/igt@kms_prime@basic-crc@second-to-first.html
* igt@kms_psr@psr2_primary_mmap_gtt:
- shard-iclb: [SKIP][87] ([fdo#109441]) -> [PASS][88]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-iclb3/igt@kms_psr@psr2_primary_mmap_gtt.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-iclb2/igt@kms_psr@psr2_primary_mmap_gtt.html
* igt@sysfs_heartbeat_interval@mixed@vcs1:
- shard-kbl: [INCOMPLETE][89] ([i915#1731]) -> [PASS][90]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-kbl4/igt@sysfs_heartbeat_interval@mixed@vcs1.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-kbl2/igt@sysfs_heartbeat_interval@mixed@vcs1.html
#### Warnings ####
* igt@kms_content_protection@atomic:
- shard-apl: [TIMEOUT][91] ([i915#1319] / [i915#1635]) -> [FAIL][92] ([fdo#110321] / [fdo#110336] / [i915#1635])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-apl2/igt@kms_content_protection@atomic.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-apl1/igt@kms_content_protection@atomic.html
* igt@kms_content_protection@atomic-dpms:
- shard-apl: [FAIL][93] ([fdo#110321] / [fdo#110336] / [i915#1635]) -> [TIMEOUT][94] ([i915#1319] / [i915#1635])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-apl3/igt@kms_content_protection@atomic-dpms.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-apl4/igt@kms_content_protection@atomic-dpms.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-shrfb-msflip-blt:
- shard-tglb: [FAIL][95] -> [DMESG-FAIL][96] ([i915#1982])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-tglb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-shrfb-msflip-blt.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-tglb8/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-shrfb-msflip-blt.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-7efc:
- shard-apl: [FAIL][97] ([fdo#108145] / [i915#1635] / [i915#265]) -> [DMESG-FAIL][98] ([fdo#108145] / [i915#1635] / [i915#1982])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-apl3/igt@kms_plane_alpha_blend@pipe-a-alpha-7efc.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-apl1/igt@kms_plane_alpha_blend@pipe-a-alpha-7efc.html
* igt@runner@aborted:
- shard-glk: [FAIL][99] ([i915#2439] / [k.org#202321]) -> [FAIL][100] ([i915#1611] / [i915#2439] / [k.org#202321])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9135/shard-glk1/igt@runner@aborted.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/shard-glk5/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#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#128]: https://gitlab.freedesktop.org/drm/intel/issues/128
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1611]: https://gitlab.freedesktop.org/drm/intel/issues/1611
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#1731]: https://gitlab.freedesktop.org/drm/intel/issues/1731
[i915#1836]: https://gitlab.freedesktop.org/drm/intel/issues/1836
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2283]: https://gitlab.freedesktop.org/drm/intel/issues/2283
[i915#2389]: https://gitlab.freedesktop.org/drm/intel/issues/2389
[i915#2439]: https://gitlab.freedesktop.org/drm/intel/issues/2439
[i915#247]: https://gitlab.freedesktop.org/drm/intel/issues/247
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2542]: https://gitlab.freedesktop.org/drm/intel/issues/2542
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[k.org#202321]: https://bugzilla.kernel.org/show_bug.cgi?id=202321
Participating hosts (11 -> 8)
------------------------------
Missing (3): pig-skl-6260u pig-glk-j5005 pig-icl-1065g7
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5813 -> IGTPW_5063
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_9135: eb70ad33fcc91d3464b07679391fb477927ad4c7 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5063: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5063/index.html
IGT_5813: d4e6dd955a1dad02271aa41c9389f5097ee17765 @ 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_5063/index.html
[-- Attachment #1.2: Type: text/html, Size: 26442 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2020-10-14 6:58 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-13 12:11 [Intel-gfx] [PATCH] tests/gem_exec_params: test overly large batch Matthew Auld
2020-10-13 12:11 ` [igt-dev] " Matthew Auld
2020-10-13 12:21 ` [Intel-gfx] " Chris Wilson
2020-10-13 12:21 ` Chris Wilson
2020-10-13 14:40 ` [Intel-gfx] " Chris Wilson
2020-10-13 14:40 ` Chris Wilson
2020-10-13 12:53 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-10-13 13:54 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure " Patchwork
2020-10-14 6:58 ` [igt-dev] ✗ Fi.CI.IGT: " 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.