it never reappeared, so the original timeout remained in place

@Dusan Fodor please change timeouts as needed, I think me and Ehud have provided enough information for you to proceed.

for infra issue i am not certain, we need to ask Evgheni maybe. because 2 runs produced the same results.

so if it’s only decided in the stage itself, I think that’s safe enough to limit for 5h. you can’t alter it on runtime..

Then we would have the same 5hrs timeout for all the builds (even the non release ones, which have less permutation and take less time), so i'm not sure that good enough solution. Extending the timeout only for the release build only would be better, but it is only decided in build_artifacts.sh how many permutation will it do, so already below level of stages.
Also, i don't remember seeing this before, so it might've been an infra issue.

You can define stages in the stdci.yaml file and under the build-artifacts stage you can define:

timeout: 5h

meanwhile the job was retriggered to see if this was a one-time issue (which might be the case as i don’t recall seeing this before)
https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/2974/console