Description:
If server is built with sanitizers, the test failed with a result difference every time I tried. If not built with sanitizers, the test passes most of the time but not always. I suspect the cause is not the sanitizer itself, but that it adds enough slowness to expose some underlying instability.
$ mtr innodb.resurrection_logs
...
[ 50%] innodb.resurrection_logs [ fail ]
Test ended at 2024-01-24 12:16:08
CURRENT_TEST: innodb.resurrection_logs
WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version.
WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version.
--- /Users/laurynas/vilniusdb/mysql-8.3.0/mysql-test/suite/innodb/r/resurrection_logs.result 2024-01-22 16:39:22
+++ /Users/laurynas/vilniusdb/mysql-8.3.0/_build-debug-san/mysql-test/var/log/resurrection_logs.reject 2024-01-24 13:16:08
@@ -31,7 +31,7 @@
CALL bulk_upd(10);
# Kill and restart: --log-error-verbosity=3 --debug=+d,resurrect_logs
Pattern "Transaction ID:.* found for resurrecting inserts" found
-Pattern "Records read:.* - Pages read:.*" not found
+Pattern "Records read:.* - Pages read:.*" found
Pattern "Transaction ID:.* found for resurrecting updates" found
Pattern "Identified table ID:.* to acquire lock" found
Pattern "Resurrected .* transaction.* doing inserts." found
mysqltest: Result content mismatch
How to repeat:
Server built with -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_BUILD_TYPE=Debug -DWITH_DEBUG=ON -DMYSQL_MAINTAINER_MODE=ON -DWITH_SYSTEM_LIBS=ON -DFORCE_COLORED_OUTPUT=ON -DWITH_ZLIB=bundled -DWITH_ASAN=ON -DWITH_ASAN_SCOPE=ON -DWITH_UBSAN=ON