[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 120 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/120/ Build Number: 120 Build Status: Fixed Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 118 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/118/ Build Number: 118 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success:

[JIRA] (OVIRT-1772) s390x build support for oVirt infra

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35482#comment-35482 ] Barak Korren commented on OVIRT-1772: - An s390x VM has been added as a slave to both Jenkins instances.

[JIRA] (OVIRT-1772) s390x build support for oVirt infra

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1772: Blocked By: Code review Status: Blocked (was: In Progress) > s390x build support for

[JIRA] (OVIRT-1797) restart an OST suite at specific point (for development)

Greg Sheremeta created OVIRT-1797: - Summary: restart an OST suite at specific point (for development) Key: OVIRT-1797 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1797 Project: oVirt -

Re: [ovirt-devel] [ OST Failure Report ] [ oVirtMaster ] [ 07-11-2017 ] [007_sd_reattach.deactivate_storage_domain ]

On Fri, Dec 8, 2017 at 11:20 PM, Yaniv Kaul wrote: > > > On Fri, Dec 8, 2017 at 10:39 PM, Yaniv Kaul wrote: > >> >> >> On Fri, Dec 8, 2017 at 9:31 PM, Dafna Ron wrote: >> >>> I opened a bug:

Re: Change in ovirt-system-tests[master]: Run 'ss -anp' after engine-setup

On Sun, Dec 10, 2017 at 1:38 PM, Code Review wrote: > Jenkins CI posted comments on this change. > > View Change > > Patch set 1:Continuous-Integration -1 http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/2701/console : 11:37:51 + lvcreate -Zn

[JIRA] (OVIRT-1772) s390x build support for oVirt infra

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1772: Status: In Progress (was: To Do) > s390x build support for oVirt infra >

[JIRA] (OVIRT-1797) restart an OST suite at specific point (for development)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Sheremeta updated OVIRT-1797: -- Resolution: Duplicate Status: Done (was: To Do) > restart an OST suite at specific

[JIRA] (OVIRT-1797) restart an OST suite at specific point (for development)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35483#comment-35483 ] Greg Sheremeta commented on OVIRT-1797: --- Moved to https://ovirt-jira.atlassian.net/browse/OST-87 >

[JIRA] (OVIRT-1797) restart an OST suite at specific point (for development)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35484#comment-35484 ] Gal Ben Haim commented on OVIRT-1797: - The code in the link should work. When trying it, what is the

Re: Finding the "last successful" OST CI run of something

On Sun, Dec 10, 2017 at 3:43 PM, Yedidyah Bar David wrote: > Hi, > > I understand that OST (or the job(s) that run it in CI) has some logic > to decide what tests need to be ran based on the components that were > changed since the last run. > Indeed. OST have a tool that we

Finding the "last successful" OST CI run of something

Hi, I understand that OST (or the job(s) that run it in CI) has some logic to decide what tests need to be ran based on the components that were changed since the last run. Suppose that I want to see how the last good run of something looked like. Say the engine, or vdsm, or hosted-engine. Is

Re: Finding the "last successful" OST CI run of something

On 10 December 2017 at 15:43, Yedidyah Bar David wrote: > Hi, > > I understand that OST (or the job(s) that run it in CI) has some logic > to decide what tests need to be ran based on the components that were > changed since the last run. First you need to be clear about what

Re: Change in ovirt-system-tests[master]: Run 'ss -anp' after engine-setup

It's failing on ngn 4.1 suite, adding suite maintainers. On Sun, Dec 10, 2017 at 2:34 PM, Yedidyah Bar David wrote: > On Sun, Dec 10, 2017 at 1:38 PM, Code Review wrote: > > Jenkins CI posted comments on this change. > > > > View Change > > > > Patch set

4.1 OST - wrong dependency ?

Hi, I am running the OST on a private build and getting following dependency issue: *19:58:26* Error: Package: ovirt-engine-backend-4.1.8.1-0.0.master.20171210155452.git01b4ee6.el7.centos.noarch (alocalsync)*19:58:26*Requires: vdsm-jsonrpc-java >= 1.3.14*19:58:26*

Re: 4.1 OST - wrong dependency ?

On 10 December 2017 at 22:06, Ala Hino wrote: > Hi, > > I am running the OST on a private build and getting following dependency > issue: > > 19:58:26 Error: Package: > ovirt-engine-backend-4.1.8.1-0.0.master.20171210155452.git01b4ee6.el7.centos.noarch > (alocalsync) > 19:58:26