[
https://ovirt-jira.atlassian.net/browse/OVIRT-2853?page=com.atlassian.jir...
]
Dusan Fodor edited comment on OVIRT-2853 at 1/9/20 8:59 AM:
------------------------------------------------------------
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.
was (Author: dfodor):
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 in infra issue.
ovirt-engine standard checkpatch times out when doing release build
-------------------------------------------------------------------
Key: OVIRT-2853
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-2853
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: Dusan Fodor
Assignee: infra
Labels: infra
Link to the job:
https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine_standar...
It failed on timeout (3hrs), but the job it triggered [1] finished successfully (in 5+hrs
though). This is special case of release build which builds all possible
permutations-option BUILD_GWT is enabled in [2].
[1]
https://jenkins.ovirt.org/job/ovirt-engine_4.3_check-patch-el7-x86_64/649/
[2]
https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=automation/ch...
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100118)