Bug #46470 sys_vars.max_binlog_cache_size_basic_32 is broken

• Submitted: 30 Jul 2009 8:41
• Modified: 6 Mar 2010 23:57
• Reporter: Sergei Golubchik
• Status: Closed
• Category: MySQL Server: Tests
• Severity: S3 (Non-critical)
• Version: 5.1, azalea
• OS: Any
• CPU Architecture: Any

[30 Jul 2009 8:41] Sergei Golubchik

Description:
looks like a fix for Bug#40657 has broken sys_vars.max_binlog_cache_size_basic_32 in a not very helpful way.

sys_vars is broken in many places, I'm fixing all the others, but not the max_binlog_cache_size_basic_32.

How to repeat:
./mtr sys_vars.max_binlog_cache_size_basic_32

[30 Jul 2009 8:58] Sveta Smirnova

Thank you for the report.

Verified as described:

CURRENT_TEST: sys_vars.max_binlog_cache_size_basic_32
--- /Users/apple/bzr/mysql-azalea/mysql-test/suite/sys_vars/r/max_binlog_cache_size_basic_32.result     2009-06-17 12:09:15.000000000 +0300
+++ /Users/apple/bzr/mysql-azalea/mysql-test/suite/sys_vars/r/max_binlog_cache_size_basic_32.reject     2009-07-30 11:54:23.000000000 +0300
@@ -1,13 +1,13 @@
 SET @start_value = @@global.max_binlog_cache_size;
 SELECT @start_value;
 @start_value
-4294963200
+-4096
 '#--------------------FN_DYNVARS_072_01------------------------#'
 SET @@global.max_binlog_cache_size = 5000;
 SET @@global.max_binlog_cache_size = DEFAULT;
 SELECT @@global.max_binlog_cache_size;
 @@global.max_binlog_cache_size
-4294963200
+-4096
 '#---------------------FN_DYNVARS_072_02-------------------------#'
 SET @@global.max_binlog_cache_size = @start_value;
 SELECT @@global.max_binlog_cache_size = 4294967295;
@@ -38,28 +38,22 @@
 'Bug# 34877: Invalid Values are coming in variable on assigning valid values';
 '#--------------------FN_DYNVARS_072_04-------------------------#'
 SET @@global.max_binlog_cache_size = -1;
-Warnings:
-Warning        1292    Truncated incorrect max_binlog_cache_size value: '-1'
 SELECT @@global.max_binlog_cache_size;
 @@global.max_binlog_cache_size
-4096
+-4096
 SET @@global.max_binlog_cache_size = 100000000000;
-Warnings:
-Warning        1292    Truncated incorrect max_binlog_cache_size value: '100000000000'
 SELECT @@global.max_binlog_cache_size;
 @@global.max_binlog_cache_size
-4294963200
[phone]
 SET @@global.max_binlog_cache_size = 10000.01;
 ERROR 42000: Incorrect argument type to variable 'max_binlog_cache_size'
 SELECT @@global.max_binlog_cache_size;
 @@global.max_binlog_cache_size
-4294963200
[phone]
 SET @@global.max_binlog_cache_size = -1024;
-Warnings:
-Warning        1292    Truncated incorrect max_binlog_cache_size value: '-1024'
 SELECT @@global.max_binlog_cache_size;
 @@global.max_binlog_cache_size
-4096
+-4096
 SET @@global.max_binlog_cache_size = 1024;
 Warnings:
 Warning        1292    Truncated incorrect max_binlog_cache_size value: '1024'
@@ -67,11 +61,9 @@
 @@global.max_binlog_cache_size
 4096
 SET @@global.max_binlog_cache_size = 4294967296;
-Warnings:
-Warning        1292    Truncated incorrect max_binlog_cache_size value: '4294967296'
 SELECT @@global.max_binlog_cache_size;
 @@global.max_binlog_cache_size
-4294963200
[phone]
 SET @@global.max_binlog_cache_size = 4095;
 Warnings:
 Warning        1292    Truncated incorrect max_binlog_cache_size value: '4095'
@@ -142,4 +134,4 @@
 SET @@global.max_binlog_cache_size = @start_value;
 SELECT @@global.max_binlog_cache_size;
 @@global.max_binlog_cache_size
-4294963200
+-4096

[31 Aug 2009 17:04] Sergei Golubchik

not surprisingly, sys_vars.max_binlog_cache_size_basic_64 is broken too

[6 Mar 2010 11:02] Bugs System

Pushed into 5.5.3-m3 (revid:[e-mail]-20100306103849-hha31z2enhh7jwt3) (version source revid:vvaintroub@fedora12-20091225154921-x25a5pyw1pxiwobv) (merge vers: 5.5.99) (pib:16)

[6 Mar 2010 23:57] Paul DuBois

Changes to test case. No changelog entry needed.