[MDEV-11185] innodb.innodb_trx_weight fails in buildbot Created: 2016-10-31  Updated: 2016-11-16  Resolved: 2016-11-16

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

Type: Bug Priority: Critical
Reporter: Elena Stepanova Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-quantal-amd64/builds/3815/steps/test/logs/stdio

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



 Comments   
Comment by Elena Stepanova [ 2016-11-06 ]

Raising to critical because it makes buildbot very red.

Comment by Jan Lindström (Inactive) [ 2016-11-15 ]

This looks like new InnoDB default lock wait protocol VATS makes this test fail (no real bugs here).

Comment by Jan Lindström (Inactive) [ 2016-11-16 ]

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.

Generated at Thu Feb 08 07:47:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.