gem_exec_reloc & gem_shrink: Added gem_require_mappable_ggtt to check mappable aperture
PATCH 1/1 gem_exec_reloc & gem_shrink: Added gem_require_mappable_ggtt to check mappable aperture
Added gem_require_mappable_ggtt to check mappable aperture. This is to avoid any test crash that might happen if mappable aperture is not avilable.
--- tests/i915/gem_exec_reloc.c | 3 +++ tests/i915/gem_shrink.c | 2 ++ 2 files changed, 5 insertions(+)
tests/i915/gem_exec_reloc.c +3 -0
@@ -1217,6 +1217,7 @@ igt_mainif (!(f->flags &NORELOC )) {igt_subtest_f ("%srange%s" , f->basic ? "basic-" : "", f->name) { +gem_require_mappable_ggtt (fd); igt_while_interruptible(f->flags & INTERRUPTIBLE)basic_range (fd, f->flags); }
@@ -1264,6 +1265,7 @@ igt_main } igt_subtest_with_dynamic("basic-spin") { +__for_each_physical_engine (fd, e) { igt_dynamic_f("%s", e->name)active_spin (fd, e->flags);
@@ -1278,6 +1280,7 @@ igt_main } igt_subtest_with_dynamic("basic-many-active") { +gem_require_mappable_ggtt (fd);__for_each_physical_engine (fd, e) { igt_dynamic_f("%s", e->name)many_active (fd, e->flags);
tests/i915/gem_shrink.c +2 -0
@@ -432,6 +432,8 @@ igt_main fd =drm_open_driver (DRIVER_INTEL );igt_require_gem (fd); +gem_require_mappable_ggtt (fd); +/* * Spawn enough processes to use all memory, but each only * uses half the available mappable aperture ~128MiB.
Signature · 6 lines
2.25.1 _______________________________________________ igt-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 17 lines · Arjun Melkaveri
Added
gem_require_mappable_ggttto check mappable aperture. This is to avoid any test crash that might happen if mappable aperture is not avilable.Cc Chris Wilson <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Arjun Melkaveri <[email protected]>--- tests/i915/gem_exec_reloc.c | 3 +++ tests/i915/gem_shrink.c | 2 ++ 2 files changed, 5 insertions(+)tests/i915/gem_exec_reloc.c +0
-0
tests/i915/gem_exec_reloc.c igt_main · line 1220
Quoted 4 lines
tests/i915/gem_exec_reloc.c +1
-0@@ -1217,6 +1217,7 @@ igt_mainif (!(f->flags &NORELOC )) {igt_subtest_f ("%srange%s" , f->basic ? "basic-" : "", f->name) { +gem_require_mappable_ggtt (fd);
From the code and commit message it is not immediately obvious to me why basic_range needs the aperture, Chris? Answer to that will drive the solution.
tests/i915/gem_exec_reloc.c igt_main · line 1268
Quoted 8 lines
tests/i915/gem_exec_reloc.c +1
-0igt_while_interruptible(f->flags & INTERRUPTIBLE)basic_range (fd, f->flags); }@@ -1264,6 +1265,7 @@ igt_main } igt_subtest_with_dynamic("basic-spin") { +
!
tests/i915/gem_exec_reloc.c igt_main · line 1286
Quoted 11 lines
tests/i915/gem_exec_reloc.c +1
-0__for_each_physical_engine (fd, e) { igt_dynamic_f("%s", e->name)active_spin (fd, e->flags);@@ -1278,6 +1280,7 @@ igt_main } igt_subtest_with_dynamic("basic-many-active") { +gem_require_mappable_ggtt (fd);__for_each_physical_engine (fd, e) { igt_dynamic_f("%s", e->name)many_active (fd, e->flags);
Same for many_active - maybe tests should use ggtt size and not aperture, with some tweaks to make size/runtime sane?
Quoted 6 lines
tests/i915/gem_shrink.c +0
-0
tests/i915/gem_shrink.c igt_main · line 439
Quoted 8 lines
tests/i915/gem_shrink.c +2
-0@@ -432,6 +432,8 @@ igt_main fd =drm_open_driver (DRIVER_INTEL );igt_require_gem (fd); +gem_require_mappable_ggtt (fd); +/* * Spawn enough processes to use all memory, but each only * uses half the available mappable aperture ~128MiB.
And for this one the same I think. Apart from the subtests using mmap-gtt other ones could probably be made work by calculating the working set in a different way. Possibly just use the ggtt size and skip tests which need aperture if no aperture. Chris would that be acceptable or there is a special reason to have N clients with each using an aperture sized amount of memory, to total RAM size?
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoting Tvrtko Ursulin (2020-11-30 10:04:17)
Quoted 14 lines · Arjun Melkaveri
Quoted 12 lines
Added
gem_require_mappable_ggttto check mappable aperture. This is to avoid any test crash that might happen if mappable aperture is not avilable.Cc Chris Wilson <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Arjun Melkaveri <[email protected]>--- tests/i915/gem_exec_reloc.c | 3 +++ tests/i915/gem_shrink.c | 2 ++ 2 files changed, 5 insertions(+)
Quoted 13 lines
tests/i915/gem_exec_reloc.c igt_main · line 1220
Quoted 9 lines
tests/i915/gem_exec_reloc.c +1
-0@@ -1217,6 +1217,7 @@ igt_mainif (!(f->flags &NORELOC )) {igt_subtest_f ("%srange%s" , f->basic ? "basic-" : "", f->name) { +gem_require_mappable_ggtt (fd);From the code and commit message it is not immediately obvious to me
whybasic_rangeneeds the aperture, Chris? Answer to that will drive the solution.
It does not.
Quoted 18 lines
tests/i915/gem_exec_reloc.c igt_main · line 1268
Quoted 9 lines
tests/i915/gem_exec_reloc.c +1
-0igt_while_interruptible(f->flags & INTERRUPTIBLE)basic_range (fd, f->flags); }@@ -1264,6 +1265,7 @@ igt_main } igt_subtest_with_dynamic("basic-spin") { +!
Quoted 6 lines
tests/i915/gem_exec_reloc.c +0
-0__for_each_physical_engine (fd, e) { igt_dynamic_f("%s", e->name)active_spin (fd, e->flags);@@ -1278,6 +1280,7 @@ igt_main }
Quoted 8 lines
tests/i915/gem_exec_reloc.c igt_main · line 1286
Quoted 5 lines
tests/i915/gem_exec_reloc.c +1
-0igt_subtest_with_dynamic("basic-many-active") { +gem_require_mappable_ggtt (fd);__for_each_physical_engine (fd, e) { igt_dynamic_f("%s", e->name)many_active (fd, e->flags);Same for
many_active- maybe tests should use ggtt size and not aperture, with some tweaks to make size/runtime sane?
It does not. This is somebody hacking over a major kernel bug.
Quoted 8 lines
Quoted 8 lines
tests/i915/gem_shrink.c +0
-0@@ -432,6 +432,8 @@ igt_main fd =drm_open_driver (DRIVER_INTEL );igt_require_gem (fd);
Quoted 13 lines
tests/i915/gem_shrink.c igt_main · line 439
Quoted 6 lines
tests/i915/gem_shrink.c +2
-0+gem_require_mappable_ggtt (fd); +/* * Spawn enough processes to use all memory, but each only * uses half the available mappable aperture ~128MiB. And for this one the same I think. Apart from the subtests using mmap-gtt other ones could probably be made work by calculating the working set in a different way. Possibly just use the ggtt size and skip tests which need aperture if no aperture. Chris would that be acceptable or there is a special reason to have N clients with each using an aperture sized amount of memory, to total RAM size?
shrink is system memory limits.
-Chris
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 28 lines · Chris Wilson
Quoting Tvrtko Ursulin (2020-11-30 10:04:17)
Quoted 13 lines · Arjun Melkaveri
Quoted 12 lines
Added
gem_require_mappable_ggttto check mappable aperture. This is to avoid any test crash that might happen if mappable aperture is not avilable.Cc Chris Wilson <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Arjun Melkaveri <[email protected]>--- tests/i915/gem_exec_reloc.c | 3 +++ tests/i915/gem_shrink.c | 2 ++ 2 files changed, 5 insertions(+)Quoted 13 lines
tests/i915/gem_exec_reloc.c igt_main · line 1220
Quoted 9 lines
tests/i915/gem_exec_reloc.c +1
-0@@ -1217,6 +1217,7 @@ igt_mainif (!(f->flags &NORELOC )) {igt_subtest_f ("%srange%s" , f->basic ? "basic-" : "", f->name) { +gem_require_mappable_ggtt (fd);From the code and commit message it is not immediately obvious to me
whybasic_rangeneeds the aperture, Chris? Answer to that will drive the solution.
Quoted 1 line
It does not.
Okay, so the plan for this one should be to stop probing aperture size and instead probe the size of the address space in use. This will be ggtt on old gens and ppgtt on new ones. And to keep object count in check with regards to available backing store, if required (not sure right now).
Quoted 27 lines
Quoted 18 lines
tests/i915/gem_exec_reloc.c igt_main · line 1268
Quoted 9 lines
tests/i915/gem_exec_reloc.c +1
-0igt_while_interruptible(f->flags & INTERRUPTIBLE)basic_range (fd, f->flags); }@@ -1264,6 +1265,7 @@ igt_main } igt_subtest_with_dynamic("basic-spin") { +!
Quoted 6 lines
tests/i915/gem_exec_reloc.c +0
-0__for_each_physical_engine (fd, e) { igt_dynamic_f("%s", e->name)active_spin (fd, e->flags);@@ -1278,6 +1280,7 @@ igt_main }Quoted 8 lines
tests/i915/gem_exec_reloc.c igt_main · line 1286
Quoted 5 lines
tests/i915/gem_exec_reloc.c +1
-0igt_subtest_with_dynamic("basic-many-active") { +gem_require_mappable_ggtt (fd);__for_each_physical_engine (fd, e) { igt_dynamic_f("%s", e->name)many_active (fd, e->flags);Same for
many_active- maybe tests should use ggtt size and not aperture, with some tweaks to make size/runtime sane?
Quoted 1 line
It does not. This is somebody hacking over a major kernel bug.
Okay so same as above, don't probe aperture but address space size.
Quoted 23 lines
Quoted 9 lines
Quoted 9 lines
tests/i915/gem_shrink.c +0
-0@@ -432,6 +432,8 @@ igt_main fd =drm_open_driver (DRIVER_INTEL );igt_require_gem (fd);Quoted 13 lines
tests/i915/gem_shrink.c igt_main · line 439
Quoted 6 lines
tests/i915/gem_shrink.c +2
-0+gem_require_mappable_ggtt (fd); +/* * Spawn enough processes to use all memory, but each only * uses half the available mappable aperture ~128MiB. And for this one the same I think. Apart from the subtests using mmap-gtt other ones could probably be made work by calculating the working set in a different way. Possibly just use the ggtt size and skip tests which need aperture if no aperture. Chris would that be acceptable or there is a special reason to have N clients with each using an aperture sized amount of memory, to total RAM size?
Quoted 1 line
shrink is system memory limits.
Yes, I was ignoring that aspect for now and focusing on the aperture size misuse. But yes, making gem_shrink falsely pass on dg1 is not what we really want. Probably make it explicitly use system memory objects once that API is available.
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 30 lines · Tvrtko Ursulin
Quoted 28 lines · Chris Wilson
Quoting Tvrtko Ursulin (2020-11-30 10:04:17)
Quoted 26 lines · Arjun Melkaveri
Quoted 17 lines
Added
gem_require_mappable_ggttto check mappable aperture. This is to avoid any test crash that might happen if mappable aperture is not avilable.Cc Chris Wilson <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Arjun Melkaveri <[email protected]>--- tests/i915/gem_exec_reloc.c | 3 +++ tests/i915/gem_shrink.c | 2 ++ 2 files changed, 5 insertions(+)tests/i915/gem_exec_reloc.c +0
-0tests/i915/gem_exec_reloc.c igt_main · line 1220
Quoted 4 lines
tests/i915/gem_exec_reloc.c +1
-0@@ -1217,6 +1217,7 @@ igt_mainif (!(f->flags &NORELOC )) {igt_subtest_f ("%srange%s" , f->basic ? "basic-" : "", f->name) { +gem_require_mappable_ggtt (fd);From the code and commit message it is not immediately obvious to me
whybasic_rangeneeds the aperture, Chris? Answer to that will drive the solution.
Quoted 6 lines
Quoted 1 line
It does not.
Okay, so the plan for this one should be to stop probing aperture size and instead probe the size of the address space in use. This will be ggtt on old gens and ppgtt on new ones. And to keep object count in check with regards to available backing store, if required (not sure right now).
Let me know if this is okay
#define MAX_47b ((1ull << 47)) // address range's most signifcant bit. const uint64_t max = (AT_LEAST_GEN(devid, 8) ? MAX_47b : gem_aperture_size(i915) / 2); instead of checking gem_require_mappable_ggtt in subtest .
Quoted 54 lines
Quoted 26 lines
Quoted 12 lines
tests/i915/gem_exec_reloc.c igt_main · line 1267
Quoted 9 lines
tests/i915/gem_exec_reloc.c +1
-0igt_while_interruptible(f->flags & INTERRUPTIBLE)basic_range (fd, f->flags); }@@ -1264,6 +1265,7 @@ igt_main } igt_subtest_with_dynamic("basic-spin") { +!
Quoted 13 lines
tests/i915/gem_exec_reloc.c igt_main · line 1285
Quoted 10 lines
tests/i915/gem_exec_reloc.c +1
-0__for_each_physical_engine (fd, e) { igt_dynamic_f("%s", e->name)active_spin (fd, e->flags);@@ -1278,6 +1280,7 @@ igt_main } igt_subtest_with_dynamic("basic-many-active") { +gem_require_mappable_ggtt (fd);__for_each_physical_engine (fd, e) { igt_dynamic_f("%s", e->name)many_active (fd, e->flags);Same for
many_active- maybe tests should use ggtt size and not aperture, with some tweaks to make size/runtime sane?Quoted 1 line
It does not. This is somebody hacking over a major kernel bug.
Okay so same as above, don't probe aperture but address space size.
Quoted 22 lines
Quoted 13 lines
Quoted 13 lines
tests/i915/gem_shrink.c +2
-0@@ -432,6 +432,8 @@ igt_main fd =drm_open_driver (DRIVER_INTEL );igt_require_gem (fd); +gem_require_mappable_ggtt (fd); +/* * Spawn enough processes to use all memory, but each only * uses half the available mappable aperture ~128MiB. Quoted 8 lines
Quoted 1 line
And for this one the same I think. Apart from the subtests using mmap-gtt other ones could probably be made work by calculating the working set in a different way. Possibly just use the ggtt size and skip tests which need aperture if no aperture. Chris would that be acceptable or there is a special reason to have N clients with each using an aperture sized amount of memory, to total RAM size?
Quoted 1 line
shrink is system memory limits.
Quoted 8 lines
Yes, I was ignoring that aspect for now and focusing on the aperture size misuse. But yes, making
gem_shrinkfalsely pass on dg1 is not what we really want. Probably make it explicitly use system memory objects once that API is available.Regards,
Tvrtko
Any suggestion for this ? can we use gem_require_mappable_ggtt as all tests use size from gem_mappable_aperture_size. or can i modify code something like this
#define MAX_32b ((1ull << 32))
alloc_size = AT_LEAST_GEN(intel_get_drm_devid(fd), 8) ? MAX_32b : gem_mappable_aperture_size(); alloc_size = alloc_size /2
Test would probabbly skip if estimated size is more than RAM + swap)
-Arjun
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoting Melkaveri, Arjun (2020-12-02 11:05:23)
Quoted 33 lines · Tvrtko Ursulin
Quoted 32 lines · Chris Wilson
Quoted 29 lines
Quoting Tvrtko Ursulin (2020-11-30 10:04:17)
Quoted 13 lines · Arjun Melkaveri
Quoted 12 lines
Added
gem_require_mappable_ggttto check mappable aperture. This is to avoid any test crash that might happen if mappable aperture is not avilable.Cc Chris Wilson <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Arjun Melkaveri <[email protected]>--- tests/i915/gem_exec_reloc.c | 3 +++ tests/i915/gem_shrink.c | 2 ++ 2 files changed, 5 insertions(+)Quoted 13 lines
tests/i915/gem_exec_reloc.c igt_main · line 1220
Quoted 9 lines
tests/i915/gem_exec_reloc.c +1
-0@@ -1217,6 +1217,7 @@ igt_mainif (!(f->flags &NORELOC )) {igt_subtest_f ("%srange%s" , f->basic ? "basic-" : "", f->name) { +gem_require_mappable_ggtt (fd);From the code and commit message it is not immediately obvious to me
whybasic_rangeneeds the aperture, Chris? Answer to that will drive the solution.It does not.
Quoted 8 lines
Quoted 4 lines
Okay, so the plan for this one should be to stop probing aperture size and instead probe the size of the address space in use. This will be ggtt on old gens and ppgtt on new ones. And to keep object count in check with regards to available backing store, if required (not sure right now).
Let me know if this is okay
#defineMAX_47b((1ull << 47)) // address range's most signifcant bit. constuint64_tmax = (AT_LEAST_GEN(devid, 8)?MAX_47b:gem_aperture_size(i915)/ 2); instead of checkinggem_require_mappable_ggttin subtest .
Where are you getting the impression that basic_range() uses the mappable aperture?
Quoted 28 lines
Quoted 28 lines
Quoted 21 lines
Quoted 12 lines
Quoted 12 lines
tests/i915/gem_shrink.c +2
-0@@ -432,6 +432,8 @@ igt_main fd =drm_open_driver (DRIVER_INTEL );igt_require_gem (fd); +gem_require_mappable_ggtt (fd); +/* * Spawn enough processes to use all memory, but each only * uses half the available mappable aperture ~128MiB. Quoted 8 lines
Quoted 1 line
And for this one the same I think. Apart from the subtests using mmap-gtt other ones could probably be made work by calculating the working set in a different way. Possibly just use the ggtt size and skip tests which need aperture if no aperture. Chris would that be acceptable or there is a special reason to have N clients with each using an aperture sized amount of memory, to total RAM size?
Quoted 1 line
shrink is system memory limits.
Yes, I was ignoring that aspect for now and focusing on the aperture size misuse. But yes, making
gem_shrinkfalsely pass on dg1 is not what we really want. Probably make it explicitly use system memory objects once that API is available.
Quoted 7 lines
Quoted 3 lines
Regards,
Tvrtko
Any suggestion for this ? can we use
gem_require_mappable_ggttas all tests use size fromgem_mappable_aperture_size. or can i modify code something like this
#defineMAX_32b((1ull << 32))
More conservative; use the 128MiB that I mention in the comments. The goal is to have many processes pushing the system to the edge so that there is plenty of contention on the shrinker. Being specifically a shrinker test, they should remain smem objects.
-Chris
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 38 lines · Chris Wilson
Quoting Melkaveri, Arjun (2020-12-02 11:05:23)
Quoted 37 lines · Tvrtko Ursulin
Quoted 36 lines · Chris Wilson
Quoted 28 lines
Quoting Tvrtko Ursulin (2020-11-30 10:04:17)
Quoted 13 lines · Arjun Melkaveri
Quoted 12 lines
Added
gem_require_mappable_ggttto check mappable aperture. This is to avoid any test crash that might happen if mappable aperture is not avilable.Cc Chris Wilson <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Arjun Melkaveri <[email protected]>--- tests/i915/gem_exec_reloc.c | 3 +++ tests/i915/gem_shrink.c | 2 ++ 2 files changed, 5 insertions(+)Quoted 13 lines
tests/i915/gem_exec_reloc.c igt_main · line 1220
Quoted 9 lines
tests/i915/gem_exec_reloc.c +1
-0@@ -1217,6 +1217,7 @@ igt_mainif (!(f->flags &NORELOC )) {igt_subtest_f ("%srange%s" , f->basic ? "basic-" : "", f->name) { +gem_require_mappable_ggtt (fd);From the code and commit message it is not immediately obvious to me
whybasic_rangeneeds the aperture, Chris? Answer to that will drive the solution.Quoted 1 line
It does not.
Okay, so the plan for this one should be to stop probing aperture size and instead probe the size of the address space in use. This will be ggtt on old gens and ppgtt on new ones. And to keep object count in check with regards to available backing store, if required (not sure right now).
Quoted 7 lines
Quoted 4 lines
Let me know if this is okay
#defineMAX_47b((1ull << 47)) // address range's most signifcant bit. constuint64_tmax = (AT_LEAST_GEN(devid, 8)?MAX_47b:gem_aperture_size(i915)/ 2); instead of checkinggem_require_mappable_ggttin subtest .Where are you getting the impression that
basic_range()uses the mappable aperture?
my bad , i'll send patch only for gem_shrink that uses gem_require_mappable_ggtt.
I was in doubt if aperture is not supported , gem_aperture_size would return 0 . something like on dg1.
I got to know that gem_aperture_size, it would return gtt address space size. Will withdraw this changes .
Thanks
-Arjun
Quoted 37 lines
Quoted 29 lines
Quoted 29 lines
Quoted 22 lines
Quoted 13 lines
Quoted 13 lines
tests/i915/gem_shrink.c +2
-0@@ -432,6 +432,8 @@ igt_main fd =drm_open_driver (DRIVER_INTEL );igt_require_gem (fd); +gem_require_mappable_ggtt (fd); +/* * Spawn enough processes to use all memory, but each only * uses half the available mappable aperture ~128MiB. Quoted 8 lines
Quoted 1 line
And for this one the same I think. Apart from the subtests using mmap-gtt other ones could probably be made work by calculating the working set in a different way. Possibly just use the ggtt size and skip tests which need aperture if no aperture. Chris would that be acceptable or there is a special reason to have N clients with each using an aperture sized amount of memory, to total RAM size?
Quoted 1 line
shrink is system memory limits.
Yes, I was ignoring that aspect for now and focusing on the aperture size misuse. But yes, making
gem_shrinkfalsely pass on dg1 is not what we really want. Probably make it explicitly use system memory objects once that API is available.Quoted 7 lines
Quoted 3 lines
Regards,
Tvrtko
Any suggestion for this ? can we use
gem_require_mappable_ggttas all tests use size fromgem_mappable_aperture_size. or can i modify code something like this
#defineMAX_32b((1ull << 32))
Quoted 5 lines
More conservative; use the 128MiB that I mention in the comments. The goal is to have many processes pushing the system to the edge so that there is plenty of contention on the shrinker. Being specifically a shrinker test, they should remain smem objects.
-Chris
Will modify this to use 128 MiB .
Thanks
Arjun
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Patchwork
CI[igt-dev] ✓ Fi.CI.BAT: success for gem_exec_reloc & gem_shrink: Added gem_require_mappable_ggtt to check mappable aperture
In reply to Arjun Melkaveri== Series Details ==
== Series Details ==
Series: gem_exec_reloc & gem_shrink: Added gem_require_mappable_ggtt to check mappable aperture
URL : https://patchwork.freedesktop.org/series/84387/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9404 -> IGTPW_5238
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/index.html
Known issues
------------
Here are the changes found in IGTPW_5238 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_close_race@basic-threads:
- fi-bsw-kefka: [PASS][1] -> [DMESG-WARN][2] ([i915#1982])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/fi-bsw-kefka/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/fi-bsw-kefka/igt@[email protected]
* igt@gem_mmap_gtt@basic:
- fi-tgl-y: [PASS][3] -> [DMESG-WARN][4] ([i915#402]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/fi-tgl-y/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/fi-tgl-y/igt@[email protected]
* igt@i915_module_load@reload:
- fi-icl-u2: [PASS][5] -> [DMESG-WARN][6] ([i915#1982]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/fi-icl-u2/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/fi-icl-u2/igt@[email protected]
- fi-kbl-soraka: [PASS][7] -> [DMESG-WARN][8] ([i915#1982])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/fi-kbl-soraka/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/fi-kbl-soraka/igt@[email protected]
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-bsw-n3050: [PASS][9] -> [DMESG-WARN][10] ([i915#1982])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/fi-bsw-n3050/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/fi-bsw-n3050/igt@[email protected]
#### Possible fixes ####
* igt@core_hotunplug@unbind-rebind:
- fi-kbl-7500u: [DMESG-WARN][11] -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/fi-kbl-7500u/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/fi-kbl-7500u/igt@[email protected]
* igt@debugfs_test@read_all_entries:
- fi-tgl-y: [DMESG-WARN][13] ([i915#402]) -> [PASS][14] +2 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/fi-tgl-y/igt@debugfs_test@read_all_entries.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/fi-tgl-y/igt@debugfs_test@read_all_entries.html
* igt@i915_pm_rpm@module-reload:
- fi-kbl-soraka: [DMESG-WARN][15] ([i915#1982]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/fi-kbl-soraka/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/fi-kbl-soraka/igt@[email protected]
* igt@kms_busy@basic@flip:
- fi-tgl-y: [DMESG-WARN][17] ([i915#1982]) -> [PASS][18] +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/fi-tgl-y/igt@kms_busy@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/fi-tgl-y/igt@kms_busy@[email protected]
* igt@kms_chamelium@dp-crc-fast:
- fi-cml-u2: [FAIL][19] ([i915#1161] / [i915#262]) -> [PASS][20]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/fi-cml-u2/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/fi-cml-u2/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-icl-u2: [DMESG-WARN][21] ([i915#1982]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/fi-icl-u2/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/fi-icl-u2/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1161]: https://gitlab.freedesktop.org/drm/intel/issues/1161
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#262]: https://gitlab.freedesktop.org/drm/intel/issues/262
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
Participating hosts (45 -> 39)
------------------------------
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-dg1-1 fi-blb-e6850 fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5876 -> IGTPW_5238
CI-20190529: 20190529
CI_DRM_9404: f515fa81d87ef367735d3a57a002fc72c8e55909 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5238: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/index.html
IGT_5876: cf2f41b3d3dfabaf3a4837062f996f3491a350b1 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Patchwork
CI[igt-dev] ✗ Fi.CI.IGT: failure for gem_exec_reloc & gem_shrink: Added gem_require_mappable_ggtt to check mappable aperture
In reply to Arjun Melkaveri== Series Details ==
== Series Details ==
Series: gem_exec_reloc & gem_shrink: Added gem_require_mappable_ggtt to check mappable aperture
URL : https://patchwork.freedesktop.org/series/84387/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9404_full -> IGTPW_5238_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_5238_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in IGTPW_5238_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_5238/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_5238_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_exec_reloc@basic-wide-active@bcs0:
- shard-glk: NOTRUN -> [FAIL][1] +3 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-glk5/igt@gem_exec_reloc@[email protected]
Known issues
------------
Here are the changes found in IGTPW_5238_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_gttfill@all:
- shard-glk: [PASS][2] -> [DMESG-WARN][3] ([i915#118] / [i915#95])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-glk1/igt@[email protected]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-glk7/igt@[email protected]
* igt@gem_exec_reloc@basic-many-active@rcs0:
- shard-hsw: [PASS][4] -> [FAIL][5] ([i915#2389])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-hsw6/igt@gem_exec_reloc@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-hsw4/igt@gem_exec_reloc@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [PASS][6] -> [SKIP][7] ([i915#2190])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-tglb3/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-tglb6/igt@[email protected]
* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-tglb: [PASS][8] -> [INCOMPLETE][9] ([i915#1436] / [i915#1602] / [i915#1887] / [i915#2411] / [i915#456])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-tglb3/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-tglb3/igt@[email protected]
- shard-apl: [PASS][10] -> [INCOMPLETE][11] ([i915#2635])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-apl2/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-apl6/igt@[email protected]
- shard-iclb: [PASS][12] -> [INCOMPLETE][13] ([i915#1185])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-iclb8/igt@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-iclb2/igt@[email protected]
- shard-kbl: [PASS][14] -> [INCOMPLETE][15] ([i915#155] / [i915#794])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-kbl2/igt@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-kbl4/igt@[email protected]
- shard-hsw: [PASS][16] -> [INCOMPLETE][17] ([i915#2055] / [i915#2637])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-hsw4/igt@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-hsw6/igt@[email protected]
- shard-glk: [PASS][18] -> [INCOMPLETE][19] ([i915#2199] / [i915#2635])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-glk3/igt@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-glk1/igt@[email protected]
* igt@kms_big_fb@yf-tiled-32bpp-rotate-180:
- shard-iclb: [PASS][20] -> [FAIL][21] ([i915#1119])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-iclb8/igt@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-iclb5/igt@[email protected]
* igt@kms_cursor_edge_walk@pipe-b-64x64-left-edge:
- shard-apl: [PASS][22] -> [DMESG-WARN][23] ([i915#1982]) +5 similar issues
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-apl1/igt@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-apl3/igt@[email protected]
- shard-glk: [PASS][24] -> [DMESG-WARN][25] ([i915#1982]) +2 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-glk5/igt@[email protected]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-glk6/igt@[email protected]
* igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy:
- shard-glk: [PASS][26] -> [FAIL][27] ([i915#72])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-glk9/igt@[email protected]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-glk8/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-varying-size:
- shard-tglb: [PASS][28] -> [FAIL][29] ([i915#2346])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-tglb2/igt@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-tglb6/igt@[email protected]
* igt@kms_flip@flip-vs-absolute-wf_vblank@a-edp1:
- shard-tglb: [PASS][30] -> [FAIL][31] ([i915#2122])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-tglb2/igt@kms_flip@[email protected]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-tglb6/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc:
- shard-kbl: [PASS][32] -> [DMESG-WARN][33] ([i915#1982]) +1 similar issue
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-kbl2/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-kbl6/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-indfb-draw-mmap-wc:
- shard-tglb: [PASS][34] -> [DMESG-WARN][35] ([i915#1982])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-tglb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-indfb-draw-mmap-wc.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-tglb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-indfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-mmap-cpu:
- shard-iclb: [PASS][36] -> [DMESG-WARN][37] ([i915#1982]) +1 similar issue
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-iclb7/igt@[email protected]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-iclb1/igt@[email protected]
* igt@kms_pipe_crc_basic@disable-crc-after-crtc-pipe-c:
- shard-hsw: [PASS][38] -> [DMESG-WARN][39] ([i915#1982]) +1 similar issue
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-hsw6/igt@[email protected]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-hsw6/igt@[email protected]
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [PASS][40] -> [SKIP][41] ([fdo#109441])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-iclb1/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@testdisplay:
- shard-kbl: [PASS][42] -> [DMESG-WARN][43] ([i915#165] / [i915#78]) +1 similar issue
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-kbl4/[email protected]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-kbl2/[email protected]
#### Possible fixes ####
* igt@gem_exec_reloc@basic-many-active@rcs0:
- shard-glk: [FAIL][44] ([i915#2389]) -> [PASS][45]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-glk8/igt@gem_exec_reloc@[email protected]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-glk6/igt@gem_exec_reloc@[email protected]
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-hsw: [WARN][46] ([i915#1519]) -> [PASS][47]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-hsw4/igt@[email protected]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-hsw4/igt@[email protected]
* {igt@kms_async_flips@alternate-sync-async-flip}:
- shard-tglb: [FAIL][48] ([i915#2521]) -> [PASS][49]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-tglb3/igt@[email protected]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-tglb3/igt@[email protected]
* {igt@kms_async_flips@test-time-stamp}:
- shard-tglb: [FAIL][50] ([i915#2597]) -> [PASS][51]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-tglb8/igt@[email protected]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-tglb6/igt@[email protected]
* igt@kms_big_fb@linear-8bpp-rotate-180:
- shard-apl: [DMESG-WARN][52] ([i915#1982]) -> [PASS][53] +5 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-apl6/igt@[email protected]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-apl6/igt@[email protected]
* igt@kms_flip@2x-plain-flip-fb-recreate-interruptible@ac-vga1-hdmi-a1:
- shard-hsw: [FAIL][54] ([i915#2122]) -> [PASS][55]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-hsw6/igt@kms_flip@[email protected]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-hsw4/igt@kms_flip@[email protected]
* igt@kms_flip@2x-plain-flip@ab-vga1-hdmi-a1:
- shard-hsw: [DMESG-WARN][56] ([i915#1982]) -> [PASS][57]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-hsw6/igt@kms_flip@[email protected]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-hsw6/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-badstride:
- shard-glk: [DMESG-WARN][58] ([i915#1982]) -> [PASS][59] +5 similar issues
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-glk9/igt@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-glk1/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-wc:
- shard-tglb: [DMESG-WARN][60] ([i915#1982]) -> [PASS][61] +4 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-tglb8/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-wc.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-tglb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-indfb-pgflip-blt:
- shard-iclb: [DMESG-WARN][62] ([i915#1982]) -> [PASS][63]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-iclb3/igt@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-iclb2/igt@[email protected]
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [SKIP][64] ([fdo#109441]) -> [PASS][65] +1 similar issue
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-iclb6/igt@kms_psr@psr2_sprite_plane_move.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
* igt@kms_vblank@pipe-b-wait-forked-busy:
- shard-kbl: [DMESG-WARN][66] ([i915#1982]) -> [PASS][67] +3 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-kbl1/igt@[email protected]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-kbl2/igt@[email protected]
* igt@perf_pmu@module-unload:
- shard-apl: [DMESG-WARN][68] ([i915#1982] / [i915#262]) -> [PASS][69]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-apl6/igt@[email protected]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-apl3/igt@[email protected]
#### Warnings ####
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: [WARN][70] ([i915#1804] / [i915#2684]) -> [WARN][71] ([i915#2681] / [i915#2684])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-iclb3/igt@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-iclb1/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-alpha-7efc:
- shard-apl: [DMESG-FAIL][72] ([fdo#108145] / [i915#1982]) -> [FAIL][73] ([fdo#108145] / [i915#265])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-apl7/igt@[email protected]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-apl3/igt@[email protected]
* igt@runner@aborted:
- shard-iclb: [FAIL][74] ([i915#2295] / [i915#2722]) -> ([FAIL][75], [FAIL][76]) ([i915#2295] / [i915#2722] / [i915#483])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-iclb4/igt@[email protected]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-iclb7/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-iclb2/igt@[email protected]
- shard-glk: ([FAIL][77], [FAIL][78]) ([i915#1814] / [i915#2295] / [i915#2722] / [k.org#202321]) -> ([FAIL][79], [FAIL][80]) ([i915#2295] / [i915#2722] / [k.org#202321])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-glk8/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-glk2/igt@[email protected]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-glk1/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-glk8/igt@[email protected]
- shard-tglb: [FAIL][81] ([i915#2295] / [i915#2722]) -> ([FAIL][82], [FAIL][83]) ([i915#1602] / [i915#2295] / [i915#2722])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9404/shard-tglb6/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-tglb3/igt@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/shard-tglb3/igt@[email protected]
{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#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1185]: https://gitlab.freedesktop.org/drm/intel/issues/1185
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1519]: https://gitlab.freedesktop.org/drm/intel/issues/1519
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1814]: https://gitlab.freedesktop.org/drm/intel/issues/1814
[i915#1887]: https://gitlab.freedesktop.org/drm/intel/issues/1887
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2055]: https://gitlab.freedesktop.org/drm/intel/issues/2055
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2199]: https://gitlab.freedesktop.org/drm/intel/issues/2199
[i915#2295]: https://gitlab.freedesktop.org/drm/intel/issues/2295
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2389]: https://gitlab.freedesktop.org/drm/intel/issues/2389
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2597]: https://gitlab.freedesktop.org/drm/intel/issues/2597
[i915#262]: https://gitlab.freedesktop.org/drm/intel/issues/262
[i915#2635]: https://gitlab.freedesktop.org/drm/intel/issues/2635
[i915#2637]: https://gitlab.freedesktop.org/drm/intel/issues/2637
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#2684]: https://gitlab.freedesktop.org/drm/intel/issues/2684
[i915#2722]: https://gitlab.freedesktop.org/drm/intel/issues/2722
[i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456
[i915#483]: https://gitlab.freedesktop.org/drm/intel/issues/483
[i915#72]: https://gitlab.freedesktop.org/drm/intel/issues/72
[i915#78]: https://gitlab.freedesktop.org/drm/intel/issues/78
[i915#794]: https://gitlab.freedesktop.org/drm/intel/issues/794
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[k.org#202321]: https://bugzilla.kernel.org/show_bug.cgi?id=202321
Participating hosts (10 -> 8)
------------------------------
Missing (2): pig-skl-6260u pig-glk-j5005
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5876 -> IGTPW_5238
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_9404: f515fa81d87ef367735d3a57a002fc72c8e55909 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5238: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5238/index.html
IGT_5876: cf2f41b3d3dfabaf3a4837062f996f3491a350b1 @ 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_5238/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev