Thanks for the tips. Unfortunately running just the single test
without any other load on the system still crashes it and system load
was otherwise zero, so it is not due to slowness.
I also tested explicit debug run and various ways to invoke gdb, but
--debug didn't yield any new info and all
I built the binary in debug mode and that yielded a stacktrace:
***
main.partition w38 [ retry-fail ]
Test ended at 2024-07-06 01:14:43
CURRENT_TEST: main.partition
mysqltest: At line 3010: query 'select id from t1 where data =
Hi!
On Tue, 2 Jul 2024 at 23:24, John Paul Adrian Glaubitz
wrote:
>
> Hello Otto,
>
> On Tue, 2024-07-02 at 21:10 -0700, Otto Kekäläinen wrote:
> > I recently uploaded MariaDB 11.4 to Debian, and it seems it regressed
> > on sparc64.
> >
> > Are there any
Hi!
I recently uploaded MariaDB 11.4 to Debian, and it seems it regressed
on sparc64.
Are there any sparc64 hackers interested in taking a look?
The build itself passed and most of the post-build passes, but some
tests cause the database to crash. Stack traces are visible in the
logs:
Source: mariadb
Version: 1:10.11.5-1
Tags: upstream, confirmed, help, ftbfs
X-Debbugs-CC: debian-sparc@lists.debian.org
User: debian-sparc@lists.debian.org
Usertags: sparc64
Builds on sparc64 repeatedly failed on tests main.ctype_binary
main.ctype_latin1 with error message:
main.ctype_binary
Source: mariadb
Version: 1:10.11.1-2
Tags: ftbfs
X-Debbugs-CC: debian-sparc@lists.debian.org
User: debian-sparc@lists.debian.org
Usertags: sparc64
In previous upload of MariaDB 1:10.11.1-1 the sparc64 build compiled
but then failed on test as reported in
Source: mariadb-10.6
Version: 1:10.6.7-3
Tags: upstream, confirmed, ftbfs
User: debian-sparc@lists.debian.org
Usertags: sparc64
Forwarded: https://jira.mariadb.org/browse/MDEV-28052
X-Debbugs-CC: debian-sparc@lists.debian.org
After upload of mariadb-10.6 1:10.6.7-3 I noticed that sparc64 builds
7 matches
Mail list logo
