Bug #76676 MTR should run testcases with --parallel=1 option automatically when inc file ex
Submitted: 13 Apr 2015 12:02 Modified: 11 Dec 2015 13:52
Reporter: Viswanatham Gudipati Email Updates:
Status: Closed Impact on me:
None 
Category:Tools: MTR / mysql-test-run Severity:S3 (Non-critical)
Version:5.6 OS:Any
Assigned to: CPU Architecture:Any

[13 Apr 2015 12:02] Viswanatham Gudipati
Description:
Problem : Currently with MTR testcase(s) containing this inc file : include/not_parallel.inc , they would get skipped from the PB2 machines. The reason being on PB2 machines testcase(s) will be run with --parallel=8 options (not less < 8).

In order to run those testcase(s) one has to add a MTR command in the collection files (default.push,default.weekly etc) as below mentioned

./mtr --parallel=1 --suite=InnoDB sample.test 

But add above such commands in collection files may not be a good solution. 

If the no of such testcase(s) are very high, in different suites (innodb,innodb_gis etc) , then adding a mtr command is not a good solutions , some times even user might for get.  

Hence t  

Hence MTR should have an intelligence to pick each such testcase(s) from different suites and get executed on PB2 machine(s) with --parallel=1 option automatically .
   

How to repeat:
./mtr --suite=InnoDB 

Suggested fix:
New enhancement required in MTR for testcase(s) which has include/not_parallel.inc
[11 Dec 2015 13:52] Paul DuBois
Fixed in 5.8.0.

Changes for test suite. No changelog entry needed.