[MTR] Update the values of the MTR up to the current and long-term observed needs

Explanation of the options per:
https://dev.mysql.com/doc/dev/mysql-server/latest/PAGE_MYSQL_TEST_RUN_PL.html

--max-test-fail=N
  Stop execution after the specified number of tests have failed, to avoid
  using up resources (and time) in case of massive failures. retries are not
  counted. Defaults to 10, set to 0 for no limit.

--retry=N
  If a test fails, it is retried up to a maximum of N runs, but will terminate
  after 2 failures. Default is 3, set to 1 or 0 for no retries. This option has
  no effect unless --force is also used; without it, test execution will terminate
  after the first failure.
This commit is contained in:
Michal Schorm 2024-08-15 01:16:53 +02:00
parent ff887ad643
commit 9a8f94a4f3

View File

@ -773,7 +773,7 @@ export MTR_BUILD_THREAD=$(( $(date +%s) % 2200 ))
export common_testsuite_arguments=" %{?with_debug:--debug-server} \
--force --skip-combinations --report-unstable-tests --clean-vardir --nocheck-testcases \
--suite-timeout=900 --testcase-timeout=30 \
--parallel=auto --retry=2 --max-test-fail=5 "
--parallel=auto --retry=3 --max-test-fail=30 "
# If full testsuite has already been run on this version and we don't explicitly want the full testsuite to be run
if [[ "%{last_tested_version}" == "%{version}" ]] && [[ %{force_run_testsuite} -eq 0 ]]