Bug #37480 commit_1innodb.test fails randomly

• Submitted: 18 Jun 2008 13:45
• Modified: 19 Jun 2008 20:59
• Reporter: Alexander Nozdrin
• Status: Closed
• Category: MySQL Server: Tests
• Severity: S7 (Test Cases)
• Version: 6.0
• OS: Any
• CPU Architecture: Any
• Tags: pushbuild, sporadic, test failure
• Triage: D3 (Medium)

[18 Jun 2008 13:45] Alexander Nozdrin

Description:
main.commit_1innodb.test fails randomly

--- /home/pushbuild/pb3/pb/bzr_mysql-6.0-bugteam/23/mysql-6.0.6-alpha-pb23/mysql-test/r/commit_1innodb.result	2008-06-18 08:29:06.000000000 +0300
+++ /home/pushbuild/pb3/pb/bzr_mysql-6.0-bugteam/23/mysql-6.0.6-alpha-pb23/mysql-test/r/commit_1innodb.reject	2008-06-18 16:19:31.000000000 +0300
@@ -493,12 +493,12 @@
 #
 replace t1 set a=1;
 call p_verify_status_increment(2, 2, 1, 0);
-SUCCESS
-
+ERROR
+Expected commit increment: 1 actual: 2
 commit;
 call p_verify_status_increment(2, 2, 1, 0);
-SUCCESS
-
+ERROR
+Expected commit increment: 1 actual: 2
 # 11. Read-write statement: IODKU, change 1 row. 
 #
 insert t1 set a=1 on duplicate key update a=a+1;

mysqltest: Result content mismatch

How to repeat:
https://intranet.mysql.com/secure/pushbuild/xref.pl?testname=main.commit_1innodb

[19 Jun 2008 20:59] Timothy Smith

Pushed to mysql-6.0 as part of large batch of InnoDB changes.  See https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-6.0&order=9