[MDEV-16573] rocksdb.autoinc_vars_thread fails in buildbot with wrong result Created: 2018-06-25  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - RocksDB, Tests
Affects Version/s: 10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Petrunia
Resolution: Won't Fix Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-16576 rocksdb.unique_check fails in buildbo... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64-debug/builds/588

rocksdb.autoinc_vars_thread              w1 [ fail ]
 
        Test ended at 2018-06-22 15:55:53
 
 
 
CURRENT_TEST: rocksdb.autoinc_vars_thread
 
--- /usr/share/mysql-test/plugin/rocksdb/rocksdb/r/autoinc_vars_thread.result	2018-06-22 14:42:26.000000000 +0000
 
+++ /dev/shm/var/1/log/autoinc_vars_thread.reject	2018-06-22 15:55:53.212777446 +0000
 
@@ -25,6 +25,8 @@
 
 SET debug_sync='now SIGNAL go2';
 
 connection default;
 
 connection con1;
 
+Warnings:
 
+Warning	1639	debug sync point wait timed out
 
 connection con2;
 
 connection default;
 
 SET debug_sync='RESET';
 
 
 
mysqltest: Result length mismatch
 
 
 
 - found 'core.5352' (0/0)
 
 
 
Trying 'dbx' to get a backtrace
 
gdb not found, cannot get the stack trace
 
Compressed file /dev/shm/var/1/log/rocksdb.autoinc_vars_thread/mysqld.1/data/core.5352
 
 - found 'core.5276' (1/0)
 
 
 
Trying 'dbx' to get a backtrace
 
gdb not found, cannot get the stack trace
 
Compressed file /dev/shm/var/1/log/rocksdb.autoinc_vars_thread/mysqld.1/data/core.5276
 
 - skipping '/dev/shm/var/1/log/rocksdb.autoinc_vars_thread/'



 Comments   
Comment by Sergei Petrunia [ 2018-10-16 ]

Still fails intermittently like so:
https://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64-debug/builds/1003/steps/mtr/logs/stdio

rocksdb.autoinc_vars_thread 'write_prepared' w2 [ fail ]
 
        Test ended at 2018-10-15 18:01:58
 
 
 
CURRENT_TEST: rocksdb.autoinc_vars_thread
 
--- /usr/share/mysql-test/plugin/rocksdb/rocksdb/r/autoinc_vars_thread.result	2018-10-15 16:33:45.000000000 +0000
 
+++ /dev/shm/var/2/log/autoinc_vars_thread.reject	2018-10-15 18:01:58.104750298 +0000
 
@@ -20,12 +20,18 @@
 
 connection default;
 
 SET debug_sync='now WAIT_FOR parked1';
 
 SET debug_sync='now WAIT_FOR parked2';
 
+Warnings:
 
+Warning	1639	debug sync point wait timed out
 
 SET debug_sync='now SIGNAL go1';
 
 connection con3;
 
 SET debug_sync='now SIGNAL go2';
 
 connection default;
 
 connection con1;
 
+Warnings:
 
+Warning	1639	debug sync point wait timed out
 
 connection con2;
 
+Warnings:
 
+Warning	1639	debug sync point wait timed out
 
 connection default;
 
 SET debug_sync='RESET';
 
 disconnect con1;
 
 
 
mysqltest: Result length mismatch
 
 
 
 - saving '/dev/shm/var/2/log/rocksdb.autoinc_vars_thread-write_prepared/' to '/dev/shm/var/log/rocksdb.autoinc_vars_thread-write_prepared/'
 
 
 
Retrying test rocksdb.autoinc_vars_thread, attempt(2/3)...
 
 
 
worker[2] > Restart  - not started
 
rocksdb.autoinc_vars_thread 'write_prepared' w2 [ retry-pass ]     55

Comment by Sergei Petrunia [ 2018-10-16 ]

I've had it fail for me too, but I havent' been able to reproduce with any reliability that would allow to debug.

Comment by Sergei Petrunia [ 2019-07-15 ]

Discussed with svoj (in late May). He has pointed out that dbug sync is not being used in a correct way.

Yesterday, pushed a fix to 10.2. Let's see whether it works.

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