|
The test for MDEV-6619 occasionally fails as follows (observed on the mandatory MemorySanitizer staging builder, but I have seen it in my local environment as well):
main.kill_processlist-6619 w55 [ fail ]
|
Test ended at 2024-01-22 06:48:05
|
CURRENT_TEST: main.kill_processlist-6619
|
--- /home/buildbot/amd64-debian-11-msan/build/mysql-test/main/kill_processlist-6619.result 2024-01-22 06:34:52.000000000 +0000
|
+++ /home/buildbot/amd64-debian-11-msan/build/mysql-test/main/kill_processlist-6619.reject 2024-01-22 06:48:04.671491118 +0000
|
@@ -1,7 +1,7 @@
|
connect con1,localhost,root,,;
|
SHOW PROCESSLIST;
|
Id User Host db Command Time State Info Progress
|
-# root # test Sleep # # NULL 0.000
|
+# root # test Query # # select count(*) = 0 from information_schema.session_variables where variable_name = 'debug_sync' and 0.000
|
# root # test Query # # SHOW PROCESSLIST 0.000
|
SET DEBUG_SYNC='before_execute_sql_command SIGNAL ready WAIT_FOR go';
|
SHOW PROCESSLIST;
|
As far as I can tell, this is a race condition. I failed to reproduce this by running the last few tests that had been executed on the same server instance before the failure:
./mtr --no-reorder main.keywords main.kill main.kill_processlist-6619
|
|