Bug #119746 innodb.table_encrypt_4 failing with a result difference

Submitted:	22 Jan 12:04	Modified:	2 Jul 4:08
Reporter:	Laurynas Biveinis (OCA)	Email Updates:
Status:	Open	Impact on me:	None
Category:	MySQL Server: Tests	Severity:	S7 (Test Cases)
Version:	9.7.0	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
9.5.0 debug+sanitizers build:

$ ./mtr innodb.table_encrypt_4
...
[ 50%] innodb.table_encrypt_4                    [ fail ]
        Test ended at 2026-01-22 14:02:42

CURRENT_TEST: innodb.table_encrypt_4
--- /Users/laurynas/vilniusdb/mysql-9.6.0/mysql-test/suite/innodb/r/table_encrypt_4.result	2026-01-22 07:35:02
+++ /Users/laurynas/vilniusdb/mysql-9.6.0/_build-debug-san/mysql-test/var/log/table_encrypt_4.reject	2026-01-22 15:02:41
@@ -1,5 +1,6 @@
 # ----------------------------------------------------------------------
 # Setup
+# Do global_backup of global manifest and global configuration file for: component_keyring_file
 # Creating custom global manifest file for MySQL server
 # Creating custom global configuration file for keyring component: component_keyring_file
 # Re-starting mysql server with manifest file
@@ -161,5 +162,6 @@
 # Removing local keyring file for keyring component: component_keyring_file
 # Removing global configuration file for keyring component: component_keyring_file
 # Removing global manifest file for MySQL server
+# Restore global manifest and global configuration file from global_backup for: component_keyring_file
 # Restarting server without the manifest file
 # ----------------------------------------------------------------------

mysqltest: Result content mismatch

How to repeat:
See above

Same with 9.7.0-er

Same under 9.7.0

Page generated in 0.049 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.