December 2016 - Infra - Ovirt List Archives

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4371 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_130_741767172.1482410173640 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4371/, Build Number: 4371, Build Status: FAILURE ------=_Part_130_741767172.1482410173640--

8 years

1
77
0 / 0

[JIRA] (OVIRT-985) Fix the way repoman deploy to experimental

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-985?page=com.atlassian.jira... ] eyal edri [Administrator] commented on OVIRT-985: ------------------------------------------------- [~gshinar] please add the relevant failing job ( mark it to keep forever ) and paste the exception here. > Fix the way repoman deploy to experimental > ------------------------------------------ > > Key: OVIRT-985 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-985 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > Please consult with Eyal on that. > No idea what should be done. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

8 years

1
0
0 / 0

[JIRA] (OVIRT-984) Add emails to deploy to experimental jobs

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-984?page=com.atlassian.jira... ] eyal edri [Administrator] reassigned OVIRT-984: ----------------------------------------------- Assignee: Pavel Zhukov (was: infra) > Add emails to deploy to experimental jobs > ----------------------------------------- > > Key: OVIRT-984 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-984 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Pavel Zhukov > > When deploy to experimental fails, we need to alert. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

8 years

1
0
0 / 0

[JIRA] (OVIRT-985) Fix the way repoman deploy to experimental

by Gil Shinar (oVirt JIRA)

Gil Shinar created OVIRT-985: -------------------------------- Summary: Fix the way repoman deploy to experimental Key: OVIRT-985 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-985 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra Please consult with Eyal on that. No idea what should be done. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

8 years

1
0
0 / 0

[JIRA] (OVIRT-984) Add emails to deploy to experimental jobs

by Gil Shinar (oVirt JIRA)

Gil Shinar created OVIRT-984: -------------------------------- Summary: Add emails to deploy to experimental jobs Key: OVIRT-984 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-984 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra When deploy to experimental fails, we need to alert. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

8 years

1
0
0 / 0

[JIRA] (OVIRT-983) Improve CI output for Jenkins repo

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-983: ---------------------------------- Summary: Improve CI output for Jenkins repo Key: OVIRT-983 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-983 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Since we've added more ci jobs to the {{jenkins}} repo, the CI output because unclear. When it was one job, it was easy to understand it failed because of YAML issues. Now, when it passes on all platforms but el7, its easy to mistake this for a infra failure on el7 rather then a real problem with the patch. The following improvements should be made to the job output: # The YAML failure message should be placed directly in the Gerrit comment, this can be done with the "Unsuccessful Message File" feature of the Gerrit plugin. # When YAML check succeeds ther sohuld be a message in Gerrit saying so and indicating where the DIFF output can be seen (will "Unsuccessful Message File" also work on success?) # The {{differences.html}} file should probably be called {{index.html}} to get it placed in the job status page. # Maybe add some javascript to {{differences.html}} to allow collapsing individual differences. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

8 years

1
0
0 / 0

[JIRA] (OVIRT-983) Improve CI output for Jenkins repo

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-983?page=com.atlassian.jira... ] Barak Korren updated OVIRT-983: ------------------------------- Epic Link: OVIRT-400 > Improve CI output for Jenkins repo > ---------------------------------- > > Key: OVIRT-983 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-983 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Since we've added more ci jobs to the {{jenkins}} repo, the CI output because unclear. When it was one job, it was easy to understand it failed because of YAML issues. Now, when it passes on all platforms but el7, its easy to mistake this for a infra failure on el7 rather then a real problem with the patch. > The following improvements should be made to the job output: > # The YAML failure message should be placed directly in the Gerrit comment, this can be done with the "Unsuccessful Message File" feature of the Gerrit plugin. > # When YAML check succeeds ther sohuld be a message in Gerrit saying so and indicating where the DIFF output can be seen (will "Unsuccessful Message File" also work on success?) > # The {{differences.html}} file should probably be called {{index.html}} to get it placed in the job status page. > # Maybe add some javascript to {{differences.html}} to allow collapsing individual differences. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

8 years

1
0
0 / 0

[VDSM] Testing vdsm master on Fedora 23?

by Nir Soffer

Hi all, For some reason we have a new job testing vdsm master/4.1 on Fedora 23. http://jenkins.ovirt.org/job/vdsm_4.1_check-patch-fc23-x86_64/2/ Fedora 23 is not support on vdsm master long time ago. Please remove this job. Thanks, Nir

8 years

3
2
0 / 0

oVirt infra daily report - unstable production jobs - 181

by jenkins＠jenkins.phx.ovirt.org

------=_Part_357_1053470227.1482793204575 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/181//artifact/exported... Cheers, Jenkins ------=_Part_357_1053470227.1482793204575 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 26/12/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_buil...">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x...">ovirt-system-tests_master_check-patch-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_system-tests/">ovirt_4.1_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_system-tests/">ovirt_master_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_ovirt_org</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  <br><br>Job disabled - The old Jenkins is probably not up any more </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> ------=_Part_357_1053470227.1482793204575--

8 years

1
0
0 / 0

[JIRA] (OVIRT-982) Fwd: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.1_el7_created/431

by Yevgeny Zaspitsky (oVirt JIRA)

Yevgeny Zaspitsky created OVIRT-982: --------------------------------------- Summary: Fwd: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.1_el7_cre... Key: OVIRT-982 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-982 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yevgeny Zaspitsky Assignee: infra Looks like a lot of jobs fail on similar problem. >From the job console log: git -c core.askpass=true fetch --tags --progress git://gerrit.ovirt.org/ovirt-engine.git refs/changes/93/67593/22 --prune ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException <http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitExcep...>: Failed to fetch from git://gerrit.ovirt.org/ovirt-engine.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:766) <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.git.GitSCM....> at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1022) <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.git.GitSCM....> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1053) <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.git.GitSCM....> at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:129) <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.mult...> at hudson.scm.SCM.checkout(SCM.java:485) <http://stacktrace.jenkins-ci.org/search/?query=hudson.scm.SCM.checkout&en...> at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractProje...> at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild...> at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) <http://stacktrace.jenkins-ci.org/search/?query=jenkins.scm.SCMCheckoutStr...> at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild...> at hudson.model.Run.execute(Run.java:1738) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute&e...> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuil...> at hudson.model.ResourceController.execute(ResourceController.java:98) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceContr...> at hudson.model.Executor.run(Executor.java:410) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run&...> Caused by: hudson.plugins.git.GitException <http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitExcep...>: Command "git -c core.askpass=true fetch --tags --progress git://gerrit.ovirt.org/ovirt-engine.git refs/changes/93/67593/22 --prune" returned status code 128: stdout: stderr: fatal: read error: Connection reset by peer at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1640) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1388) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:62) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:313) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:152) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:332) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ......remote call to vm0040.workers-phx.ovirt.org(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.UserResponse.retrieve(UserRequest.java:252) at hudson.remoting.Channel.call(Channel.java:781) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) at sun.reflect.GeneratedMethodAccessor452.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131) at com.sun.proxy.$Proxy60.execute(Unknown Source) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:764) ... 12 more ERROR: null -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

8 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra December 2016