[MDEV-28543] Check testcase fails with --mysqld=--debug=d,intermittent_read_failure for various test cases Created: 2022-05-11  Updated: 2023-11-28

Status: Confirmed
Project: MariaDB Server
Component/s: Replication, Tests
Affects Version/s: 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9
Fix Version/s: 10.4, 10.5, 10.6

Type: Bug Priority: Major
Reporter: Angelique Sklavounos (Inactive) Assignee: Angelique Sklavounos (Inactive)
Resolution: Unresolved Votes: 0
Labels: None


 Description   

./mtr --mysqld=--debug=d,intermittent_read_failure binlog_encryption.rpl_parallel_incorrect_relay_pos  rpl.rpl_semisync_ali_issues binlog_encryption.rpl_parallel_stop_on_con_kill gcol.gcol_purge rpl.rpl_seconds_behind_master_spike binlog_encryption.rpl_parallel_retry_deadlock rpl.rpl_row_corruption rpl.rpl_parallel_stop_on_con_kill rpl.rpl_parallel_incorrect_relay_pos rpl.rpl_semi_sync_master_shutdown rpl.rpl_parallel_retry_deadlock

fails at check testcase step:

rpl.rpl_semi_sync_master_shutdown 'stmt' [ pass ]   3916
 
MTR's internal check of the test case 'rpl.rpl_semi_sync_master_shutdown' failed.
This means that the test case does not preserve the state that existed
before the test case was executed.  Most likely the test case did not
do a proper clean-up. It could also be caused by the previous test run
by this thread, if the server wasn't restarted.
This is the diff of the states of the servers before and after the
test case was executed:
mysqltest: Logging to '/home/parallels/dev/10.5/build1/mysql-test/var/tmp/check-mysqld_1.log'.
mysqltest: Results saved in '/home/parallels/dev/10.5/build1/mysql-test/var/tmp/check-mysqld_1.result'.
mysqltest: Connecting to server localhost:16000 (socket /home/parallels/dev/10.5/build1/mysql-test/var/tmp/mysqld.1.sock) as 'root', connection 'default', attempt 0 ...
mysqltest: ... Connected.
mysqltest: Start processing test commands from './include/check-testcase.test' ...
mysqltest: ... Done processing test commands.
--- /home/parallels/dev/10.5/build1/mysql-test/var/tmp/check-mysqld_1.result	2022-05-11 13:25:37.457554354 +0100
+++ /home/parallels/dev/10.5/build1/mysql-test/var/tmp/check-mysqld_1.reject	2022-05-11 13:25:41.554341020 +0100
@@ -124,9 +124,9 @@
 DEADLOCK_SEARCH_DEPTH_SHORT	4
 DEADLOCK_TIMEOUT_LONG	50000000
 DEADLOCK_TIMEOUT_SHORT	10000
-DEBUG	d,intermittent_read_failure
+DEBUG
 DEBUG_BINLOG_FSYNC_SLEEP	0
-DEBUG_DBUG	d,intermittent_read_failure
+DEBUG_DBUG
 DEBUG_MUTEX_DEADLOCK_DETECTOR	ON
 DEBUG_NO_THREAD_ALARM	OFF
 DEFAULT_PASSWORD_LIFETIME	0
 
mysqltest: Result length mismatch
 
not ok

Checked with:
10.2 a5dc12eefd4bea1c3f77d02c55d0d459b4ae0566
10.3 b208030ef5b4274fd66cc9667a2dc96f6e63db81
10.4 a4139f8d68bd31e80ff6202c093cd232c194ddfd
10.5 fe3d07cab82b2215dc64f52ac93122072c33d021
10.6 cad792c6862546a13b83f05209e7842a95bdc5fa
10.7 9e314fcf6e666ce6fdbdd8ca1ae23d6c4b389b21
10.8 bde0b31dc59bd1f171f3e62efb5443382c94c141
10.9 51b28b24ca3a33a3a9b2a844c6c8a94df1bad253

Discovered from work on MDEV-13542.



 Comments   
Comment by Marko Mäkelä [ 2022-05-11 ]

Note: That DEBUG_DBUG label is not present in any source code yet. I am going to introduce it in MDEV-13542. Any non-existent label would reproduce the trouble equally well.

Generated at Thu Feb 08 10:01:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.