Percona Server with XtraDB

percona_innodb_deadlock_count fails on 11.0 with -DUNIV_SYNC_DEBUG -DUNIV_DEBUG

Reported by Aleksandr Kuzminsky on 2010-06-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server
Undecided
Oleg Tsarev

Bug Description

main.percona_innodb_deadlock_count [ fail ]
        Test ended at 2010-06-06 18:08:20

CURRENT_TEST: main.percona_innodb_deadlock_count
--- /mnt/data1/home/buildbot/slaves/percona-server-51-11/sm1u02/build/Percona-Server/mysql-test/r/percona_innodb_deadlock_count.result 2010-06-07 00:22:26.000000000 +0300
+++ /mnt/data1/home/buildbot/slaves/percona-server-51-11/sm1u02/build/Percona-Server/mysql-test/r/percona_innodb_deadlock_count.reject 2010-06-07 04:08:20.000000000 +0300
@@ -23,6 +23,6 @@
 # Switch to connection con2
 SELECT b FROM t WHERE a=1 FOR UPDATE;
 # Switch to connection con3
-1
+0
 # Drop test table
 drop table if exists t;

mysqltest: Result content mismatch

Changed in percona-server:
milestone: none → 5.1-11.0
Changed in percona-server:
assignee: nobody → Oleg Tsarev (tsarev)
Oleg Tsarev (tsarev) on 2010-06-07
Changed in percona-server:
status: New → In Progress
Oleg Tsarev (tsarev) on 2010-06-07
Changed in percona-server:
status: In Progress → Fix Committed
Changed in percona-server:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers