mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 13:32:33 +01:00
c3018b0ff4
This includes fixing all utilities to not have any memory leaks, as safemalloc warnings stopped tests from passing on MacOSX. - Ensure that all clients takes character-set-dir, as the libmysqlclient library will use it. - mysql-test-run now passes character-set-dir to all external clients. - Changed dynstr_free() so that it can be called twice (made freeing code easier) - Changed rpl_global_gtid_slave_state to be allocated dynamicly as it includes a mutex that needs to be initizlied/destroyed before my_end() is called. - Removed rpl_slave_state::init() and rpl_slave_stage::deinit() as their job are better handling by constructor and delete. - Print alias instead of table_name in check_duplicate_key as table_name may have been converted to lower case. Other things: - Fixed a case in time_to_datetime_with_warn() where we where using && instead of & in tests |
||
---|---|---|
.. | ||
r | ||
t | ||
disabled.def | ||
README.txt |
Putting testcases here ~~~~~~~~~~~~~~~~~~~~~~ When you work on re-verifying or re-classifying a bug (not fixing it), it's a good idea to put the mtr-parsable '.test' testcase here. Benefits: 1) tests downloaded from the bugs db are sometimes close to mtr-parsable but not completely (for example if they contain /* comment */); when you re-verify or re-classify you run the test so may have to make it mtr-parsable; if you then put it in this suite, the developer who will work on this bug in a few weeks or months will not have to re-do the same download&fix, she/he can instead reuse your work. 2) Others can see how their own work influences many unsolved bugs, by running this suite. If they find that they fix a bug in this suite, we won't later wonder "how come this bug doesn't happen anymore, what fixed it?". 3) One can also run this suite with certain switches to see how they influence unsolved bugs: ./mtr --suite=optimizer_unfixed_bugs \ --mysqld=--optimizer_switch="firstmatch=off" Adding tests to this suite ~~~~~~~~~~~~~~~~~~~~~~~~~~ One test file per bug, named bugNNNNN.test. Put the correct (not current and buggy) result file in r/, so that "[ pass ]" in mtr will mean that a bug looks like fixed. When you have fixed a bug, remove files from this suite. t/bug45219.test is an example.