Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5(EOL)
-
None
Description
http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64-debug/builds/4331
|
10.5 baff3ba6e32d68876ec91fe808de8872 |
sys_vars.innodb_fatal_semaphore_wait_threshold 'innodb' w3 [ fail ]
|
Test ended at 2020-06-18 10:30:35
|
|
|
CURRENT_TEST: sys_vars.innodb_fatal_semaphore_wait_threshold
|
mysqltest: At line 95: Server failed to dissapear
|
|
|
The result from queries just before the failure was:
|
< snip >
|
create table t1 (id integer, x integer) engine = InnoDB;
|
insert into t1 values(0, 0);
|
set DEBUG_DBUG='+d,fatal-semaphore-timeout';
|
set autocommit=0;
|
# Sending query on con1,
|
# the session will hold lock table mutex and sleep
|
SELECT * from t1 where id = 0 FOR UPDATE;
|
connection con2;
|
set autocommit=0;
|
# Sending query on con2,
|
# the session will be blocked on the lock table mutex and
|
# thus be put into sync arry
|
SELECT * from t1 where id = 0 FOR UPDATE;
|
connection default;
|
# Waitting for mysqld to crash
|