Bug#1118963: gtk4: Please disable four more tests on sparc64
Jeremy Bícha
jbicha at debian.org
Mon Feb 16 20:27:58 GMT 2026
On Mon, Oct 27, 2025 at 3:33 PM John Paul Adrian Glaubitz
<glaubitz at physik.fu-berlin.de> wrote:
> On Mon, 2025-10-27 at 19:21 +0100, John Paul Adrian Glaubitz wrote:
> > After the last changes, the failures on sparc64 are actually now down to [1]:
> >
> > Summary of Failures:
> >
> > 26/755 gtk:gdk / dmabufformats ERROR 3.28s killed by signal 5 SIGTRAP
> > 21/755 gtk:gdk / memorytexture ERROR 3.58s killed by signal 5 SIGTRAP
> > 131/755 gtk:gsk / scaling ERROR 3.36s killed by signal 5 SIGTRAP
> > 128/755 gtk:gsk / misc ERROR 3.82s killed by signal 5 SIGTRAP
> >
> > Ok: 723
> > Fail: 4
> > Skipped: 28
>
> And we need to disable those tests plus another one on powerpc as well:
>
> Summary of Failures:
>
> 26/755 gtk:gdk / dmabufformats ERROR 4.57s killed by signal 5 SIGTRAP
> 21/755 gtk:gdk / memorytexture ERROR 5.05s killed by signal 5 SIGTRAP
> 131/755 gtk:gsk / scaling ERROR 5.31s killed by signal 5 SIGTRAP
> 128/755 gtk:gsk / misc ERROR 5.45s killed by signal 5 SIGTRAP
> 178/755 gtk:gtk / sorter ERROR 4.37s killed by signal 6 SIGABRT
Sorry for the delay responding. I think what the Debian GNOME team
would like to see before skipping additional tests is some assurance
that gtk4 actually works well on these platforms. None of us have
access to a physical machine for these ports. If you have access to a
machine like that, could you confirm that gtk4 is working despite
these bugs? There is a binary package gtk-4-examples that install
gtk4-demo you can use to manually test a wide variety of gtk4 UI
elements.
Alternatively, and I know it's a lot of work, but someone could
identify and fix the code (or the tests) to correct the assumption
that isn't true for these architectures.
Thank you,
Jeremy Bícha
More information about the pkg-gnome-maintainers
mailing list