percona_innodb_deadlock fails

Bug #800559 reported by Oleg Tsarev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
High
Oleg Tsarev
5.1
Fix Released
High
Oleg Tsarev
5.5
Fix Released
High
Oleg Tsarev

Bug Description

main.percona_innodb_deadlock_count w5 [ fail ]
        Test ended at 2011-06-21 17:33:12

CURRENT_TEST: main.percona_innodb_deadlock_count
--- /mnt/workspace/percona-server-5.1-trunk/BUILD_TYPE/release/Host/ubuntu-maverick-64bit/Percona-Server-5.1.57/mysql-test/r/percona_innodb_deadlock_count.result 2011-06-21 20:20:07.000000000 +0300
+++ /mnt/workspace/percona-server-5.1-trunk/BUILD_TYPE/release/Host/ubuntu-maverick-64bit/Percona-Server-5.1.57/mysql-test/r/percona_innodb_deadlock_count.reject 2011-06-21 20:33:11.000000000 +0300
@@ -23,10 +23,10 @@
 # Switch to connection con2
 SELECT b FROM t WHERE a=1 FOR UPDATE;
 # Switch to connection con1
-b
-1
-# Switch to connection con2
 ERROR 40001: Deadlock found when trying to get lock; try restarting transaction
+# Switch to connection con2
+b
+2
 # Switch to connection con3
 1
 # Drop test table

mysqltest: Result content mismatch

Related branches

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-486

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.