[MDEV-12753] innodb.truncate_debug fails in buildbot with debug sync point timeout warning Created: 2017-05-09  Updated: 2017-05-10  Resolved: 2017-05-10

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2
Fix Version/s: N/A

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

Issue Links:
Duplicate
duplicates MDEV-12754 innodb.truncate_debug fails in buildb... Closed

 Description   

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

innodb.truncate_debug 'innodb'           w4 [ fail ]
        Test ended at 2017-05-09 13:54:49
 
CURRENT_TEST: innodb.truncate_debug
--- /mnt/buildbot/build/mariadb-10.2.6/mysql-test/suite/innodb/r/truncate_debug.result	2017-05-09 12:10:00.000000000 +0300
+++ /mnt/buildbot/build/mariadb-10.2.6/mysql-test/suite/innodb/r/truncate_debug.reject	2017-05-09 13:54:49.000000000 +0300
@@ -77,6 +77,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 con2;
 disconnect con2;
 
mysqltest: Result length mismatch



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

This is essentially a duplicate of MDEV-12754, most likely caused by a lost DEBUG_SYNC signal.

Generated at Thu Feb 08 08:00:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.