aarch64 macos encryption.create_or_replace assertion(end_lsn > state->end_lsn)

                      encryption.create_or_replace 'cbc,innodb' w49 [ fail ]

        Test ended at 2024-03-27 10:21:06

CURRENT_TEST: encryption.create_or_replace

mysqltest: At line 68: query 'reap;' failed: <Unknown> (2013): Lost connection to server during query

The result from queries just before the failure was:

SET @save_threads = @@GLOBAL.innodb_encryption_threads;

SET default_storage_engine = InnoDB;

SET GLOBAL innodb_encryption_threads = 4;

CREATE TABLE `table10_int_autoinc` (`col_int_key` int, pk int auto_increment, `col_int` int, key (`col_int_key` ),primary key (pk)) engine=innodb;

INSERT /*! IGNORE */ INTO table10_int_autoinc VALUES  (NULL, NULL, -474021888) ,  (1, NULL, NULL) ,  (1141047296, NULL, NULL) ,  (NULL, NULL, NULL) ,  (NULL, NULL, 1) ,  (NULL, NULL, 9) ,  (0, NULL, 1225785344) ,  (NULL, NULL, 157

...

Version: '10.11.8-MariaDB-log'  socket: '/Users/ec2-user/buildbot/aarch64-macos/build/mysql-test/var/tmp/49/mysqld.1.sock'  port: 16920  Source distribution

2024-03-27 10:18:53 4 [Note] InnoDB: Creating #1 encryption thread id 0x16b537000 total threads 4.

2024-03-27 10:18:53 4 [Note] InnoDB: Creating #2 encryption thread id 0x16b5c3000 total threads 4.

2024-03-27 10:18:53 4 [Note] InnoDB: Creating #3 encryption thread id 0x16b64f000 total threads 4.

2024-03-27 10:18:53 4 [Note] InnoDB: Creating #4 encryption thread id 0x16b6db000 total threads 4.

2024-03-27 10:21:03 0x16b537000  InnoDB: Assertion failure in file /Users/ec2-user/buildbot/aarch64-macos/build/storage/innobase/fil/fil0crypt.cc line 1823

InnoDB: Failing assertion: end_lsn > state->end_lsn

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to https://jira.mariadb.org/

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mariadbd startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/

InnoDB: about forcing recovery.

240327 10:21:03 [ERROR] mysqld got signal 6 ;

Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.

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.11.8-MariaDB-log source revision: 0c6cac0a6fab8bf80f5509bec7eb8eff04446dde

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=3

max_threads=153

thread_count=3

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63843 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

Printing to addr2line failed

0   mariadbd                            0x00000001055741dc my_print_stacktrace + 68

0   mariadbd                            0x0000000104ebb694 handle_fatal_signal + 772

0   libsystem_platform.dylib            0x00000001858e3a24 _sigtramp + 56

0   libsystem_pthread.dylib             0x00000001858b4cc0 pthread_kill + 288

0   libsystem_c.dylib                   0x00000001857c4a40 abort + 180

0   mariadbd                            0x0000000105631ce8 _Z16ib_list_add_lastP9ib_list_tPvP16mem_block_info_t.cold.1 + 0

0   mariadbd                            0x00000001053fc890 _ZL16fil_crypt_threadv + 5976

0   mariadbd                            0x00000001053c7c38 _ZNSt3__114__thread_proxyB7v160006INS_5tupleIJNS_10unique_ptrINS_15__thread_structENS_14default_deleteIS3_EEEEPFvvEEEEEEPvSA_ + 52

0   libsystem_pthread.dylib             0x00000001858b5034 _pthread_start + 136

0   libsystem_pthread.dylib             0x00000001858afe3c thread_start + 8

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains

information that should help you find out what is causing the crash.

Core pattern: /cores/core.%P