mirror of
https://github.com/MariaDB/server.git
synced 2025-02-01 11:31:51 +01:00
2745978a9e
This patch aims at moving some rpl tests to be run on a daily basis instead of running on a per push basis. To accomplish such goal the following modifications are proposed: - MTR: added --skip-test-list cli parameter This option allows the user to specify more than one disabled.def file, for example: perl mtr --skip-test-list=list1.list --skip-test-list=list2.list - Added collections/disabled-per-push.list This file lists the test cases that should be disabled per push. - Changed mysql-test/collections/default.push Added --skip-test-list=collections/disabled-per-push.list to rpl_binlog_row, ps_row and n_mix runs. - Changed mysql-test/collections/default.daily Added rpl_binlog_row run (since it is partially run per push we should run it fully on a daily basis). |
||
|---|---|---|
| .. | ||
| default.daily | ||
| default.experimental | ||
| default.push | ||
| default.weekly | ||
| disabled-per-push.list | ||
| mysql-next-mr.push | ||
| mysql-trunk.push | ||
| README | ||
| README.experimental | ||
| test-bt | ||
| test-bt-debug | ||
| test-bt-debug-fast | ||
| test-bt-fast | ||
This directory contains collections of test runs that we run during our integration and release testing. Each file contains zero or more lines, with one invocation of mysql-test-run.pl on each. These invocations are written so that, with the assumption that perl is in your search path, any collection can run as a shell script or a batch file, with the parent mysql-test directory being the current working directory. During integration testing, we choose the collection to run by following these steps: 1) We choose the extension to look for, based on these rules: - If we're running a per-push test, we choose ".push" as the extension. - If we're running a daily test, we choose ".daily" as the extension. - If we're running a weekly test, we choose ".weekly" as the extension. 2) If there is a collection that has the same name as the branch we're testing plus the extension as determined in step 1, we choose that collection. 3) If the branch is unknown or we have removed all characters from it and still not found a matching collection, we choose the name "default" plus the extension determined in step 1. If there is no such file, we give up and don't test anything at all. 4) If we haven't found a collection yet, we remove the last character from the branch name and go back to step 2. 5) The commands from the collection are run line by line via execv() or similar system calls. They are not run as a shell script. Shell expansions are not guaranteed to work and most likely won't.