Re: MySQL-4.1 bk failures on OpenServer 5.0.7 26 May 04 16:00 MDT

 Hi All,

On Sat, 26 Jun 2004, Boyd Lynn Gerber wrote:
> OpenServer 5.0.7 has failure with the following.
> func_group                     [ fail ]
> 
> Errors are (from 
> /home/blg/osr507/mysql-4.1.3-beta/mysql-test/var/log/mysqltest-time) :
> /home/blg/osr507/mysql-4.1.3-beta/client/.libs/mysqltest: At line 421: 
> Result length mismatch
> (the last lines may be the most important ones)
> Below are the diffs between actual and expected results:
> -------------------------------------------------------
> *** r/func_group.result Sat Jun 26 18:45:33 2004
> --- r/func_group.reject Sun Jun 27 02:23:15 2004
> ***************
> *** 576,582 ****
>   explain
>   select min(a1) from t1 where a1 != 'KKK';
>   id    select_type     table   type    possible_keys   key     key_len 
> ref    rows     Extra
> ! 1     SIMPLE  NULL    NULL    NULL    NULL    NULL    NULL    NULL    
> Impossible WHERE noticed after reading const tables
>   explain
>   select max(a3) from t1 where a2 < 2 and a3 < 'SEA';
>   id    select_type     table   type    possible_keys   key     key_len 
> ref    rows     Extra
> --- 576,582 ----
>   explain
>   select min(a1) from t1 where a1 != 'KKK';
>   id    select_type     table   type    possible_keys   key     key_len 
> ref    rows     Extra
> ! 1     SIMPLE  t1      range   PRIMARY PRIMARY 3       NULL    14      
> Using where; Using index
>   explain
>   select max(a3) from t1 where a2 < 2 and a3 < 'SEA';
>   id    select_type     table   type    possible_keys   key     key_len 
> ref    rows     Extra
> ***************
> *** 621,627 ****
>   explain
>   select concat(min(t1.a1),min(t2.a4)) from t1, t2 where t2.a4 <> 'AME';
>   id    select_type     table   type    possible_keys   key     key_len 
> ref    rows     Extra
> ! 1     SIMPLE  t2      ref     k2      k2      4       const   6       
> Using where; Using index
>   1     SIMPLE  t1      index   NULL    PRIMARY 3       NULL    14      
> Using index
>   drop table t1, t2;
>   create table t1 (USR_ID integer not null, MAX_REQ integer not null, 
> constraint PK_SEA_USER primary key (USR_ID)) engine=InnoDB;
> --- 621,627 ----
>   explain
>   select concat(min(t1.a1),min(t2.a4)) from t1, t2 where t2.a4 <> 'AME';
>   id    select_type     table   type    possible_keys   key     key_len 
> ref    rows     Extra
> ! 1     SIMPLE  t2      range   k2      k2      4       NULL    6       
> Using where; Using index
>   1     SIMPLE  t1      index   NULL    PRIMARY 3       NULL    14      
> Using index
>   drop table t1, t2;
>   create table t1 (USR_ID integer not null, MAX_REQ integer not null, 
> constraint PK_SEA_USER primary key (USR_ID)) engine=InnoDB;
> -------------------------------------------------------
> Please follow the instructions outlined at
> http://www.mysql.com/doc/en/Reporting_mysqltest_bugs.html
> to find the reason to this problem and how to report this.
> 
> Ending Tests
> Shutting-down MySQL daemon
> 
> Master shutdown finished
> Slave shutdown finished
> Resuming Tests

Fixed with bk as of 12:00 NDT 27 Jun 04
 
> key_cache                      [ fail ]
> 
> Errors are (from 
> /home/blg/osr507/mysql-4.1.3-beta/mysql-test/var/log/mysqltest-time) :
> /home/blg/osr507/mysql-4.1.3-beta/client/.libs/mysqltest: At line 159: 
> Result length mismatch
> (the last lines may be the most important ones)
> Below are the diffs between actual and expected results:
> -------------------------------------------------------
> *** r/key_cache.result Wed Jun 16 08:25:53 2004
> --- r/key_cache.reject Sun Jun 27 02:24:46 2004
> ***************
> *** 90,96 ****
>   Key_blocks_used       0
>   show status like 'key_blocks_unused';
>   Variable_name Value
> ! Key_blocks_unused     KEY_BLOCKS_UNUSED
>   insert into t1 values (1, 'qqqq'), (11, 'yyyy');
>   insert into t2 values (1, 1, 'qqqq'), (2, 1, 'pppp'),
>   (3, 1, 'yyyy'), (4, 3, 'zzzz');
> --- 90,96 ----
>   Key_blocks_used       0
>   show status like 'key_blocks_unused';
>   Variable_name Value
> ! Key_blocks_unused     1824
>   insert into t1 values (1, 'qqqq'), (11, 'yyyy');
>   insert into t2 values (1, 1, 'qqqq'), (2, 1, 'pppp'),
>   (3, 1, 'yyyy'), (4, 3, 'zzzz');
> ***************
> *** 111,117 ****
>   Key_blocks_used       4
>   show status like 'key_blocks_unused';
>   Variable_name Value
> ! Key_blocks_unused     KEY_BLOCKS_UNUSED
>   cache index t1 key (`primary`) in keycache1;
>   Table Op      Msg_type        Msg_text
>   test.t1       assign_to_keycache      status  OK
> --- 111,117 ----
>   Key_blocks_used       4
>   show status like 'key_blocks_unused';
>   Variable_name Value
> ! Key_blocks_unused     1820
>   cache index t1 key (`primary`) in keycache1;
>   Table Op      Msg_type        Msg_text
>   test.t1       assign_to_keycache      status  OK
> ***************
> *** 273,279 ****
>   Key_blocks_used       4
>   show status like 'key_blocks_unused';
>   Variable_name Value
> ! Key_blocks_unused     KEY_BLOCKS_UNUSED
>   set global keycache2.key_buffer_size=0;
>   set global keycache3.key_buffer_size=100;
>   set global keycache3.key_buffer_size=0;
> --- 273,279 ----
>   Key_blocks_used       4
>   show status like 'key_blocks_unused';
>   Variable_name Value
> ! Key_blocks_unused     1824
>   set global keycache2.key_buffer_size=0;
>   set global keycache3.key_buffer_size=100;
>   set global keycache3.key_buffer_size=0;
> -------------------------------------------------------
> Please follow the instructions outlined at
> http://www.mysql.com/doc/en/Reporting_mysqltest_bugs.html
> to find the reason to this problem and how to report this.
> 
> Ending Tests
> Shutting-down MySQL daemon
> 
> Master shutdown finished
> Slave shutdown finished
> Resuming Tests

Still failing.

> The rpl000001... tests (bug 3828) is still running after 2 hours.
> 
> The master.err log shows...
> CURRENT_TEST: rpl000001

This test never finished after 24 hours so I stopped tests to try latest 
bk.
 
> The slave.err log shows...
> 
> 040627  2:32:02  Warning: Got signal 16 from thread 10
> 040627  2:32:02  Slave I/O thread killed during or after a reconnect done 
> to recover from failed read
> 040627  2:32:02  Slave I/O thread exiting, read up to log 
> 'master-bin.000001', position 769321
> 
> It appears that the innodb bug that was fixed in mysql-4.0.19 is now back 
> since mysql-4.0.20 and mysql-4.1.2.  These tests used to be really quick.
> 
> I will post tomorrow the results because these tests now take 8-20 hours 
> where they took only a few minutes in mysql-4.1.1 and mysql-4.0.18.

As mention above this test never finished in 24 hours so I stopped it to 
test new bk.

Thanks,

--
Boyd Gerber <[email protected]>
ZENEZ	1042 East Fort Union #135, Midvale Utah  84047

-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]