[MDEV-11422] rpl.rpl_parallel_optimistic_nobinlog failed in buildbot with "InnoDB: Killing connection failed Deadlock" Created: 2016-11-29  Updated: 2016-12-08  Resolved: 2016-12-08

Status: Closed
Project: MariaDB Server
Component/s: Replication, Storage Engine - InnoDB, Tests
Affects Version/s: 10.2.2
Fix Version/s: 10.2.3

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None

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

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-deb-trusty-amd64/builds/4069/steps/test_5/logs/stdio

rpl.rpl_parallel_optimistic_nobinlog 'stmt,xtradb' w1 [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2016-11-29 17:27:17
 
line
 
2016-11-29 17:27:17 140288030135040 [Warning] InnoDB: Killing connection failed Deadlock(16)
 
^ Found warnings in /run/shm/var/1/log/mysqld.2.err
 
ok
 
 
 
 - saving '/run/shm/var/1/log/rpl.rpl_parallel_optimistic_nobinlog-stmt,xtradb/' to '/run/shm/var/log/rpl.rpl_parallel_optimistic_nobinlog-stmt,xtradb/'
 
 
 
Retrying test rpl.rpl_parallel_optimistic_nobinlog, attempt(2/3)...



 Comments   
Comment by Marko Mäkelä [ 2016-12-08 ]

This turned out to be a bogus warning message for the rare case that the transaction that is subject to KILL QUERY has already been aborted due to a deadlock.

Comment by Jan Lindström (Inactive) [ 2016-12-08 ]

ok to push.

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