maria.maria-no-logging failed in buildbot: SIGABRT on server shutdown or can't start server

maria.maria-no-logging                   w2 [ fail ]

        Test ended at 2019-07-24 15:07:02

CURRENT_TEST: maria.maria-no-logging

mysqltest: In included file "./include/wait_until_connected_again.inc": 

included from ./include/maria_empty_logs.inc at line 85:

included from /home/buildbot/buildbot/build/mariadb-10.3.17/mysql-test/suite/maria/maria-no-logging.test at line 41:

At line 23: Server failed to restart

The result from queries just before the failure was:

< snip >

connection default;

use mysqltest;

set global aria_checkpoint_interval=0;

create table t2 (a varchar(100)) engine=myisam;

insert into t2 select repeat('z',100);

insert into t2 select * from t2;

insert into t2 select * from t2;

insert into t2 select * from t2;

insert into t2 select * from t2;

insert into t2 select * from t2;

insert into t2 select * from t2;

connection default;

connection admin;

* shut down mysqld, removed logs, restarted it

connection default;

maria.maria-no-logging                   w4 [ fail ]  Found warnings/errors in server log file!

        Test ended at 2019-07-13 15:42:17

line

Attempting backtrace. You can use the following information to find out

^ Found warnings in /dev/shm/var/4/log/mysqld.1.err

ok

2019-07-13 15:42:14 0 [Note] /usr/sbin/mysqld (initiated by: root[root] @ localhost []): Normal shutdown

2019-07-13 15:42:14 0 [Note] Event Scheduler: Purging the queue. 0 events

190713 15:42:14 [ERROR] mysqld got signal 6 ;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed, 

something is definitely wrong and this may fail.

Server version: 10.4.7-MariaDB-log

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=2

max_threads=153

thread_count=1

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63515 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

stack_bottom = 0x0 thread_stack 0x49000

2019-07-13 15:42:14 0 [Note] /usr/sbin/mysqld: Shutdown complete