Bug #40699 concurrent_innodb_unsafelog fails sporadically on pushbuild: result mismatch

• Submitted: 13 Nov 2008 14:37
• Modified: 4 Aug 2009 23:27
• Reporter: Sven Sandberg
• Status: Closed
• Category: Tests: Server
• Severity: S7 (Test Cases)
• Version: 5.1, 6.0
• OS: Any
• Assigned to: Horst Hunger
• CPU Architecture: Any
• Tags: concurrent_innodb_unsafelog, pushbuild, sporadic, test failure

[13 Nov 2008 14:37] Sven Sandberg

Description:
seen on pushbuild:

main.concurrent_innodb_unsafelog         [ fail ]

CURRENT_TEST: main.concurrent_innodb_unsafelog
--- /data0/pushbuild/pb/bzr_mysql-5.1-rpl/64/bzr_mysql-5.1-rpl-exp/mysql-test/r/concurrent_innodb_unsafelog.result	2008-10-08 00:51:45.000000000 +0300
+++ /data0/pushbuild/pb/bzr_mysql-5.1-rpl/64/bzr_mysql-5.1-rpl-exp/mysql-test/r/concurrent_innodb_unsafelog.reject	2008-10-08 01:01:31.000000000 +0300
@@ -71,7 +71,7 @@
 ** Release the lock and collect result from update on thread 2
 select release_lock("hello");
 release_lock("hello")
-1
+NULL
 ** Table should have eta updates where tipo=11 but updates made by
 ** thread 1 shouldn't be visible yet.
 select * from t1;

mysqltest: Result content mismatch

 - saving '/dev/shm/var-ps_row-121/2/log/main.concurrent_innodb_unsafelog/' to '/dev/shm/var-ps_row-121/log/main.concurrent_innodb_unsafelog/'

Retrying test, attempt(2/3)...

How to repeat:
https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-5.1-rpl&order=64 sapsrv1/ps_row
xref: http://tinyurl.com/5l75nm

[4 Aug 2009 23:27] Paul DuBois

Test case changes. No changelog entry needed.