Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.5, 10.6
Description
According to cross-reference, this test fails rather often on buildbot.
First occurence, according to cross-reference was 2023-12-07 05:58:09
Typical 10.5 error - "timeout after 900 seconds", ánd in 10.6 error "debug sync point timeout"
Example of failing build https://buildbot.mariadb.net/buildbot/builders/kvm-fulltest2-protocols/builds/1305
Sample output from failure
innodb.innodb-lock-inherit-read_commited 'innodb' w2 [ fail ] timeout after 900 seconds
|
Test ended at 2023-12-19 15:42:20
|
|
|
Test case timeout after 900 seconds
|
|
|
== /mnt/buildbot/build/mariadb-10.5.24/mysql-test/var/2/log/innodb-lock-inherit-read_commited.log ==
|
con1_locks_done WAIT_FOR con1_go';
|
SET debug_sync = 'ha_commit_trans_after_acquire_commit_lock SIGNAL
|
con1_insert_done WAIT_FOR con1_finish';
|
REPLACE INTO t1 VALUES (1,2);
|
connect con2,localhost,root,,;
|
SET debug_sync = 'now WAIT_FOR con1_locks_done';
|
SET debug_sync = 'lock_wait_suspend_thread_enter SIGNAL con2_blocked
|
WAIT_FOR con2_go';
|
SET debug_sync = 'ha_commit_trans_after_acquire_commit_lock
|
WAIT_FOR con2_finish';
|
SET debug_sync = 'ib_after_row_insert SIGNAL con2_insert_done';
|
REPLACE INTO t1 VALUES (1,3);
|
connection default;
|
SET debug_sync = 'now WAIT_FOR con2_blocked';
|
connection purge_control;
|
COMMIT;
|
disconnect purge_control;
|
connection default;
|
InnoDB 0 transactions not purged
|
SET debug_sync = 'now SIGNAL con2_go WAIT_FOR con2_insert_done';
|
|
|
|
|
- saving '/mnt/buildbot/build/mariadb-10.5.24/mysql-test/var/2/log/innodb.innodb-lock-inherit-read_commited-innodb/' to '/mnt/buildbot/build/mariadb-10.5.24/mysql-test/var/log/innodb.innodb-lock-inherit-read_commited-innodb/'
|
|
|
Retrying test innodb.innodb-lock-inherit-read_commited, attempt(2/3)...
|
|