Actions
action #175482
closedcoordination #102906: [saga][epic] Increased stability of tests with less "known failures", known incompletes handled automatically within openQA
coordination #175515: [epic] incomplete jobs with "Failed to find an available port: Address already in use"
jobs incomplete with auto_review:"setup failure: isotovideo can not be started" - why did no tests prevent this to be deployed on both o3+osd?
Description
Observation¶
today's osd deployment triggered https://gitlab.suse.de/openqa/osd-deployment/-/jobs/3659163#L22 which does
$ for i in {1..7}; do curl -S -s http://jenkins.qa.suse.de/job/monitor-openQA_in_openQA-TW/lastCompletedBuild/api/json | jq -e 'select(.result=="SUCCESS")' >/dev/null && break || (echo "Retry $i after sleep ..." && sleep 300); done
Retry 1 after sleep ...
Retry 2 after sleep ...
Retry 3 after sleep ...
Retry 4 after sleep ...
Retry 5 after sleep ...
Retry 6 after sleep ...
Retry 7 after sleep ...
Cleaning up project directory and file based variables 00:01
Job succeeded
the according jenkins job is http://jenkins.qa.suse.de/job/monitor-openQA_in_openQA-TW/28665/ which is correctly failed. I think the evaluation in the for loop is wrong. We run out of retries and consider that success.
Actions