percona_innodb_deadlock fails
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_
Test ended at 2011-06-21 17:33:12
CURRENT_TEST: main.percona_
--- /mnt/workspace/
+++ /mnt/workspace/
@@ -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
- Percona developers: Pending requested
-
Diff: 139 lines (+72/-41)2 files modifiedmysql-test/innodb_deadlock_count.patch/percona_innodb_deadlock_count.result (+25/-12)
mysql-test/innodb_deadlock_count.patch/percona_innodb_deadlock_count.test (+47/-29)
- Percona developers: Pending requested
-
Diff: 82 lines (+12/-12)2 files modifiedmysql-test/innodb_deadlock_count.patch/percona_innodb_deadlock_count.result (+3/-8)
mysql-test/innodb_deadlock_count.patch/percona_innodb_deadlock_count.test (+9/-4)
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PS-486