[debian-mysql] Bug#970041: galera-4: FTBFS on sparc64: Received signal 10 (Bus error)

[Otto Kekäläinen]

Source: galera-4
Version: 26.4.5-1
Severity: normal
Justification: unofficial architecture
User: debian-ia64 at lists.debian.org
Usertags: sparc64
Forwarded: https://github.com/codership/galera/issues/558

The sparc64 build at
https://buildd.debian.org/status/fetch.php?pkg=galera-4&arch=sparc64&ver=26.4.5-1&stamp=1593565379&raw=0
failed with

*******
Running suite(s): DataSet
0%: Checks: 2, Failures: 0, Errors: 2
galera/tests/data_set_check.cpp:243:E:DataSet:ver1:0: (after this
point) Received signal 10 (Bus error)
galera/tests/data_set_check.cpp:143:E:DataSet:ver2:0: (after this
point) Received signal 10 (Bus error)
Running suite(s): KeySet
0%: Checks: 4, Failures: 0, Errors: 4
galera/tests/key_set_check.cpp:54:E:KeySet:ver1_3:0: (after this
point) Received signal 10 (Bus error)
galera/tests/key_set_check.cpp:235:E:KeySet:ver2_3:0: (after this
point) Received signal 10 (Bus error)
galera/tests/key_set_check.cpp:235:E:KeySet:ver2_4:0: (after this
point) Received signal 10 (Bus error)
galera/tests/key_set_check.cpp:235:E:KeySet:ver2_5:0: (after this
point) Received signal 10 (Bus error)
Running suite(s): WriteSet
60%: Checks: 5, Failures: 0, Errors: 2
galera/tests/write_set_ng_check.cpp:83:E:WriteSet
basic:ver3_basic_rsv1:0: (after this point) Received signal 10 (Bus
error)
galera/tests/write_set_ng_check.cpp:307:E:WriteSet
annotation:ver3_annotation_rsv1:0: (after this point) Received signal
10 (Bus error)
Running suite(s): certification
100%: Checks: 5, Failures: 0, Errors: 0
Running suite(s): trx_handle
100%: Checks: 4, Failures: 0, Errors: 0
Running suite(s): service_thd
100%: Checks: 3, Failures: 0, Errors: 0
Running suite(s): ist
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): saved_state
100%: Checks: 3, Failures: 0, Errors: 0
Running suite(s): Defaults
100%: Checks: 1, Failures: 0, Errors: 0
Total tests failed: 8
scons: *** [galera/tests/galera_check.passed] Error 1
scons: building terminated because of errors.
*******

Help from sparc64 experts on why this happens on sparc64 but not other
platforms would be appreciated.

Contributions are welcome in this bug report or via Salsa:
https://wiki.debian.org/Teams/MySQL/patches