Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.2(EOL)
-
None
Description
innodb.innodb_trx_weight 'xtradb' w3 [ fail ]
|
Test ended at 2016-10-27 08:30:49
|
|
|
CURRENT_TEST: innodb.innodb_trx_weight
|
mysqltest: In included file "./include/innodb_trx_weight.inc":
|
included from /usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/suite/innodb/t/innodb_trx_weight.test at line 99:
|
At line 29: query 'reap' succeeded - should have failed with errno 1213...
|
|
|
The result from queries just before the failure was:
|
SET storage_engine=InnoDB;
|
|
|
- saving '/usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/var/3/log/innodb.innodb_trx_weight-xtradb/' to '/usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/var/log/innodb.innodb_trx_weight-xtradb/'
|
|
|
Retrying test innodb.innodb_trx_weight, attempt(2/3)...
|
|
|
worker[3] > Restart - not started
|
innodb.innodb_trx_weight 'xtradb' w3 [ retry-pass ] 38
|
Attachments
Issue Links
- relates to
-
MDEV-7069 Fix buildbot failures in main server trees
-
- Closed
-
Activity
This looks like new InnoDB default lock wait protocol VATS makes this test fail (no real bugs here).
commit 0838fd00e7c95d54541c2126ef933d0ae65c02f7
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Wed Nov 16 12:07:12 2016 +0200
MDEV-11185: innodb.innodb_trx_weight fails in buildbot
Problem was that test assumes locks to be granted on first-come-first-served (FCFS)
policy. However, in 10.2 we use by default Variance-Aware-Transaction-Scheduling
(VATS) algorithm. Test failure fixed by setting lock wait policy to FCFS.
Raising to critical because it makes buildbot very red.