[ https://ovirt-jira.atlassian.net/browse/OVIRT-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37405#comment-37405 ] Barak Korren commented on OVIRT-2301: ------------------------------------- Nothing can be stuck for 6 days (we have timeouts defined) - if it is it means jenkins was shut down while it was running (which can cause pipeline jobs for freeze and not resume), and it should be aborted. Although by the looks of it, this might have run while using a buggy modified version of the pipeline code, [~dbelenky@redhat.com] can you confirm?

cq job stuck for 6 days -----------------------

Key: OVIRT-2301 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2301 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Labels: ost_failures, ost_infra

[~ederevea] noticed that this job has been stuck for 6 days: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2570/ The job got stuck while waiting for build-artifacts: http://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-4.2_change-queue-t... before he restarts jenkins I though [~bkorren@redhat.com] or [~dbelenky@redhat.com] would like to take a look. the job is still reported as active

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)