August 2019 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2780) Fwd: [ovirt-devel] jenkins CI failing to fetch repo

by Anton Marchukov (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2780?page=com.atlassian.jir... ] Anton Marchukov reassigned OVIRT-2780: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Fwd: [ovirt-devel] jenkins CI failing to fetch repo > --------------------------------------------------- > > Key: OVIRT-2780 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2780 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Ehud Yonasi > Assignee: Evgheni Dereveanchin > > ---------- Forwarded message --------- > From: Miguel Duarte de Mora Barroso <mdbarroso(a)redhat.com> > Date: Thu, Aug 22, 2019 at 11:02 AM > Subject: [ovirt-devel] jenkins CI failing to fetch repo > To: oVirt devel <devel(a)ovirt.org>, oVirt Jenkins <jenkins(a)ovirt.org> > Hi, > Since yesterday I can't get ovirt-provider-ovn builds to run, each > manifesting the error below: > error: index-pack died of signal 15 > 09:27:35 fatal: index-pack failed > 09:27:35 > 09:27:35 at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) > 09:27:35 at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) > 09:27:35 at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) > 09:27:35 at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) > 09:27:35 at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:655) > 09:27:35 at > org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) > 09:27:35 at > org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) > 09:27:35 at hudson.remoting.UserRequest.perform(UserRequest.java:212) > 09:27:35 at hudson.remoting.UserRequest.perform(UserRequest.java:54) > 09:27:35 at hudson.remoting.Request$2.run(Request.java:369) > 09:27:35 at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > 09:27:35 at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 09:27:35 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 09:27:35 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 09:27:35 at java.lang.Thread.run(Thread.java:748) > 09:27:35 Suppressed: hudson.remoting.Channel$CallSiteStackTrace: > Remote call to vm0038.workers-phx.ovirt.org > 09:27:35 at > hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) > 09:27:35 at > hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) > 09:27:35 at hudson.remoting.Channel.call(Channel.java:957) > 09:27:35 at > org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) > 09:27:35 at sun.reflect.GeneratedMethodAccessor793.invoke(Unknown Source) > 09:27:35 at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 09:27:35 at java.lang.reflect.Method.invoke(Method.java:498) > 09:27:35 at > org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) > 09:27:35 at com.sun.proxy.$Proxy118.execute(Unknown Source) > 09:27:35 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1152) > 09:27:35 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192) > 09:27:35 at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124) > 09:27:35 at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93) > 09:27:35 at > org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) > 09:27:35 at > org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) > 09:27:35 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > 09:27:35 ... 4 more > It can be seen on: > - > https://jenkins.ovirt.org/job/ovirt-provider-ovn_standard-check-patch/247... > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/XOYJOK4AXT7... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

5 years, 2 months

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 930

by jenkins＠jenkins.phx.ovirt.org

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/930//artifact/exported... Cheers, Jenkins

5 years, 2 months

1
0
0 / 0

[CQ]: 102861, 1 (ovirt-host-deploy) failed "ovirt-4.3" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.3" change queue including change 102861,1 (ovirt-host-deploy) failed. However, this change seems not to be the root cause for this failure. Change 102426,5 (ovirt-host-deploy) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102426,5 (ovirt-host-deploy) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102861/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102426/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1918/

5 years, 2 months

1
0
0 / 0

[CQ]: 102839, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 102839,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 101913,10 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102839/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101913/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15580/

5 years, 2 months

1
0
0 / 0

[CQ]: 8af0004 (ovirt-ansible-vm-infra) failed "ovirt-master" system tests

by oVirt Jenkins

Change 8af0004 (ovirt-ansible-vm-infra) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-vm-infra/commit/8af000487c9442a3f0... For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15575/

5 years, 2 months

1
0
0 / 0

[CQ]: 101402, 10 (ovirt-engine-api-model) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 101402,10 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 102344,1 (ovirt-engine-api-model) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102344,1 (ovirt-engine-api- model) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/101402/10 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102344/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15572/

5 years, 2 months

1
0
0 / 0

[CQ]: 102860, 1 (ovirt-host-deploy) failed "ovirt-4.3" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.3" change queue including change 102860,1 (ovirt-host-deploy) failed. However, this change seems not to be the root cause for this failure. Change 102426,5 (ovirt-host-deploy) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102426,5 (ovirt-host-deploy) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102860/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102426/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1908/

5 years, 2 months

1
0
0 / 0

[CQ]: 101267, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 101267,8 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 101913,10 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/101267/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101913/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15569/

5 years, 2 months

1
0
0 / 0

[CQ]: 102761, 10 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 102761,10 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 101913,10 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102761/10 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101913/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15565/

5 years, 2 months

1
0
0 / 0

[CQ]: 98257, 23 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 98257,23 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 101913,10 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/98257/23 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101913/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15562/

5 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra August 2019