March 2016 - Infra - Ovirt List Archives

[ATN] old artifactory server is being shutdown

by Eyal Edri

FYI, We're shutting down old artifactory.ovirt.org server on alterway02 (isn't being used for a few months now), as we're using the new VM running on PHX. If no issues will arise in the following days the VM will be deleted as part of cleanup and the migration process to PHX. If you encounter any issues in the next few days with Jenkins regarding artifactory, please contact the infra team. /oVirt infra team.

8 years

1
0
0 / 0

[ATN] [ACTION REQUIRED] Tweaking engine CI flow

by Roy Golan

Hi all, Eyal and I sat together to analyse and tweak the engine CI and this is what we came up with: - dao test excludes updated - exclude dal/src/main/bundles from invoking dao tests A trivial update of validation messages without any db change would trigger dao test without any need. This is one less job run for lots of patches. This change is effective now. - Spare CI re-run on trivial rebases Gerrit trigger supports suppressing itself if the change to the tree was trivial. Most of the waste of resources(time and IO :) ) is around rebasing a change and waiting for CI to rerun. if Change1 is ci+1 and Change2 is ci+1 the chances that they will break CI together is very small and taking that risk is most probably worth it due to the huge resources waste This change isn't effective yet - *Please reply here* if you agree or not to make this change available. All of this is 'master' - 3.6 will follow if we will agree on activating that change. Thanks, Roy

8 years

4
6
0 / 0

[JIRA] (OVIRT-459) create ovirt-system-tests feature page on ovirt.org

by Yaniv Kaul (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-459?page=com.atlassian.jira... ] Yaniv Kaul commented on OVIRT-459: ---------------------------------- Ideally, yes. I'd separate the test plan (which I hope QE would add a bit) and a simple positive test case to see if we can test this functionality in ovirt-system-tests. > create ovirt-system-tests feature page on ovirt.org > ---------------------------------------------------- > > Key: OVIRT-459 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-459 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > We need to have a single page on ovirt.org to concentrate all ovirt-system-tests docs and plans per ovirt version. > Ideally we'll want a test plan attached to each feature page in oVirt 4.0 to start with. > [~ykaul] what do you think? -- This message was sent by Atlassian JIRA (v7.2.0-OD-04-029#72002)

8 years

1
0
0 / 0

jenkins logs and ovirt-engine_master_upgrade-from-master_el7_merged

by Yedidyah Bar David

Hi all, On Tue, Mar 29, 2016 at 11:12 PM, Jenkins CI <gerrit2(a)gerrit.ovirt.org> wrote: > Jenkins CI has posted comments on this change. > > Change subject: packaging: spec: Fix deps for ovirt-engine-tools-backup > ...................................................................... > > > Patch Set 2: > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_... : FAILURE This failed due to [1]. Above run 2500 contained the fix, but still failed. Why? Because it started from a broken build. The fix only fixes upgrades from good builds to good builds. I tried to follow the console logs of various runs of this job and have some questions: 1. How do we decide what version to upgrade *from*? 2. I suspect that we pick the last "good" version, with some definition of good, but by the time I am looking at this, there are already newer runs that succeeded, but all those before 2500 failed. Can't see in the web interface older non-failed ones. 3. Also searched my mail and could not find a report. When do we send email? To whom? Is there an archive somewhere? Not that important, now that all is fixed. Asking mainly for my own understanding. [1] https://bugzilla.redhat.com/1321249 > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_mer... : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/15... : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_64/... : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_unit-tests_merged/15408/ : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc23-x86_64... : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/55287 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-MessageType: comment > Gerrit-Change-Id: I2772037157f2f1ba77b3be96c6375558fe3d6582 > Gerrit-PatchSet: 2 > Gerrit-Project: ovirt-engine > Gerrit-Branch: master > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-HasComments: No -- Didi

8 years

2
3
0 / 0

No jobs triggered for this event

by Martin Perina

Hi, could you please take a look at the patch [1]? For some reason unknown to me any build job cannot be trigered for the patch neither automatically nor manually. Thanks Martin [1] https://gerrit.ovirt.org/55407

8 years

2
2
0 / 0

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 2346 - Failure!

by jenkins＠ovirt.org

------=_Part_255_1325727796.1458935120059 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_mer... Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_mer... Build Number: 2346 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/54228 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #2346 [Jakub Niedermertl] core: Console stealing fix [Sandro Bonazzola] otopi: add standard ci on master ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_255_1325727796.1458935120059--

8 years

1
45
0 / 0

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 2432 - Failure!

by jenkins＠ovirt.org

------=_Part_134_507391851.1458644250067 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_... Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_... Build Number: 2432 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/55011 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #2432 [Tomas Jelinek] webadmin: the HA flag was not shown in the edit instance type ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_134_507391851.1458644250067--

8 years

2
75
0 / 0

[JIRA] (OVIRT-456) Build oVirt 3.6.5 RC1

by sbonazzo (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-456?page=com.atlassian.jira... ] sbonazzo updated OVIRT-456: --------------------------- Assignee: sbonazzo (was: infra) Status: Accepted (was: New) > Build oVirt 3.6.5 RC1 > --------------------- > > Key: OVIRT-456 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-456 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: sbonazzo > Priority: Highest > -- This message was sent by Atlassian JIRA (v7.2.0-OD-04-029#72002)

8 years

1
0
0 / 0

DAO test

by Yevgeny Zaspitsky

Hi All, I renamed NetworkAttachmentDaoTest.java to NetworkAttachmentDaoImplTest.java (note the added "Impl") and Jenkins now includes the test in the regular unit-tests run rather than running that as a dao-unit-tests job. That causes test to fail as it cannot connect ot the tests DB. Where the logic of choosing the right configuration sits? Shouldn't any dal change trigger the dao tests rather than the regular ones? Yevgeny

8 years

3
3
0 / 0

[JIRA] (OVIRT-459) create ovirt-system-tests feature page on ovirt.org

by eyal edri [Administrator] (oVirt JIRA)

eyal edri [Administrator] created OVIRT-459: ----------------------------------------------- Summary: create ovirt-system-tests feature page on ovirt.org Key: OVIRT-459 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-459 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra We need to have a single page on ovirt.org to concentrate all ovirt-system-tests docs and plans per ovirt version. Ideally we'll want a test plan attached to each feature page in oVirt 4.0 to start with. [~ykaul] what do you think? -- This message was sent by Atlassian JIRA (v7.2.0-OD-04-029#72002)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra March 2016