Hello,
On Mon, 2024-09-16 at 16:08 +0100, Simon McVittie wrote:
I don't know whether this is a bug in the test, or a bug in the part
of
GTK that is being tested. It might be a problem with pointers or
varargs
or something (powerpc is 32-bit big-endian, which is unusual these
days).
The same test fails on hppa, which I think might also be 32-bit
big-endian?
Yes, both hppa and powerpc are 32-bit big-endian.
That test does succeed on ppc64 and s390x, which are 64-bit
big-endian.
The Debian GNOME team is unlikely to prioritize investigating this,
because our focus is the release architectures where GNOME is most
commonly used, but tested patches (ideally sent upstream) would be
appreciated.
I think we should just ignore this test for now. There are currently 5
tests
in total failing on powerpc and we should ignore all of those:
Summary of Failures:
26/755 gtk:gdk / dmabufformats
ERROR 0.25s killed by signal 5 SIGTRAP
21/755 gtk:gdk / memorytexture
ERROR 1.32s killed by signal 5 SIGTRAP
131/755 gtk:gsk / scaling
ERROR 0.26s killed by signal 5 SIGTRAP
128/755 gtk:gsk / misc
ERROR 0.97s killed by signal 5 SIGTRAP
178/755 gtk:gtk / sorter
ERROR 0.10s killed by signal 6 SIGABRT
Ok: 722
Fail: 5
Skipped: 28
I have been trying to figure out how to skip those, but I have not been
able
to figure out the mechanism behind that and no matter what I try, the
tests
are still run.
Anyone got any idea?
Adrian
[1]
https://buildd.debian.org/status/fetch.php?pkg=gtk4&arch=powerpc&ver=4.20.2%2Bds-2&stamp=1761591976&raw=0