Skip to content

Reduce retry rate when running in parallel - part I

Sofia Vistas requested to merge parallel-retry-rate1 into master

What does this MR do and why?

This MR introduces a series of changes that need to be in place to enable the parallelization of tests. There are issues with concurrency due to some test and framework design that when run in parallel increase the retry rate of the tests (the tests don't run in parallel when retried). The MR is focusing on:

  • Create unique runners so we fix the clash when using the same runner - it causes increase of load in the runner and delay in the tests;
  • Avoid running docker services on the same host port - it can clash if two tests with different services are running at the same time

Retry rate before with parallel enabled and after this fix:

Screenshot 2024-10-02 at 22.21.55.png

️ Note: Parallel is enabled on the code but should be disabled before merging

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Sofia Vistas

Merge request reports

Loading