Bug #76347 innodb_stress : suites are to be run on mysql5.6 branche
Submitted: 17 Mar 2015 5:53 Modified: 26 Mar 2015 13:18
Reporter: Viswanatham Gudipati Email Updates:
Status: Closed Impact on me:
Category:Tests: Engine Severity:S3 (Non-critical)
Version:5.6 OS:Any
Assigned to: CPU Architecture:Any

[17 Mar 2015 5:53] Viswanatham Gudipati
The innodb_stress testcases are contributed by Mark C , these testcases are pushed and running on mysql-5.7 and trunk
branches ,the same suite should also run on mysql-5.6, hence need to push on 5.6.

Reason for 2 different patches of innodb_stress testcases:
The mysql code base of 5.7 is different from 5.6 and some of the innodb parameters are going to be depreciated (Ex: innodb_file_format)
from 5.7 onwards , hence the innodb_stress testcases of 5.7 and 5.6 are also little different. So in 5.6 branch , these testcases
are to run by setting the paramter innodb_file_format = Barracuda, whereas in 5.7 onwards, no need to set this parameter. 

* Look at the wl7703.
* mysql-5.7 and Trunk  :  innodb_file_format = Barracuda (default)
* mysql-5.6 : innodb_file_format = Antelope 

How to repeat:
New suite , need to push into 5.6 , not a defect 

Suggested fix:
New suite , need to push into 5.6 , not a defect
[8 Apr 2015 13:10] Paul Dubois
Noted in 5.6.25, 5.7.8, 5.8.0 changelogs.

MySQL distributions now include an innodb_stress suite of test cases.
Thanks to Mark Callaghan for the contribution.
[31 May 2015 19:33] Daniƫl van Eeden
It's merged in 5.6.25 https://github.com/mysql/mysql-server/tree/5.6/mysql-test/suite/innodb_stress
[23 Jun 2015 15:56] Laurynas Biveinis
commit 1347d3590c11c7d6ff2270ad9dfbc3285909f04c
Author: viswanatham <viswanatham.gudipati@oracle.com>
Date:   Wed Mar 18 15:42:13 2015 +0530

    A new testcases Innodb stress are being added