Improve socket binding related tests by varying the port
Currently, test jobs fail because they run in parallel and some of the tests try to bind to a specific port for the test. As this port is more or less hardcoded in the configuration, starting the same test at the same time in two or more jobs in parallel leads to failures.
One possible solution is to add variation to the port numbers by adjusting them based on an offset based on the job number or runner id for example.
-
adapt test configurations using scons and the
CI_RUNNER_IDand/or theCI_JOB_ID - check if backend services like databases need a similar handling, either by using different service names or ports