Jenkins build is back to normal : ovirt_master_system-tests #906

See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: ovirt_4.0_he-system-tests #628

See Changes: [ngoldin] Enable debug mode in 'setup-ds.pl' [Gil Shinar] Changed ovirt version to 4.0 from 0.16 [Daniel Belenky] added 4.1 branch to the yaml conf -- [...truncated 748 lin

Build failed in Jenkins: ovirt_4.1_system-tests #35

See Changes: [ngoldin] Enable debug mode in 'setup-ds.pl' [Gil Shinar] Changed ovirt version to 4.0 from 0.16 [Daniel Belenky] added 4.1 branch to the yaml conf -- [...truncated 1014 lines.

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #196 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/196/, Build Number: 196, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #195 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/195/, Build Number: 195, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: ovirt_4.0_publish-rpms_nightly #293

See -- Started by timer [EnvInject] - Loading node environment variables. Building on master in workspace [WS-CLEANUP] Delet

Build failed in Jenkins: ovirt_3.6_publish-rpms_nightly #321

See -- Started by timer [EnvInject] - Loading node environment variables. Building on master in workspace [WS-CLEANUP] Delet

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4669/, Build Number: 4669, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4668 - SUCCESS!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4668/, Build Number: 4668, Build Status: SUCCESS___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

oVirt infra daily report - unstable production jobs - 196

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/196//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4667/, Build Number: 4667, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #194 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/194/, Build Number: 194, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #193 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/193/, Build Number: 193, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4666/, Build Number: 4666, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4665/, Build Number: 4665, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #192 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/192/, Build Number: 192, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4664/, Build Number: 4664, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #191 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/191/, Build Number: 191, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4663/, Build Number: 4663, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3669 - SUCCESS!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3669/, Build Number: 3669, Build Status: SUCCESS___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3668 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3668/, Build Number: 3668, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #190 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/190/, Build Number: 190, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #189 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/189/, Build Number: 189, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4662/, Build Number: 4662, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1015) kernel panic in nested VM

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25413#comment-25413 ] Evgheni Dereveanchin commented on OVIRT-1015: - I logged in to the builder to see i

[JIRA] (OVIRT-1015) kernel panic in nested VM

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25412#comment-25412 ] Evgheni Dereveanchin commented on OVIRT-1015: - The host has nothing specific in dm

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4661/, Build Number: 4661, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1015) kernel panic in nested VM

Evgheni Dereveanchin created OVIRT-1015: --- Summary: kernel panic in nested VM Key: OVIRT-1015 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1015 Project: oVirt - virtualization made easy

Re: upgrade job failures

Daniel, I suggest we'll remove this job for now as we're going to add the new suits in the coming days, So we'll avoid more noise from any issues that pop as a result of the 4.1/master mess. e. On Tue, Jan 10, 2017 at 6:32 PM, Vojtech Szocs wrote: > Hi, > > the patch that triggered the failed

Re: upgrade job failures

Hi, the patch that triggered the failed build is for ovirt-engine-4.1 branch and `yum -y install ovirt-engine` fails on dep. resolution because ovirt-engine-dashboard-1.2.0-0.1.20170105gitcb8e435.el7.centos.noarch Dashboard 1.y == Engine 4.y by convention. I guess the CI job has wrong repo? Th

Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #627

On Jan 10, 2017 6:18 PM, "Lev Veyde" wrote: Hi Yaniv, Sent a pull request to fix the issue, at least for our tests, by returning the SandyBridge CPU family: https://github.com/lago-project/lago/pull/424/ Yep, saw it. Milan - can you ensure it still OK with your servers? Y. Thanks in advanc

[no subject]

The last failure was in the engine upgrade phase [ ERROR ] Yum Cannot queue package iproute: Cannot find a valid baseurl for repo: epel/x86_64 I've re triggered the build, and it passed. On Tue, Jan 10, 2017 at 5:41 PM, Greg Sheremeta wrote: > Seems to be still not working. > > Greg Sheremet

Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #627

Hi Yaniv, Sent a pull request to fix the issue, at least for our tests, by returning the SandyBridge CPU family: https://github.com/lago-project/lago/pull/424/ Thanks in advance, Lev Veyde. - Original Message - From: "Yaniv Kaul" To: "Evgheni Dereveanchin" Cc: "Milan Zamazal" , "Lev V

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4660 - SUCCESS!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4660/, Build Number: 4660, Build Status: SUCCESS___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #188 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/188/, Build Number: 188, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Re: upgrade job failures

Seems to be still not working. Greg Sheremeta, MBA Red Hat, Inc. gsher...@redhat.com On Jan 10, 2017 10:31 AM, "Daniel Belenky" wrote: > Hi Greg, > > The error you see was caused by wrong RPMs in the snapshot repo. We are > currently working on new upgrade jobs that will replace the old ones. >

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4659/, Build Number: 4659, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Re: upgrade job failures

Hi Greg, The error you see was caused by wrong RPMs in the snapshot repo. We are currently working on new upgrade jobs that will replace the old ones. I've changed the configuration in Jenkins to take RPMs from latest.tested repo, and re-triggered the build. I assume that this should resolve the i

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4658/, Build Number: 4658, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Re: [JIRA] (OVIRT-1011) Please add omachace as project maintainer for ovirt-engine-sdk project on Github

You need to have a GitHub account for that, I couldn't find an account with your email address, Can you provide the user name? On Mon, Jan 9, 2017 at 4:10 PM, Ondra Machacek (oVirt JIRA) < j...@ovirt-jira.atlassian.net> wrote: > Ondra Machacek created OVIRT-1011: > ---

Re: [JIRA] (OVIRT-1012) ovirt-engine-sdk is build on el6 in following branches master, sdk_4.1 and sdk_4.0

You can send a patch to the project yaml file and exclude it in the build-artifacts section. for e.g: exclude: - version: master distro: el6 - version: 4.1 distro: el6 - version: 4.0 distro: fc24 - version: 4.0 distro: el6 On Mon, Jan 9,

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25409#comment-25409 ] Barak Korren commented on OVIRT-1014: - {quote} the translation of *.pacakges to yum comman

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25408#comment-25408 ] danken commented on OVIRT-1014: --- the translation of *.pacakges to yum command may include more t

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #186 - SUCCESS!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/186/, Build Number: 186, Build Status: SUCCESS___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25407#comment-25407 ] Barak Korren commented on OVIRT-1014: - {quote} could work for me. But I would like to be a

Re: CI not running on ovirt-engine-dashboard-1.1 branch

Im sorry, I meant to this job: http://jenkins.ovirt.org/job/ovirt-engine-dashboard_master_check-patch-el7-x86_64/ On Tue, Jan 10, 2017 at 4:15 PM, Daniel Belenky wrote: > Hi Greg, > > It seems that this is the first patch for this branch, and I see it was > sent at Jan 5th. The corresponding Jen

Re: CI not running on ovirt-engine-dashboard-1.1 branch

Hi Greg, It seems that this is the first patch for this branch, and I see it was sent at Jan 5th. The corresponding Jenkins job http://jenkins.ovirt.org/job/ovirt-engine-dashboard_4.1_check-merged-el7-x86_64/ was also created at Jan 5th, so maybe you've sent your patch before the job was created?

Re: CI not running on ovirt-engine-dashboard-1.1 branch

On Tue, Jan 10, 2017 at 4:00 PM, Greg Sheremeta wrote: > Hi, > > Even after [3] was merged, no CI is running on [1] and [2]. > I tried "Re-run hooks: all" but no luck. > > Any ideas? Something else I need to do? > Do you have check-patch.sh under your 4.1 branch in automation dir? Also, I do se

upgrade job failures

Hi, What do I need to do to fix this? "Error: Package: ovirt-engine-dashboard-1.2.0-0.1.20170105gitcb8e435.el7.centos.noarch (upgrade_to_0) Requires: ovirt-engine-webadmin-portal >= 4.2 " http://jenkins.ovirt.org/job/ovirt-engine_4.1_upgrade-from-3.6_el7_merged/129/console -- Gr

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25405#comment-25405 ] danken commented on OVIRT-1014: --- We are using symlinks when possible. #include "./check-patch

CI not running on ovirt-engine-dashboard-1.1 branch

Hi, Even after [3] was merged, no CI is running on [1] and [2]. I tried "Re-run hooks: all" but no luck. Any ideas? Something else I need to do? Greg [1] https://gerrit.ovirt.org/#/c/69731/ [2] https://gerrit.ovirt.org/#/c/69735/ [3] https://gerrit.ovirt.org/#/c/69737/ -- Greg Sheremeta, MBA

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #185 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/185/, Build Number: 185, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4656 - SUCCESS!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4656/, Build Number: 4656, Build Status: SUCCESS___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #184 - SUCCESS!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/184/, Build Number: 184, Build Status: SUCCESS___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #627

On Tue, Jan 10, 2017 at 3:14 PM, Evgheni Dereveanchin wrote: > Not sure what the initial problem was, but on my laptop (Haswell-MB) > I always use the lowest possible CPU family to ensure it's using > as few features as possible in nested VMs: > ;-) I'm doing the exact opposite, for two reasons

Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #627

Not sure what the initial problem was, but on my laptop (Haswell-MB) I always use the lowest possible CPU family to ensure it's using as few features as possible in nested VMs: core2duo Respectively, I use model_Conroe on oVirt side and didn't have problems with it. Do we really nee

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25404#comment-25404 ] Barak Korren edited comment on OVIRT-1014 at 1/10/17 3:15 PM: -- Th

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25404#comment-25404 ] Barak Korren commented on OVIRT-1014: - This had been asked for before. If the files are e

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4655/, Build Number: 4655, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages

danken created OVIRT-1014: - Summary: avoid repetition in automation/*packages Key: OVIRT-1014 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 Project: oVirt - virtualization made easy Issue T

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4654/, Build Number: 4654, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-754) Guest name 'TestNode-node' is already in use.

[ https://ovirt-jira.atlassian.net/browse/OVIRT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-754: -- Assignee: Evgheni Dereveanchin (was: infra) > Guest name 'TestNode-node' is a

Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #627

Yaniv Kaul writes: > On Tue, Jan 10, 2017 at 12:45 PM, Milan Zamazal wrote: > >> Yaniv Kaul writes: >> >> > On Tue, Jan 10, 2017 at 12:08 PM, Lev Veyde wrote: >> > >> >> This patch is one that caused it probably: >> >> https://github.com/lago-project/lago/commit/ >> 05ccf7240976f91b0c14d6a1f88

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4653/, Build Number: 4653, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #627

On 10 January 2017 at 12:23, Yaniv Kaul wrote: > > > On Tue, Jan 10, 2017 at 12:08 PM, Lev Veyde wrote: >> >> This patch is one that caused it probably: >> >> https://github.com/lago-project/lago/commit/05ccf7240976f91b0c14d6a1f88016376d5e87f0 > > > +Milan. > > I must confess that I did not like

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #183 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/183/, Build Number: 183, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4652 - SUCCESS!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4652/, Build Number: 4652, Build Status: SUCCESS___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #182 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/182/, Build Number: 182, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #181 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/181/, Build Number: 181, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4651/, Build Number: 4651, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #627

On Tue, Jan 10, 2017 at 12:45 PM, Milan Zamazal wrote: > Yaniv Kaul writes: > > > On Tue, Jan 10, 2017 at 12:08 PM, Lev Veyde wrote: > > > >> This patch is one that caused it probably: > >> https://github.com/lago-project/lago/commit/ > 05ccf7240976f91b0c14d6a1f88016 > >> 376d5e87f0 > > > > > >

Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #627

Yaniv Kaul writes: > On Tue, Jan 10, 2017 at 12:08 PM, Lev Veyde wrote: > >> This patch is one that caused it probably: >> https://github.com/lago-project/lago/commit/05ccf7240976f91b0c14d6a1f88016 >> 376d5e87f0 > > > +Milan. +Martin > I must confess that I did not like the patch to begin with

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4650 - SUCCESS!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4650/, Build Number: 4650, Build Status: SUCCESS___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #180 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/180/, Build Number: 180, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #627

On Tue, Jan 10, 2017 at 12:08 PM, Lev Veyde wrote: > This patch is one that caused it probably: > https://github.com/lago-project/lago/commit/05ccf7240976f91b0c14d6a1f88016 > 376d5e87f0 +Milan. I must confess that I did not like the patch to begin with... I did not understand what real problem

Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #627

This patch is one that caused it probably: https://github.com/lago-project/lago/commit/05ccf7240976f91b0c14d6a1f88016376d5e87f0 Thanks in advance, Lev Veyde. - Original Message - From: "Lev Veyde" To: "Eyal Edri" , sbona...@redhat.com Cc: infra@ovirt.org, "Gal Ben Haim" Sent: Tuesday, J

Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #627

Hi, Checked the logs and see the following: 02:42:05 [WARNING] OVF does not contain a valid image description, using default. 02:42:05 The following CPU types are supported by this host: 02:42:05 - model_Westmere: Intel Westmere Family 02:42:05 - model_N

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

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4649/, Build Number: 4649, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-914) Better arch support for mock_runner.sh

[ https://ovirt-jira.atlassian.net/browse/OVIRT-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-914: --- Labels: mock_runner.sh standard-ci (was: ) > Better arch support for mock_runner.sh > --

[JIRA] (OVIRT-1013) Automate standard-CI job creation

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25400#comment-25400 ] Barak Korren commented on OVIRT-1013: - Since this may be a developer-visible change, a mes

[JIRA] (OVIRT-1013) Automate standard-CI job creation

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1013: Labels: standard-ci (was: ) > Automate standard-CI job creation > ---

[JIRA] (OVIRT-1013) Automate standard-CI job creation

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1013: Description: The premise of the CI standard is simple: The developers place simple script in the

[JIRA] (OVIRT-1013) Automate standard-CI job creation

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1013: Epic Link: OVIRT-400 > Automate standard-CI job creation > - > >

[JIRA] (OVIRT-1013) Automate standard-CI job creation

Barak Korren created OVIRT-1013: --- Summary: Automate standard-CI job creation Key: OVIRT-1013 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 Project: oVirt - virtualization made easy Is

[JIRA] (OVIRT-894) Add support of secrets and credentials in Standard-CI

[ https://ovirt-jira.atlassian.net/browse/OVIRT-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-894: --- Summary: Add support of secrets and credentials in Standard-CI (was: Add support of sercers and cred