Skip to content

ci: continue stress run'n'monitor

When we launch the tool over a pipeline that has some jobs already completed, it only triggers the jobs missing, to complete the task. If the target is divided into two sets (ones non-started, others completed) the tool is triggering the non-started and lists the completed like if they were completed during this execution.

But the behavior on the stress test is inconsistent, and it triggers n times all the jobs, no matter if they ran already.

With this change, the tool checks if there are prior executions of the jobs. Then it will finish with the jobs having the commanded number of runs (or more if there already were).


On a pipeline where the stress test was already launched, a command like:

./bin/ci/ci_run_n_monitor.sh --pipeline-url https://gitlab.freedesktop.org/mesa/mesa/-/pipelines/1187626 --target '.*adl.*' --stress 2

outputs directly a summary because the previous runs are kept:

image

But if we add the --force-manual it will trigger those manual jobs two times. Without wasting resources with the other ran jobs.

Also, setting --stress 5 it will only trigger the jobs that have less retries than this number.

Merge request reports