Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/9] drm/i915: Expose 10:10:10 XRGB formats on SNB-BDW sprites (rev2)
On Tue, Oct 15, 2019 at 12:25:59PM +0300, Petri Latvala wrote: > On Tue, Oct 15, 2019 at 09:41:20AM +0300, Arkadiusz Hiler wrote: > > On Mon, Oct 14, 2019 at 10:23:42PM +0300, Ville Syrjälä wrote: > > > On Wed, Oct 09, 2019 at 09:12:23PM -, Patchwork wrote: > > > > == Series Details == > > > > > > > > Series: series starting with [1/9] drm/i915: Expose 10:10:10 XRGB > > > > formats on SNB-BDW sprites (rev2) > > > > URL : https://patchwork.freedesktop.org/series/67741/ > > > > State : failure > > > > > > > > == Summary == > > > > > > > > CI Bug Log - changes from CI_DRM_7042_full -> Patchwork_14725_full > > > > > > > > > > > > Summary > > > > --- > > > > > > > > **FAILURE** > > > > > > > > Serious unknown changes coming with Patchwork_14725_full absolutely > > > > need to be > > > > verified manually. > > > > > > > > If you think the reported changes have nothing to do with the changes > > > > introduced in Patchwork_14725_full, please notify your bug team to > > > > allow them > > > > to document this new failure mode, which will reduce false positives > > > > in CI. > > > > > > > > > > > > > > > > Possible new issues > > > > --- > > > > > > > > Here are the unknown changes that may have been introduced in > > > > Patchwork_14725_full: > > > > > > > > ### IGT changes ### > > > > > > > > Possible regressions > > > > > > > > * igt@gem_eio@in-flight-1us: > > > > - shard-snb: [PASS][1] -> [FAIL][2] > > > >[1]: > > > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-snb7/igt@gem_...@in-flight-1us.html > > > >[2]: > > > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-snb7/igt@gem_...@in-flight-1us.html > > > > > > > > * igt@kms_plane@pixel-format-pipe-a-planes: > > > > - shard-iclb: [PASS][3] -> [FAIL][4] +13 similar issues > > > >[3]: > > > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-iclb7/igt@kms_pl...@pixel-format-pipe-a-planes.html > > > >[4]: > > > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-iclb8/igt@kms_pl...@pixel-format-pipe-a-planes.html > > > > > > IGT-Version: 1.24-ge501741f > > > ... > > > Testing format AR30(0x30335241) / modifier 0x103 on A.0 > > > (kms_plane:1411) igt_fb-CRITICAL: Conversion not implemented (from format > > > 0x30335241 to 0x78464749) > > > > > > DRM_FORMAT_ARGB2101010 = 0x30335241 > > > IGT_FORMAT_FLOAT = 0x78464749 > > > > > > { .name = "ARGB2101010", .depth = 30, .drm_id = DRM_FORMAT_ARGB2101010, > > > .pixman_id = PIXMAN_a2r10g10b10, > > > > > > { .name = "IGT-FLOAT", .depth = -1, .drm_id = IGT_FORMAT_FLOAT, > > > .pixman_id = PIXMAN_rgba_float, > > > > > > if ((drm_format_to_pixman(cvt->src.fb->drm_format) != PIXMAN_invalid) && > > > (drm_format_to_pixman(cvt->dst.fb->drm_format) != PIXMAN_invalid)) { > > > cnvert_pixman(cvt); > > > return; > > > ... > > > igt_assert_f(false, "Conversion not implemented ...); > > > > > > So wtf? > > > > > > Are we somehow compiling igt with an old pixman causing > > > #if PIXMAN_VERSION < PIXMAN_VERSION_ENCODE(0, 36, 0) > > > #define PIXMAN_rgba_float PIXMAN_invalid > > > #endif > > > to happen? > > > > oof, seems like the building machine got downgraded somehow > > > > ci-worker1:~$ dpkg -l '*pixman*' > > Desired=Unknown/Install/Remove/Purge/Hold > > | > > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > > ||/ NameVersion > > Architecture Description > > +++-===---=== > > ii libpixman-1-0:amd64 0.34.0-2 > > amd64pixel-manipulation library for X and cairo > > ii libpixman-1-dev:amd64 0.34.0-2 > > amd64pixel-manipulation library for X and > > cairo (development files) > > > > that's bad... > > > > > But the reference run shows it testing all the fancy YUV formats so > > > I don't think that can be the case. > > > > That's the weird bit... > > > > Anyway the building machine needs updating and apt-mark hold. > > This can cause fallout and we need to file bugs to limit the noise. > > > > There is quite some queue right now, but hopefully by tomorrow it will > > be drained. I'll do the necessary updates and force IGT run to see what > > is going to happen in the morning. Then I'll rerun this series. > > > > > I don't think the builder ever had a higher version. > > The fancy YUV formats work because the runtime lib is new enough, and > the build-time
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/9] drm/i915: Expose 10:10:10 XRGB formats on SNB-BDW sprites (rev2)
On Tue, Oct 15, 2019 at 12:25:59PM +0300, Petri Latvala wrote: > On Tue, Oct 15, 2019 at 09:41:20AM +0300, Arkadiusz Hiler wrote: > > On Mon, Oct 14, 2019 at 10:23:42PM +0300, Ville Syrjälä wrote: > > > On Wed, Oct 09, 2019 at 09:12:23PM -, Patchwork wrote: > > > > == Series Details == > > > > > > > > Series: series starting with [1/9] drm/i915: Expose 10:10:10 XRGB > > > > formats on SNB-BDW sprites (rev2) > > > > URL : https://patchwork.freedesktop.org/series/67741/ > > > > State : failure > > > > > > > > == Summary == > > > > > > > > CI Bug Log - changes from CI_DRM_7042_full -> Patchwork_14725_full > > > > > > > > > > > > Summary > > > > --- > > > > > > > > **FAILURE** > > > > > > > > Serious unknown changes coming with Patchwork_14725_full absolutely > > > > need to be > > > > verified manually. > > > > > > > > If you think the reported changes have nothing to do with the changes > > > > introduced in Patchwork_14725_full, please notify your bug team to > > > > allow them > > > > to document this new failure mode, which will reduce false positives > > > > in CI. > > > > > > > > > > > > > > > > Possible new issues > > > > --- > > > > > > > > Here are the unknown changes that may have been introduced in > > > > Patchwork_14725_full: > > > > > > > > ### IGT changes ### > > > > > > > > Possible regressions > > > > > > > > * igt@gem_eio@in-flight-1us: > > > > - shard-snb: [PASS][1] -> [FAIL][2] > > > >[1]: > > > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-snb7/igt@gem_...@in-flight-1us.html > > > >[2]: > > > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-snb7/igt@gem_...@in-flight-1us.html > > > > > > > > * igt@kms_plane@pixel-format-pipe-a-planes: > > > > - shard-iclb: [PASS][3] -> [FAIL][4] +13 similar issues > > > >[3]: > > > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-iclb7/igt@kms_pl...@pixel-format-pipe-a-planes.html > > > >[4]: > > > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-iclb8/igt@kms_pl...@pixel-format-pipe-a-planes.html > > > > > > IGT-Version: 1.24-ge501741f > > > ... > > > Testing format AR30(0x30335241) / modifier 0x103 on A.0 > > > (kms_plane:1411) igt_fb-CRITICAL: Conversion not implemented (from format > > > 0x30335241 to 0x78464749) > > > > > > DRM_FORMAT_ARGB2101010 = 0x30335241 > > > IGT_FORMAT_FLOAT = 0x78464749 > > > > > > { .name = "ARGB2101010", .depth = 30, .drm_id = DRM_FORMAT_ARGB2101010, > > > .pixman_id = PIXMAN_a2r10g10b10, > > > > > > { .name = "IGT-FLOAT", .depth = -1, .drm_id = IGT_FORMAT_FLOAT, > > > .pixman_id = PIXMAN_rgba_float, > > > > > > if ((drm_format_to_pixman(cvt->src.fb->drm_format) != PIXMAN_invalid) && > > > (drm_format_to_pixman(cvt->dst.fb->drm_format) != PIXMAN_invalid)) { > > > cnvert_pixman(cvt); > > > return; > > > ... > > > igt_assert_f(false, "Conversion not implemented ...); > > > > > > So wtf? > > > > > > Are we somehow compiling igt with an old pixman causing > > > #if PIXMAN_VERSION < PIXMAN_VERSION_ENCODE(0, 36, 0) > > > #define PIXMAN_rgba_float PIXMAN_invalid > > > #endif > > > to happen? > > > > oof, seems like the building machine got downgraded somehow > > > > ci-worker1:~$ dpkg -l '*pixman*' > > Desired=Unknown/Install/Remove/Purge/Hold > > | > > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > > ||/ NameVersion > > Architecture Description > > +++-===---=== > > ii libpixman-1-0:amd64 0.34.0-2 > > amd64pixel-manipulation library for X and cairo > > ii libpixman-1-dev:amd64 0.34.0-2 > > amd64pixel-manipulation library for X and > > cairo (development files) > > > > that's bad... > > > > > But the reference run shows it testing all the fancy YUV formats so > > > I don't think that can be the case. > > > > That's the weird bit... > > > > Anyway the building machine needs updating and apt-mark hold. > > This can cause fallout and we need to file bugs to limit the noise. > > > > There is quite some queue right now, but hopefully by tomorrow it will > > be drained. I'll do the necessary updates and force IGT run to see what > > is going to happen in the morning. Then I'll rerun this series. > > > > > I don't think the builder ever had a higher version. > > The fancy YUV formats work because the runtime lib is new enough, and > the build-time
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/9] drm/i915: Expose 10:10:10 XRGB formats on SNB-BDW sprites (rev2)
On Tue, Oct 15, 2019 at 09:41:20AM +0300, Arkadiusz Hiler wrote: > On Mon, Oct 14, 2019 at 10:23:42PM +0300, Ville Syrjälä wrote: > > On Wed, Oct 09, 2019 at 09:12:23PM -, Patchwork wrote: > > > == Series Details == > > > > > > Series: series starting with [1/9] drm/i915: Expose 10:10:10 XRGB formats > > > on SNB-BDW sprites (rev2) > > > URL : https://patchwork.freedesktop.org/series/67741/ > > > State : failure > > > > > > == Summary == > > > > > > CI Bug Log - changes from CI_DRM_7042_full -> Patchwork_14725_full > > > > > > > > > Summary > > > --- > > > > > > **FAILURE** > > > > > > Serious unknown changes coming with Patchwork_14725_full absolutely > > > need to be > > > verified manually. > > > > > > If you think the reported changes have nothing to do with the changes > > > introduced in Patchwork_14725_full, please notify your bug team to > > > allow them > > > to document this new failure mode, which will reduce false positives in > > > CI. > > > > > > > > > > > > Possible new issues > > > --- > > > > > > Here are the unknown changes that may have been introduced in > > > Patchwork_14725_full: > > > > > > ### IGT changes ### > > > > > > Possible regressions > > > > > > * igt@gem_eio@in-flight-1us: > > > - shard-snb: [PASS][1] -> [FAIL][2] > > >[1]: > > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-snb7/igt@gem_...@in-flight-1us.html > > >[2]: > > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-snb7/igt@gem_...@in-flight-1us.html > > > > > > * igt@kms_plane@pixel-format-pipe-a-planes: > > > - shard-iclb: [PASS][3] -> [FAIL][4] +13 similar issues > > >[3]: > > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-iclb7/igt@kms_pl...@pixel-format-pipe-a-planes.html > > >[4]: > > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-iclb8/igt@kms_pl...@pixel-format-pipe-a-planes.html > > > > IGT-Version: 1.24-ge501741f > > ... > > Testing format AR30(0x30335241) / modifier 0x103 on A.0 > > (kms_plane:1411) igt_fb-CRITICAL: Conversion not implemented (from format > > 0x30335241 to 0x78464749) > > > > DRM_FORMAT_ARGB2101010 = 0x30335241 > > IGT_FORMAT_FLOAT = 0x78464749 > > > > { .name = "ARGB2101010", .depth = 30, .drm_id = DRM_FORMAT_ARGB2101010, > > .pixman_id = PIXMAN_a2r10g10b10, > > > > { .name = "IGT-FLOAT", .depth = -1, .drm_id = IGT_FORMAT_FLOAT, > > .pixman_id = PIXMAN_rgba_float, > > > > if ((drm_format_to_pixman(cvt->src.fb->drm_format) != PIXMAN_invalid) && > > (drm_format_to_pixman(cvt->dst.fb->drm_format) != PIXMAN_invalid)) { > > cnvert_pixman(cvt); > > return; > > ... > > igt_assert_f(false, "Conversion not implemented ...); > > > > So wtf? > > > > Are we somehow compiling igt with an old pixman causing > > #if PIXMAN_VERSION < PIXMAN_VERSION_ENCODE(0, 36, 0) > > #define PIXMAN_rgba_float PIXMAN_invalid > > #endif > > to happen? > > oof, seems like the building machine got downgraded somehow > > ci-worker1:~$ dpkg -l '*pixman*' > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ NameVersion >Architecture Description > +++-===---=== > ii libpixman-1-0:amd64 0.34.0-2 >amd64pixel-manipulation library for X and cairo > ii libpixman-1-dev:amd64 0.34.0-2 >amd64pixel-manipulation library for X and cairo > (development files) > > that's bad... > > > But the reference run shows it testing all the fancy YUV formats so > > I don't think that can be the case. > > That's the weird bit... > > Anyway the building machine needs updating and apt-mark hold. > This can cause fallout and we need to file bugs to limit the noise. > > There is quite some queue right now, but hopefully by tomorrow it will > be drained. I'll do the necessary updates and force IGT run to see what > is going to happen in the morning. Then I'll rerun this series. > I don't think the builder ever had a higher version. The fancy YUV formats work because the runtime lib is new enough, and the build-time checks for those are as such: #if CAIRO_VERSION < CAIRO_VERSION_ENCODE(1, 17, 2) /* * We need cairo 1.17.2 to use HDR formats, but the only thing added is a value * to cairo_format_t. * * To prevent going outside the enum, make cairo_format_t an int and define * ourselves. */ #define
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/9] drm/i915: Expose 10:10:10 XRGB formats on SNB-BDW sprites (rev2)
On Mon, Oct 14, 2019 at 10:23:42PM +0300, Ville Syrjälä wrote: > On Wed, Oct 09, 2019 at 09:12:23PM -, Patchwork wrote: > > == Series Details == > > > > Series: series starting with [1/9] drm/i915: Expose 10:10:10 XRGB formats > > on SNB-BDW sprites (rev2) > > URL : https://patchwork.freedesktop.org/series/67741/ > > State : failure > > > > == Summary == > > > > CI Bug Log - changes from CI_DRM_7042_full -> Patchwork_14725_full > > > > > > Summary > > --- > > > > **FAILURE** > > > > Serious unknown changes coming with Patchwork_14725_full absolutely need > > to be > > verified manually. > > > > If you think the reported changes have nothing to do with the changes > > introduced in Patchwork_14725_full, please notify your bug team to allow > > them > > to document this new failure mode, which will reduce false positives in > > CI. > > > > > > > > Possible new issues > > --- > > > > Here are the unknown changes that may have been introduced in > > Patchwork_14725_full: > > > > ### IGT changes ### > > > > Possible regressions > > > > * igt@gem_eio@in-flight-1us: > > - shard-snb: [PASS][1] -> [FAIL][2] > >[1]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-snb7/igt@gem_...@in-flight-1us.html > >[2]: > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-snb7/igt@gem_...@in-flight-1us.html > > > > * igt@kms_plane@pixel-format-pipe-a-planes: > > - shard-iclb: [PASS][3] -> [FAIL][4] +13 similar issues > >[3]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-iclb7/igt@kms_pl...@pixel-format-pipe-a-planes.html > >[4]: > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-iclb8/igt@kms_pl...@pixel-format-pipe-a-planes.html > > IGT-Version: 1.24-ge501741f > ... > Testing format AR30(0x30335241) / modifier 0x103 on A.0 > (kms_plane:1411) igt_fb-CRITICAL: Conversion not implemented (from format > 0x30335241 to 0x78464749) > > DRM_FORMAT_ARGB2101010 = 0x30335241 > IGT_FORMAT_FLOAT = 0x78464749 > > { .name = "ARGB2101010", .depth = 30, .drm_id = DRM_FORMAT_ARGB2101010, > .pixman_id = PIXMAN_a2r10g10b10, > > { .name = "IGT-FLOAT", .depth = -1, .drm_id = IGT_FORMAT_FLOAT, > .pixman_id = PIXMAN_rgba_float, > > if ((drm_format_to_pixman(cvt->src.fb->drm_format) != PIXMAN_invalid) && > (drm_format_to_pixman(cvt->dst.fb->drm_format) != PIXMAN_invalid)) { > cnvert_pixman(cvt); > return; > ... > igt_assert_f(false, "Conversion not implemented ...); > > So wtf? > > Are we somehow compiling igt with an old pixman causing > #if PIXMAN_VERSION < PIXMAN_VERSION_ENCODE(0, 36, 0) > #define PIXMAN_rgba_float PIXMAN_invalid > #endif > to happen? oof, seems like the building machine got downgraded somehow ci-worker1:~$ dpkg -l '*pixman*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ii libpixman-1-0:amd64 0.34.0-2 amd64pixel-manipulation library for X and cairo ii libpixman-1-dev:amd64 0.34.0-2 amd64pixel-manipulation library for X and cairo (development files) that's bad... > But the reference run shows it testing all the fancy YUV formats so > I don't think that can be the case. That's the weird bit... Anyway the building machine needs updating and apt-mark hold. This can cause fallout and we need to file bugs to limit the noise. There is quite some queue right now, but hopefully by tomorrow it will be drained. I'll do the necessary updates and force IGT run to see what is going to happen in the morning. Then I'll rerun this series. -- Cheers, Arek ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/9] drm/i915: Expose 10:10:10 XRGB formats on SNB-BDW sprites (rev2)
Quoting Ville Syrjälä (2019-10-14 20:23:42) > On Wed, Oct 09, 2019 at 09:12:23PM -, Patchwork wrote: > > == Series Details == > > > > Series: series starting with [1/9] drm/i915: Expose 10:10:10 XRGB formats > > on SNB-BDW sprites (rev2) > > URL : https://patchwork.freedesktop.org/series/67741/ > > State : failure > > > > == Summary == > > > > CI Bug Log - changes from CI_DRM_7042_full -> Patchwork_14725_full > > > > > > Summary > > --- > > > > **FAILURE** > > > > Serious unknown changes coming with Patchwork_14725_full absolutely need > > to be > > verified manually. > > > > If you think the reported changes have nothing to do with the changes > > introduced in Patchwork_14725_full, please notify your bug team to allow > > them > > to document this new failure mode, which will reduce false positives in > > CI. > > > > > > > > Possible new issues > > --- > > > > Here are the unknown changes that may have been introduced in > > Patchwork_14725_full: > > > > ### IGT changes ### > > > > Possible regressions > > > > * igt@gem_eio@in-flight-1us: > > - shard-snb: [PASS][1] -> [FAIL][2] > >[1]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-snb7/igt@gem_...@in-flight-1us.html > >[2]: > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-snb7/igt@gem_...@in-flight-1us.html > > > > * igt@kms_plane@pixel-format-pipe-a-planes: > > - shard-iclb: [PASS][3] -> [FAIL][4] +13 similar issues > >[3]: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-iclb7/igt@kms_pl...@pixel-format-pipe-a-planes.html > >[4]: > > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-iclb8/igt@kms_pl...@pixel-format-pipe-a-planes.html > > IGT-Version: 1.24-ge501741f > ... > Testing format AR30(0x30335241) / modifier 0x103 on A.0 > (kms_plane:1411) igt_fb-CRITICAL: Conversion not implemented (from format > 0x30335241 to 0x78464749) > > DRM_FORMAT_ARGB2101010 = 0x30335241 > IGT_FORMAT_FLOAT = 0x78464749 > > { .name = "ARGB2101010", .depth = 30, .drm_id = DRM_FORMAT_ARGB2101010, > .pixman_id = PIXMAN_a2r10g10b10, > > { .name = "IGT-FLOAT", .depth = -1, .drm_id = IGT_FORMAT_FLOAT, > .pixman_id = PIXMAN_rgba_float, > > if ((drm_format_to_pixman(cvt->src.fb->drm_format) != PIXMAN_invalid) && > (drm_format_to_pixman(cvt->dst.fb->drm_format) != PIXMAN_invalid)) { > cnvert_pixman(cvt); > return; > ... > igt_assert_f(false, "Conversion not implemented ...); > > So wtf? > > Are we somehow compiling igt with an old pixman causing > #if PIXMAN_VERSION < PIXMAN_VERSION_ENCODE(0, 36, 0) > #define PIXMAN_rgba_float PIXMAN_invalid > #endif > to happen? That's the only way I can see, perhaps stick a #warn in there. -Chris ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/9] drm/i915: Expose 10:10:10 XRGB formats on SNB-BDW sprites (rev2)
On Wed, Oct 09, 2019 at 09:12:23PM -, Patchwork wrote: > == Series Details == > > Series: series starting with [1/9] drm/i915: Expose 10:10:10 XRGB formats on > SNB-BDW sprites (rev2) > URL : https://patchwork.freedesktop.org/series/67741/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_7042_full -> Patchwork_14725_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_14725_full absolutely need to > be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_14725_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_14725_full: > > ### IGT changes ### > > Possible regressions > > * igt@gem_eio@in-flight-1us: > - shard-snb: [PASS][1] -> [FAIL][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-snb7/igt@gem_...@in-flight-1us.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-snb7/igt@gem_...@in-flight-1us.html > > * igt@kms_plane@pixel-format-pipe-a-planes: > - shard-iclb: [PASS][3] -> [FAIL][4] +13 similar issues >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-iclb7/igt@kms_pl...@pixel-format-pipe-a-planes.html >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-iclb8/igt@kms_pl...@pixel-format-pipe-a-planes.html IGT-Version: 1.24-ge501741f ... Testing format AR30(0x30335241) / modifier 0x103 on A.0 (kms_plane:1411) igt_fb-CRITICAL: Conversion not implemented (from format 0x30335241 to 0x78464749) DRM_FORMAT_ARGB2101010 = 0x30335241 IGT_FORMAT_FLOAT = 0x78464749 { .name = "ARGB2101010", .depth = 30, .drm_id = DRM_FORMAT_ARGB2101010, .pixman_id = PIXMAN_a2r10g10b10, { .name = "IGT-FLOAT", .depth = -1, .drm_id = IGT_FORMAT_FLOAT, .pixman_id = PIXMAN_rgba_float, if ((drm_format_to_pixman(cvt->src.fb->drm_format) != PIXMAN_invalid) && (drm_format_to_pixman(cvt->dst.fb->drm_format) != PIXMAN_invalid)) { cnvert_pixman(cvt); return; ... igt_assert_f(false, "Conversion not implemented ...); So wtf? Are we somehow compiling igt with an old pixman causing #if PIXMAN_VERSION < PIXMAN_VERSION_ENCODE(0, 36, 0) #define PIXMAN_rgba_float PIXMAN_invalid #endif to happen? But the reference run shows it testing all the fancy YUV formats so I don't think that can be the case. And my CHV can run this test with ARGB2101010 just fine so the code can't be totally broken. -- Ville Syrjälä Intel ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/9] drm/i915: Expose 10:10:10 XRGB formats on SNB-BDW sprites (rev2)
== Series Details == Series: series starting with [1/9] drm/i915: Expose 10:10:10 XRGB formats on SNB-BDW sprites (rev2) URL : https://patchwork.freedesktop.org/series/67741/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7042_full -> Patchwork_14725_full Summary --- **FAILURE** Serious unknown changes coming with Patchwork_14725_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_14725_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Possible new issues --- Here are the unknown changes that may have been introduced in Patchwork_14725_full: ### IGT changes ### Possible regressions * igt@gem_eio@in-flight-1us: - shard-snb: [PASS][1] -> [FAIL][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-snb7/igt@gem_...@in-flight-1us.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-snb7/igt@gem_...@in-flight-1us.html * igt@kms_plane@pixel-format-pipe-a-planes: - shard-iclb: [PASS][3] -> [FAIL][4] +13 similar issues [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-iclb7/igt@kms_pl...@pixel-format-pipe-a-planes.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-iclb8/igt@kms_pl...@pixel-format-pipe-a-planes.html Suppressed The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * igt@kms_plane@pixel-format-pipe-a-planes: - {shard-tglb}: [PASS][5] -> [FAIL][6] +1 similar issue [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-tglb7/igt@kms_pl...@pixel-format-pipe-a-planes.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-tglb6/igt@kms_pl...@pixel-format-pipe-a-planes.html * igt@kms_plane@pixel-format-pipe-c-planes: - {shard-tglb}: NOTRUN -> [FAIL][7] +2 similar issues [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-tglb1/igt@kms_pl...@pixel-format-pipe-c-planes.html Known issues Here are the changes found in Patchwork_14725_full that come from known issues: ### IGT changes ### Issues hit * igt@gem_eio@in-flight-contexts-immediate: - shard-snb: [PASS][8] -> [FAIL][9] ([fdo#111925]) [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-snb1/igt@gem_...@in-flight-contexts-immediate.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-snb2/igt@gem_...@in-flight-contexts-immediate.html * igt@gem_exec_schedule@promotion-bsd1: - shard-iclb: [PASS][10] -> [SKIP][11] ([fdo#109276]) +11 similar issues [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-iclb2/igt@gem_exec_sched...@promotion-bsd1.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-iclb7/igt@gem_exec_sched...@promotion-bsd1.html * igt@gem_exec_schedule@reorder-wide-bsd: - shard-iclb: [PASS][12] -> [SKIP][13] ([fdo#111325]) +1 similar issue [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-iclb3/igt@gem_exec_sched...@reorder-wide-bsd.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-iclb4/igt@gem_exec_sched...@reorder-wide-bsd.html * igt@gem_tiled_swapping@non-threaded: - shard-glk: [PASS][14] -> [INCOMPLETE][15] ([fdo#103359] / [fdo#108686] / [k.org#198133]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-glk8/igt@gem_tiled_swapp...@non-threaded.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-glk8/igt@gem_tiled_swapp...@non-threaded.html * igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy: - shard-snb: [PASS][16] -> [DMESG-WARN][17] ([fdo#111870]) +1 similar issue [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-snb4/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-snb5/igt@gem_userptr_bl...@map-fixed-invalidate-overlap-busy.html * igt@gem_userptr_blits@sync-unmap-after-close: - shard-hsw: [PASS][18] -> [DMESG-WARN][19] ([fdo#111870]) +2 similar issues [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-hsw8/igt@gem_userptr_bl...@sync-unmap-after-close.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14725/shard-hsw2/igt@gem_userptr_bl...@sync-unmap-after-close.html * igt@gem_workarounds@suspend-resume-context: - shard-apl: [PASS][20] -> [DMESG-WARN][21] ([fdo#108566]) +5 similar issues [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7042/shard-apl1/igt@gem_workarou...@suspend-resume-context.html [21]: