* [igt-dev] [PATCH i-g-t v2 0/1] tests/prime_vgem: Fix broken handling of interprocess pipes
@ 2019-07-11 8:39 Janusz Krzysztofik
2019-07-11 8:39 ` [igt-dev] [PATCH i-g-t v2 1/1] " Janusz Krzysztofik
` (3 more replies)
0 siblings, 4 replies; 7+ messages in thread
From: Janusz Krzysztofik @ 2019-07-11 8:39 UTC (permalink / raw)
To: Petri Latvala, Arkadiusz Hiler; +Cc: igt-dev
If a child process dies for any reason while basic-fence-read or
basic-fence-mmap subtest is run, the subtest may hang indefinitely on
read() from a pipe which is supposed to be written to by that child (can
be interrupted though). Fix it by first closing unused pipe ends on both
parent and child side before using the pipe, as recommended by pipe(2)
manual page.
Please note that due to the IGT library way of handling signals, now the
subtests may fail with error code 141 (128 + SIGPIPE) and no usual DEBUG
message block on stderr nor FAIL message line on stdout, however some
meaningful error messages will still be printed on stderr by the failing
child processes.
v2: resend with Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
added
Janusz Krzysztofik (1):
tests/prime_vgem: Fix broken handling of interprocess pipes
tests/prime_vgem.c | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
--
2.21.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
* [igt-dev] [PATCH i-g-t v2 1/1] tests/prime_vgem: Fix broken handling of interprocess pipes
2019-07-11 8:39 [igt-dev] [PATCH i-g-t v2 0/1] tests/prime_vgem: Fix broken handling of interprocess pipes Janusz Krzysztofik
@ 2019-07-11 8:39 ` Janusz Krzysztofik
2019-07-11 10:39 ` [igt-dev] [PATCH i-g-t v2 0/1] " Ser, Simon
` (2 subsequent siblings)
3 siblings, 0 replies; 7+ messages in thread
From: Janusz Krzysztofik @ 2019-07-11 8:39 UTC (permalink / raw)
To: Petri Latvala, Arkadiusz Hiler; +Cc: igt-dev
If a child process dies for any reason while basic-fence-read or
basic-fence-mmap subtest is run, the subtest may hang indefinitely on
read() from a pipe which is supposed to be written to by that child (can
be interrupted though). Fix it by first closing unused pipe ends on both
parent and child side before using the pipe, as recommended by pipe(2)
manual page.
Please note that due to the IGT library way of handling signals, now the
subtests may fail with error code 141 (128 + SIGPIPE) and no usual DEBUG
message block on stderr nor FAIL message line on stdout, however some
meaningful error messages will still be printed on stderr by the failing
child processes.
Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
---
tests/prime_vgem.c | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/tests/prime_vgem.c b/tests/prime_vgem.c
index 69ae8c9b..bebf9edc 100644
--- a/tests/prime_vgem.c
+++ b/tests/prime_vgem.c
@@ -82,6 +82,8 @@ static void test_fence_read(int i915, int vgem)
close(dmabuf);
igt_fork(child, 1) {
+ close(master[0]);
+ close(slave[1]);
for (i = 0; i < 1024; i++) {
uint32_t tmp;
gem_read(i915, handle, 4096*i, &tmp, sizeof(tmp));
@@ -97,6 +99,8 @@ static void test_fence_read(int i915, int vgem)
gem_close(i915, handle);
}
+ close(master[1]);
+ close(slave[0]);
read(master[0], &i, sizeof(i));
fence = vgem_fence_attach(vgem, &scratch, VGEM_FENCE_WRITE);
write(slave[1], &i, sizeof(i));
@@ -110,8 +114,6 @@ static void test_fence_read(int i915, int vgem)
igt_waitchildren();
close(master[0]);
- close(master[1]);
- close(slave[0]);
close(slave[1]);
}
@@ -137,6 +139,8 @@ static void test_fence_mmap(int i915, int vgem)
close(dmabuf);
igt_fork(child, 1) {
+ close(master[0]);
+ close(slave[1]);
ptr = gem_mmap__gtt(i915, handle, 4096*1024, PROT_READ);
gem_set_domain(i915, handle, I915_GEM_DOMAIN_GTT, 0);
@@ -153,6 +157,8 @@ static void test_fence_mmap(int i915, int vgem)
gem_close(i915, handle);
}
+ close(master[1]);
+ close(slave[0]);
read(master[0], &i, sizeof(i));
fence = vgem_fence_attach(vgem, &scratch, VGEM_FENCE_WRITE);
write(slave[1], &i, sizeof(i));
@@ -166,8 +172,6 @@ static void test_fence_mmap(int i915, int vgem)
igt_waitchildren();
close(master[0]);
- close(master[1]);
- close(slave[0]);
close(slave[1]);
}
--
2.21.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2 0/1] tests/prime_vgem: Fix broken handling of interprocess pipes
2019-07-11 8:39 [igt-dev] [PATCH i-g-t v2 0/1] tests/prime_vgem: Fix broken handling of interprocess pipes Janusz Krzysztofik
2019-07-11 8:39 ` [igt-dev] [PATCH i-g-t v2 1/1] " Janusz Krzysztofik
@ 2019-07-11 10:39 ` Ser, Simon
2019-07-11 10:49 ` Janusz Krzysztofik
2019-07-11 14:17 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/prime_vgem: Fix broken handling of interprocess pipes (rev2) Patchwork
2019-07-12 5:47 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
3 siblings, 1 reply; 7+ messages in thread
From: Ser, Simon @ 2019-07-11 10:39 UTC (permalink / raw)
To: Hiler, Arkadiusz, Latvala, Petri, janusz.krzysztofik; +Cc: igt-dev
On Thu, 2019-07-11 at 10:39 +0200, Janusz Krzysztofik wrote:
> If a child process dies for any reason while basic-fence-read or
> basic-fence-mmap subtest is run, the subtest may hang indefinitely on
> read() from a pipe which is supposed to be written to by that child
> (can
> be interrupted though). Fix it by first closing unused pipe ends on
> both
> parent and child side before using the pipe, as recommended by
> pipe(2)
> manual page.
>
> Please note that due to the IGT library way of handling signals, now
> the
> subtests may fail with error code 141 (128 + SIGPIPE) and no usual
> DEBUG
> message block on stderr nor FAIL message line on stdout, however some
> meaningful error messages will still be printed on stderr by the
> failing
> child processes.
>
> v2: resend with Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> added
You generally don't need to resend a patch just to add a R-b tag.
Do you have IGT commit rights?
> Janusz Krzysztofik (1):
> tests/prime_vgem: Fix broken handling of interprocess pipes
>
> tests/prime_vgem.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2 0/1] tests/prime_vgem: Fix broken handling of interprocess pipes
2019-07-11 10:39 ` [igt-dev] [PATCH i-g-t v2 0/1] " Ser, Simon
@ 2019-07-11 10:49 ` Janusz Krzysztofik
2019-07-11 11:17 ` Ser, Simon
0 siblings, 1 reply; 7+ messages in thread
From: Janusz Krzysztofik @ 2019-07-11 10:49 UTC (permalink / raw)
To: Ser, Simon; +Cc: igt-dev, Latvala, Petri
Hi Simon,
On Thursday, July 11, 2019 12:39:51 PM CEST Ser, Simon wrote:
> On Thu, 2019-07-11 at 10:39 +0200, Janusz Krzysztofik wrote:
> > If a child process dies for any reason while basic-fence-read or
> > basic-fence-mmap subtest is run, the subtest may hang indefinitely on
> > read() from a pipe which is supposed to be written to by that child
> > (can
> > be interrupted though). Fix it by first closing unused pipe ends on
> > both
> > parent and child side before using the pipe, as recommended by
> > pipe(2)
> > manual page.
> >
> > Please note that due to the IGT library way of handling signals, now
> > the
> > subtests may fail with error code 141 (128 + SIGPIPE) and no usual
> > DEBUG
> > message block on stderr nor FAIL message line on stdout, however some
> > meaningful error messages will still be printed on stderr by the
> > failing
> > child processes.
> >
> > v2: resend with Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> > added
>
> You generally don't need to resend a patch just to add a R-b tag.
>
> Do you have IGT commit rights?
I don't think I have.
Thanks,
Janusz
>
> > Janusz Krzysztofik (1):
> > tests/prime_vgem: Fix broken handling of interprocess pipes
> >
> > tests/prime_vgem.c | 12 ++++++++----
> > 1 file changed, 8 insertions(+), 4 deletions(-)
> >
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2 0/1] tests/prime_vgem: Fix broken handling of interprocess pipes
2019-07-11 10:49 ` Janusz Krzysztofik
@ 2019-07-11 11:17 ` Ser, Simon
0 siblings, 0 replies; 7+ messages in thread
From: Ser, Simon @ 2019-07-11 11:17 UTC (permalink / raw)
To: janusz.krzysztofik; +Cc: igt-dev, Latvala, Petri
On Thu, 2019-07-11 at 12:49 +0200, Janusz Krzysztofik wrote:
> Hi Simon,
>
> On Thursday, July 11, 2019 12:39:51 PM CEST Ser, Simon wrote:
> > On Thu, 2019-07-11 at 10:39 +0200, Janusz Krzysztofik wrote:
> > > If a child process dies for any reason while basic-fence-read or
> > > basic-fence-mmap subtest is run, the subtest may hang indefinitely on
> > > read() from a pipe which is supposed to be written to by that child
> > > (can
> > > be interrupted though). Fix it by first closing unused pipe ends on
> > > both
> > > parent and child side before using the pipe, as recommended by
> > > pipe(2)
> > > manual page.
> > >
> > > Please note that due to the IGT library way of handling signals, now
> > > the
> > > subtests may fail with error code 141 (128 + SIGPIPE) and no usual
> > > DEBUG
> > > message block on stderr nor FAIL message line on stdout, however some
> > > meaningful error messages will still be printed on stderr by the
> > > failing
> > > child processes.
> > >
> > > v2: resend with Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > added
> >
> > You generally don't need to resend a patch just to add a R-b tag.
> >
> > Do you have IGT commit rights?
>
> I don't think I have.
Okay. I just pushed this commit:
To gitlab.freedesktop.org:drm/igt-gpu-tools.git
86dc48ede7c3..d7f140b5b02d master -> master
Thanks!
Next time, you can just reply to the R-b asking for the reviewer to
push the change.
> Thanks,
> Janusz
>
> > > Janusz Krzysztofik (1):
> > > tests/prime_vgem: Fix broken handling of interprocess pipes
> > >
> > > tests/prime_vgem.c | 12 ++++++++----
> > > 1 file changed, 8 insertions(+), 4 deletions(-)
> > >
>
>
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for tests/prime_vgem: Fix broken handling of interprocess pipes (rev2)
2019-07-11 8:39 [igt-dev] [PATCH i-g-t v2 0/1] tests/prime_vgem: Fix broken handling of interprocess pipes Janusz Krzysztofik
2019-07-11 8:39 ` [igt-dev] [PATCH i-g-t v2 1/1] " Janusz Krzysztofik
2019-07-11 10:39 ` [igt-dev] [PATCH i-g-t v2 0/1] " Ser, Simon
@ 2019-07-11 14:17 ` Patchwork
2019-07-12 5:47 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
3 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2019-07-11 14:17 UTC (permalink / raw)
To: Janusz Krzysztofik; +Cc: igt-dev
== Series Details ==
Series: tests/prime_vgem: Fix broken handling of interprocess pipes (rev2)
URL : https://patchwork.freedesktop.org/series/63033/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6456 -> IGTPW_3255
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/63033/revisions/2/mbox/
Known issues
------------
Here are the changes found in IGTPW_3255 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live_contexts:
- fi-skl-iommu: [PASS][1] -> [INCOMPLETE][2] ([fdo#111050])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/fi-skl-iommu/igt@i915_selftest@live_contexts.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/fi-skl-iommu/igt@i915_selftest@live_contexts.html
#### Possible fixes ####
* igt@kms_chamelium@hdmi-edid-read:
- {fi-icl-u4}: [FAIL][3] ([fdo#111045] / [fdo#111046 ]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/fi-icl-u4/igt@kms_chamelium@hdmi-edid-read.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/fi-icl-u4/igt@kms_chamelium@hdmi-edid-read.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][5] ([fdo#109485]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
- fi-kbl-7567u: [FAIL][7] ([fdo#109485]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/fi-kbl-7567u/igt@kms_chamelium@hdmi-hpd-fast.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/fi-kbl-7567u/igt@kms_chamelium@hdmi-hpd-fast.html
#### Warnings ####
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-kbl-guc: [SKIP][9] ([fdo#109271]) -> [FAIL][10] ([fdo#110829])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/fi-kbl-guc/igt@i915_pm_rpm@basic-pci-d3-state.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/fi-kbl-guc/igt@i915_pm_rpm@basic-pci-d3-state.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109485]: https://bugs.freedesktop.org/show_bug.cgi?id=109485
[fdo#110829]: https://bugs.freedesktop.org/show_bug.cgi?id=110829
[fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045
[fdo#111046 ]: https://bugs.freedesktop.org/show_bug.cgi?id=111046
[fdo#111050]: https://bugs.freedesktop.org/show_bug.cgi?id=111050
[fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
Participating hosts (52 -> 46)
------------------------------
Missing (6): fi-kbl-soraka fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus
Build changes
-------------
* IGT: IGT_5093 -> IGTPW_3255
CI_DRM_6456: 43aa8c3633274d7cf0a6dca4b8734d84d9928cf9 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3255: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/
IGT_5093: 86dc48ede7c33bf69e15f84179d2f9e5b84c179b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
* [igt-dev] ✓ Fi.CI.IGT: success for tests/prime_vgem: Fix broken handling of interprocess pipes (rev2)
2019-07-11 8:39 [igt-dev] [PATCH i-g-t v2 0/1] tests/prime_vgem: Fix broken handling of interprocess pipes Janusz Krzysztofik
` (2 preceding siblings ...)
2019-07-11 14:17 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/prime_vgem: Fix broken handling of interprocess pipes (rev2) Patchwork
@ 2019-07-12 5:47 ` Patchwork
3 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2019-07-12 5:47 UTC (permalink / raw)
To: Janusz Krzysztofik; +Cc: igt-dev
== Series Details ==
Series: tests/prime_vgem: Fix broken handling of interprocess pipes (rev2)
URL : https://patchwork.freedesktop.org/series/63033/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6456_full -> IGTPW_3255_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/63033/revisions/2/mbox/
Known issues
------------
Here are the changes found in IGTPW_3255_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_eio@in-flight-suspend:
- shard-apl: [PASS][1] -> [DMESG-WARN][2] ([fdo#108566]) +2 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-apl4/igt@gem_eio@in-flight-suspend.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-apl2/igt@gem_eio@in-flight-suspend.html
* igt@kms_cursor_crc@pipe-c-cursor-64x21-random:
- shard-apl: [PASS][3] -> [FAIL][4] ([fdo#103232])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-apl7/igt@kms_cursor_crc@pipe-c-cursor-64x21-random.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-apl5/igt@kms_cursor_crc@pipe-c-cursor-64x21-random.html
- shard-kbl: [PASS][5] -> [FAIL][6] ([fdo#103232])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-kbl7/igt@kms_cursor_crc@pipe-c-cursor-64x21-random.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-kbl2/igt@kms_cursor_crc@pipe-c-cursor-64x21-random.html
* igt@kms_frontbuffer_tracking@fbc-badstride:
- shard-iclb: [PASS][7] -> [FAIL][8] ([fdo#103167]) +4 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-iclb8/igt@kms_frontbuffer_tracking@fbc-badstride.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-badstride.html
* igt@kms_plane_lowres@pipe-a-tiling-y:
- shard-iclb: [PASS][9] -> [FAIL][10] ([fdo#103166])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-iclb5/igt@kms_plane_lowres@pipe-a-tiling-y.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-iclb6/igt@kms_plane_lowres@pipe-a-tiling-y.html
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [PASS][11] -> [SKIP][12] ([fdo#109642] / [fdo#111068])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-iclb2/igt@kms_psr2_su@frontbuffer.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-iclb7/igt@kms_psr2_su@frontbuffer.html
* igt@perf_pmu@rc6:
- shard-kbl: [PASS][13] -> [SKIP][14] ([fdo#109271])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-kbl2/igt@perf_pmu@rc6.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-kbl1/igt@perf_pmu@rc6.html
#### Possible fixes ####
* igt@gem_exec_balancer@smoke:
- shard-iclb: [SKIP][15] ([fdo#110854]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-iclb6/igt@gem_exec_balancer@smoke.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-iclb4/igt@gem_exec_balancer@smoke.html
* igt@gem_workarounds@suspend-resume-context:
- shard-apl: [DMESG-WARN][17] ([fdo#108566]) -> [PASS][18] +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-apl1/igt@gem_workarounds@suspend-resume-context.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-apl3/igt@gem_workarounds@suspend-resume-context.html
* igt@i915_pm_rpm@system-suspend:
- shard-kbl: [INCOMPLETE][19] ([fdo#103665] / [fdo#107807]) -> [PASS][20]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-kbl4/igt@i915_pm_rpm@system-suspend.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-kbl6/igt@i915_pm_rpm@system-suspend.html
* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
- shard-hsw: [FAIL][21] ([fdo#105767]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-hsw1/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-hsw2/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
* igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic:
- shard-hsw: [SKIP][23] ([fdo#109271]) -> [PASS][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-hsw2/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-hsw2/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html
- shard-glk: [FAIL][25] ([fdo#104873]) -> [PASS][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-glk3/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-glk9/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html
* igt@kms_cursor_legacy@cursor-vs-flip-toggle:
- shard-hsw: [FAIL][27] ([fdo#103355]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-hsw5/igt@kms_cursor_legacy@cursor-vs-flip-toggle.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-hsw2/igt@kms_cursor_legacy@cursor-vs-flip-toggle.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-shrfb-msflip-blt:
- shard-glk: [FAIL][29] ([fdo#103167]) -> [PASS][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-glk8/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-shrfb-msflip-blt.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-glk9/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-shrfb-msflip-blt.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-iclb: [FAIL][31] ([fdo#103167]) -> [PASS][32] +6 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-iclb8/igt@kms_frontbuffer_tracking@fbc-suspend.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [SKIP][33] ([fdo#109441]) -> [PASS][34] +1 similar issue
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-iclb1/igt@kms_psr@psr2_sprite_plane_move.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][35] ([fdo#99912]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6456/shard-apl6/igt@kms_setmode@basic.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/shard-apl6/igt@kms_setmode@basic.html
[fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103232]: https://bugs.freedesktop.org/show_bug.cgi?id=103232
[fdo#103355]: https://bugs.freedesktop.org/show_bug.cgi?id=103355
[fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
[fdo#104873]: https://bugs.freedesktop.org/show_bug.cgi?id=104873
[fdo#105767]: https://bugs.freedesktop.org/show_bug.cgi?id=105767
[fdo#107807]: https://bugs.freedesktop.org/show_bug.cgi?id=107807
[fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110854]: https://bugs.freedesktop.org/show_bug.cgi?id=110854
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912
Participating hosts (10 -> 6)
------------------------------
Missing (4): pig-skl-6260u shard-skl pig-hsw-4770r pig-glk-j5005
Build changes
-------------
* IGT: IGT_5093 -> IGTPW_3255
* Piglit: piglit_4509 -> None
CI_DRM_6456: 43aa8c3633274d7cf0a6dca4b8734d84d9928cf9 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3255: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3255/
IGT_5093: 86dc48ede7c33bf69e15f84179d2f9e5b84c179b @ 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_3255/
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2019-07-12 5:47 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-11 8:39 [igt-dev] [PATCH i-g-t v2 0/1] tests/prime_vgem: Fix broken handling of interprocess pipes Janusz Krzysztofik
2019-07-11 8:39 ` [igt-dev] [PATCH i-g-t v2 1/1] " Janusz Krzysztofik
2019-07-11 10:39 ` [igt-dev] [PATCH i-g-t v2 0/1] " Ser, Simon
2019-07-11 10:49 ` Janusz Krzysztofik
2019-07-11 11:17 ` Ser, Simon
2019-07-11 14:17 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/prime_vgem: Fix broken handling of interprocess pipes (rev2) Patchwork
2019-07-12 5:47 ` [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.