#1118963 gtk4: Please disable four more tests on sparc64

Package:
src:gtk4
Source:
src:gtk4
Submitter:
John Paul Adrian Glaubitz
Date:
2026-02-16 21:03:02 UTC
Severity:
normal
#1118963#5
Date:
2025-10-25 21:10:56 UTC
From:
To:
Hi,

the following four tests fail on sparc64 after addressing #1118780 [1]
and #1118961 [2]:


 26/755 gtk:gdk / dmabufformats                                                      ERROR            6.06s   killed by signal 5 SIGTRAP
 21/755 gtk:gdk / memorytexture                                                      ERROR            6.34s   killed by signal 5 SIGTRAP
131/755 gtk:gsk / scaling                                                            ERROR            7.13s   killed by signal 5 SIGTRAP
128/755 gtk:gsk / misc                                                               ERROR            8.37s   killed by signal 5 SIGTRAP

Can you please disable those for sparc64?

Thanks,
Adrian
#1118963#10
Date:
2025-10-27 18:21:35 UTC
From:
To:
Hi,

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

I have tried adding those tests to the ignore list in debian/rules, but so far I failed
with the syntax. Does anyone have an idea what the correct way is to ignore those four
tests on sparc64?

Adrian
#1118963#15
Date:
2025-10-27 19:32:00 UTC
From:
To:
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

Adrian
#1118963#20
Date:
2026-02-16 20:27:58 UTC
From:
To:
On Mon, Oct 27, 2025 at 3:33 PM John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:

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
#1118963#25
Date:
2026-02-16 20:36:39 UTC
From:
To:
Hello Jeremy,

Oracle ships Gtk on Oracle Solaris for SPARC and Gtk applications worked
fine last time I tested them on my Powerbook G4, so I have no doubt that
Gtk actually works on these platforms.

However, I can test the gtk4-demo package if you let me know what to test.

Adrian
#1118963#30
Date:
2026-02-16 21:00:24 UTC
From:
To:
Control: reopen 1081952

I think selecting Application Class in the gtk4-demo app and clicking
Run and then clicking around the UI is a good start.

That particular demo is broken in 4.21.5 but works in earlier
versions. I just reported that issue upstream.

Thank you,
Jeremy Bícha