Mirrors
/
mariadb
mirror of https://github.com/MariaDB/server
3
0
Fork 0
Code Releases Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
77312 Commits
3225 Branches
1092 Tags
1.3 GiB
 
 
 
 
 
 
Tree: cd92bc38a7
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'cd92bc38a7'
${ noResults }
mariadb/storage/pbxt/mysql-test/main
Sergei Golubchik cd92bc38a7
start using jemalloc 		12 years ago
..
r mysql-test: sys_vars stub for a new xtradb config variable; tc_log_mmap test; 13 years ago
t mysql-test: sys_vars stub for a new xtradb config variable; tc_log_mmap test; 13 years ago
README pbxt suite is now a main-pbxt overlay 14 years ago
disabled.def misc test/result fixes 14 years ago
init_file.sql pbxt suite is now a main-pbxt overlay 14 years ago
suite.opt pbxt suite is now a main-pbxt overlay 14 years ago
suite.pm pbxt suite is now a main-pbxt overlay 14 years ago

README 

There are two ways to make an overlay to test a new storage engine: inclusive
and exclusive.

In the inclusive approach one would create have_pbxt.inc, and the corresponding
have_pbxt.opt. And for every test from the main suite that should run in the
overlay, one would need a wrapper like

=====[create.test]======
source have_pbxt.inc;
source create.test;
drop database pbxt;
========================

The last line is needed, because pbxt creates 'pbxt' database automatically,
and we need to remove it to pass the after-test check.

In the exclusive approach, one would create my.cnf or suite.opt - this affects
all tests, so mtr would run *all* tests of the main suite with the new options.
And one would use disabled.def to selectively disable tests and
--init-file option to create the database pbxt before the before-test check
(then we won't need to drop it at the end of the test).