Re: [ovirt-devel] Automation CI for vdsm

On 31 January 2016 at 14:15, Eyal Edri wrote: > Adding lago-devel. > Anyone from Lago project can help debug why it is taking so long to setup > Lago (1:17 hours?) > Simple, Lago downloads some big images and does a full sync of some large package repos... Most of that should be

Re: [ovirt-devel] Automation CI for vdsm

I have an unstable temporary repo with el6, el7, fc22 and fc23 images that weight ~ 300 mb and are updated to latest packages, working on get it properly generated and be able to replace all the current images, that should ease the first init, but the reposetup is still an issue, you might

Re: [ovirt-devel] Automation CI for vdsm

Adding lago-devel. Anyone from Lago project can help debug why it is taking so long to setup Lago (1:17 hours?) Yaniv, was this run done only on CI, or someone tried to run it locally on a baremetal server / laptop? e. On Tue, Dec 22, 2015 at 2:50 PM, Yaniv Bronheim wrote:

Re: [ovirt-devel] Automation CI for vdsm

Hi, OVSNetworkTest requires vdsm-hook-ovs installed (tests are not skipped if the package is not installed) and openvswitch service running (not started automatically). NetworkTest are not able to run together with OVSNetworkTest since we are doing ugly inheritance hacking there. My apologize for

Re: [ovirt-devel] Automation CI for vdsm

Nice, but we cannot enable this until all the tests pass or disabled. There is no point in broken or flaky functional tests. On Wed, Dec 16, 2015 at 5:34 PM, Yaniv Bronheim wrote: > So its not stable. It won't block merges and at least give us report after > each merge. It

Re: [ovirt-devel] Automation CI for vdsm

exactly - just posted a patch again that sings all fails as broken . we'll get the report soon and I'll publish it as well. hope the run will take less time now On Wed, Dec 16, 2015 at 6:19 PM, Nir Soffer wrote: > Nice, but we cannot enable this until all the tests pass or

Re: [ovirt-devel] Automation CI for vdsm

I like the idea but I have the same feelings as Francesco. I think that we need to make sure that functional tests for each vertical are stable before enabling this process. On Sun, Dec 13, 2015 at 8:34 AM, Eyal Edri wrote: > adding also infra team for visibility on the change

Re: [ovirt-devel] Automation CI for vdsm

adding also infra team for visibility on the change in CI. also inline. On Fri, Dec 11, 2015 at 4:19 PM, Francesco Romani wrote: > - Original Message - > > From: "Yaniv Bronheim" > > To: devel@ovirt.org, "Francesco Romani" ,

Re: [ovirt-devel] Automation CI for vdsm

- Original Message - > From: "Yaniv Bronheim" > To: devel@ovirt.org, "Francesco Romani" , "Nir Soffer" > , "Piotr Kliczewski" > > Cc: "danken" , "David Caro" , "Eyal

[ovirt-devel] Automation CI for vdsm

Hi all, We want to run functional tests as part of Vdsm CI for each patch before merge. Therefore we need to declare how to automate this process without overloading our jenkins machines. The functional tests will run using lago (https://github.com/ovirt/lago) - It will initiate multiply vms,