[MDEV-12708] innodb.truncate_purge_debug fails sporadically in buildbot Created: 2017-05-05  Updated: 2018-05-17  Resolved: 2017-05-10

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2.6
Fix Version/s: 10.2.6

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
is caused by MDEV-11802 innodb.innodb_bug14676111 fails in bu... Closed
is caused by MDEV-12754 innodb.truncate_debug fails in buildb... Closed
Relates
relates to MDEV-11802 innodb.innodb_bug14676111 fails in bu... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/7959/steps/test_2/logs/stdio

innodb.truncate_purge_debug 'innodb'     w1 [ fail ]
 
        Test ended at 2017-05-03 11:08:13
 
 
 
CURRENT_TEST: innodb.truncate_purge_debug
 
--- /mnt/buildbot/build/mariadb-10.2.6/mysql-test/suite/innodb/r/truncate_purge_debug.result	2017-05-03 09:30:39.000000000 +0300
 
+++ /mnt/buildbot/build/mariadb-10.2.6/mysql-test/suite/innodb/r/truncate_purge_debug.reject	2017-05-03 11:08:12.000000000 +0300
 
@@ -24,6 +24,8 @@
 
 SET DEBUG_SYNC = 'now SIGNAL finish_scan';
 
 SET DEBUG_SYNC = 'RESET';
 
 connection con1;
 
+Warnings:
 
+Warning	1639	debug sync point wait timed out
 
 disconnect con1;
 
 connection default;
 
 drop table t1;
 
 
 
mysqltest: Result length mismatch



 Comments   
Comment by Marko Mäkelä [ 2017-05-10 ]

This sporadic failure ("debug sync point wait timed out") is a duplicate of MDEV-12754.

There is another (independent) sporadic failure that should be tracked and fixed under this ticket (it looks like MDEV-11802 might not be fully fixed):

CURRENT_TEST: innodb.truncate_purge_debug
 
--- /mariadb/10.2/mysql-test/suite/innodb/r/truncate_purge_debug.result	2017-04-26 23:03:32.060878489 +0300
 
+++ /mariadb/10.2/mysql-test/suite/innodb/r/truncate_purge_debug.reject	2017-05-10 11:01:43.462853528 +0300
 
@@ -19,7 +19,7 @@
 
 COMMIT;
 
 disconnect con2;
 
 connection default;
 
-InnoDB		0 transactions not purged
 
+InnoDB		1 transactions not purged
 
 SET GLOBAL innodb_purge_rseg_truncate_frequency = @saved_frequency;
 
 SET DEBUG_SYNC = 'now SIGNAL finish_scan';
 
 SET DEBUG_SYNC = 'RESET';
 
 
 
mysqltest: Result content mismatch

Comment by Marko Mäkelä [ 2017-05-10 ]

I pushed a workaround that wakes up the purge when SHOW ENGINE INNODB STATUS is executed. That is what the test innodb.truncate_purge_debug uses for polling.

Note: the test will often still fail due to the lost DEBUG_SYNC signal (MDEV-12754).

Generated at Thu Feb 08 07:59:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.