Thanks for reporting Nir,
You are right about the timeout - but that exists only during the actual
code. In this case the slave was
somehow out of storage / memory and it stuck during loading our stdci code.
On Wed, May 13, 2020 at 6:50 PM Nir Soffer (oVirt JIRA) <
jira(a)ovirt-jira.atlassian.net> wrote:
Nir Soffer created OVIRT-2940:
---------------------------------
Summary: Stuck job - running 8 days
Key: OVIRT-2940
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-2940
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Nir Soffer
Assignee: infra
I found this stuck job in jenkins:
https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/5660/
Don't we have a timeout for killing run away jobs?
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100126)
_______________________________________________
Infra mailing list -- infra(a)ovirt.org
To unsubscribe send an email to infra-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/SNPYOWBWMMM...