Created attachment 866932 [details] build.log (ppc, 1.76.0) I know it looks a bit similar to bug #882071 but at least the LegacyByteArray looks ppc specific. But feel free to close it as a dupe if it happens to be a dupe. ;) [...] Summary of Failures: 33/71 gjs:JS / LegacyByteArray ERROR 0.78s killed by signal 6 SIGABRT 16/71 gjs:JS / GIMarshalling ERROR 1.30s killed by signal 6 SIGABRT 66/71 gjs:JS / Regress ERROR 1.33s killed by signal 6 SIGABRT Ok: 68 Expected Fail: 0 Fail: 3 Unexpected Pass: 0 Skipped: 0 Timeout: 0 Full log written to /var/tmp/portage/dev-libs/gjs-1.76.0/work/gjs-1.76.0-build/meson-logs/testlog.txt * ERROR: dev-libs/gjs-1.76.0::gentoo failed (test phase): * tests failed
Created attachment 866933 [details] testlog.txt
Created attachment 866934 [details] emerge --info
The fix to bug 882071 ended up being in libffi. I wonder if ppc suffers from a similar typo...
not ok 185 GByteArray marshals as a return value # Message: Expected $['0'] = 0 to equal 241. # Expected $['1'] = 49 to equal 214. # Expected $['2'] = 255 to equal 160. # Expected $['3'] = 51 to equal 32. # Stack: # error properties: Object({ matches: Function }) # <Jasmine> # testReturnValue/<@/var/tmp/portage/dev-libs/gjs-1.76.0/work/gjs-1.76.0-build/../gjs-1.76.0/installed-tests/js/testGIMarshalling.js:31:48 # <Jasmine> # setTimeout/source<@resource:///org/gnome/gjs/modules/esm/_timers.js:72:9 # _init/GLib.MainLoop.prototype.runAsync/</<@resource:///org/gnome/gjs/modules/core/overrides/GLib.js:266:34 Bail out! ERROR:/usr/share/gobject-introspection-1.0/tests/gimarshallingtests.c:2520:gi_marshalling_tests_bytearray_none_in: assertion failed (g_array_index (v, unsigned char, 0) == 0): (241 == 0) ----------------------------------- stderr ----------------------------------- ** ERROR:/usr/share/gobject-introspection-1.0/tests/gimarshallingtests.c:2520:gi_marshalling_tests_bytearray_none_in: assertion failed (g_array_index (v, unsigned char, 0) == 0): (241 == 0)
Does the libffi test suite pass for you?
Created attachment 884878 [details] libffi test suite Yes, ffi test suite passes here.
(In reply to Sam James from comment #5) > Does the libffi test suite pass for you? I can confirm libffi-3.4.4-r3 passes tests on ppc.
Created attachment 884963 [details] build.log (ppc, 1.78.3) Same for 1.78.3.
Created attachment 884964 [details] testlog.txt (ppc, 1.78.3)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c80fffe24fc41c75d0e69633dc0c04f4274fa47c commit c80fffe24fc41c75d0e69633dc0c04f4274fa47c Author: Sam James <sam@gentoo.org> AuthorDate: 2024-02-15 14:18:44 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-02-15 14:19:07 +0000 dev-libs/libffi: add 3.4.5 Includes the fixes for bug #882071 (which we already backported) and possible fixes for bug #911649. Bug: https://bugs.gentoo.org/882071 Bug: https://bugs.gentoo.org/911649 Signed-off-by: Sam James <sam@gentoo.org> dev-libs/libffi/Manifest | 1 + dev-libs/libffi/libffi-3.4.5.ebuild | 73 +++++++++++++++++++++++++++++++++++++ 2 files changed, 74 insertions(+)
libffi-3.4.5 does not make a difference for ppc test failures on gjs-1.76.0 or gjs-1.78.3. Still: Summary of Failures: 17/72 gjs:JS / LegacyByteArray ERROR 0.52s killed by signal 6 SIGABRT 23/72 gjs:JS / GIMarshalling ERROR 1.28s killed by signal 6 SIGABRT 54/72 gjs:JS / Regress ERROR 1.30s killed by signal 6 SIGABRT Ok: 69 Expected Fail: 0 Fail: 3 Unexpected Pass: 0 Skipped: 0 Timeout: 0
