[debian-mysql] Bug#1104002: mariadb: FTBFS on sparc64: new LLM embedding / vector functions crash on sparc64

[Otto Kekäläinen]

X-Debbugs-CC: debian-amd64 at lists.debian.org
User: debian-x32 at lists.debian.org
Usertags: sparc64

Looking at the most recent MariaDB builds on at
https://buildd.debian.org/status/package.php?p=mariadb seems x32 is
failing on these same vector functions.

In the sparc64 build they are skipped, but the post-build MTR test is
failing on other tests crashing:
...
main.delete_use_source_engines           w13 [ pass ]  32203
main.partition_innodb                    w3 [ pass ]  77352
main.update_use_source                   w21 [ pass ]  52894
main.update_innodb                       w30 [ pass ]  35943
main.parser_bug21114_innodb              w16 [ pass ]  133529
main.long_unique_innodb                  w17 [ retry-fail ]
        Test ended at 2025-11-08 21:44:11

CURRENT_TEST: main.long_unique_innodb
mysqltest: At line 165: query 'update ignore t1 set f = 'x'' failed
with wrong errno <Unknown> (2013): 'Lost connection to server during
query', instead of ER_NOT_SUPPORTED_YET (1235)...
...
Completed: Failed 6/1135 tests, 99.47% were successful.
Failing test(s): main.long_unique_innodb main.alter_table_lock
main.unsafe_binlog_innodb
...

This bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104002
has steps to reproduce how I tested sparc64 builds and MTR on
stadler.debian.net myself in case somebody has bandwidth to try to
make MariaDB run well on sparc64.