On Fri, Feb 10, 2023 at 09:12:01AM -0800, Otto Kekäläinen wrote: > For the record, latest upload 10.11.1-4 in > https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=sparc64&ver=1%3A10.11.1-4&stamp=1676000962&raw=0 > no longer had the bad address issue, but instead if failed on two > tests: [snip]
First of all, let me thank you for all your work on MariaDB, and let me thank the sparc64 porters for making it possible to build anything on Debian/sparc64 at all :) FWIW, I've been wondering whether something may be wrong with the sparc64 builder for a couple of weeks now: libzstd has been failing to build there since February: https://buildd.debian.org/status/logs.php?pkg=libzstd&arch=sparc64 Now, I can explain the -1, -2, and -4 failures, they were due to problems in an upstream test that is run at build time, but the -3 and -5 ones should not really have happened: those uploads of libzstd built pretty much fine on all other Debian architectures (barring the ones where the build dependencies were unavailable). The cause for the failed builds seems to be a segfault that I cannot reproduce in a sbuild+schroot+qemu run on my x86_64 laptop. Of course, it may turn out that the problem is somehow related to the amount of memory, CPUs, or other differences in the build environment. Of course, it may be totally unrelated to the failed MariaDB builds, but I just thought I'd mention it in case it turns out to be. Once again, thanks everyone, and keep up the great work! G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
signature.asc
Description: PGP signature
