[
https://ovirt-jira.atlassian.net/browse/OVIRT-2301?page=com.atlassian.jir...
]
Barak Korren commented on OVIRT-2301:
-------------------------------------
The full job log tells you the right story:
{code}
Resuming build at Wed Jul 04 18:30:12 UTC 2018 after Jenkins restart
Waiting to resume part of ovirt-4.2_change-queue-tester #2570: ???
[Pipeline] End of Pipeline
java.lang.IllegalStateException: JENKINS-37121: something already locked
/home/jenkins/workspace/ovirt-4.2_change-queue-tester
at
org.jenkinsci.plugins.workflow.support.pickles.WorkspaceListLeasePickle$1.tryResolve(WorkspaceListLeasePickle.java:75)
at
org.jenkinsci.plugins.workflow.support.pickles.WorkspaceListLeasePickle$1.tryResolve(WorkspaceListLeasePickle.java:51)
at
org.jenkinsci.plugins.workflow.support.pickles.TryRepeatedly$1.run(TryRepeatedly.java:92)
at
jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
Caused: java.io.IOException: Failed to load build state
at
org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:854)
at
org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:852)
at
org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:906)
at
org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
at
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at
jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE
{code}
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-queu...
before he restarts jenkins I though [~bkorren(a)redhat.com] or [~dbelenky(a)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)