Re: [ovirt-devel] [lago-devel] ovirt tests failing on missing libxml2-python

2016-07-04 Thread Yaniv Kaul
On Sun, Jul 3, 2016 at 3:31 PM, Barak Korren wrote: > >> Maybe we can take a middle ground, pre-fetch, but also enable external > >> repos in CI (perhaps with some way to log and find out what was not > >> pre-fetched). > > > > This is what the code is supposed to do, I

Re: [ovirt-devel] [lago-devel] ovirt tests failing on missing libxml2-python

2016-07-03 Thread Barak Korren
>> Maybe we can take a middle ground, pre-fetch, but also enable external >> repos in CI (perhaps with some way to log and find out what was not >> pre-fetched). > > This is what the code is supposed to do, I suspect. reposync syncs between > what you already have and what you fetch, no? > Y. > I

Re: [ovirt-devel] [lago-devel] ovirt tests failing on missing libxml2-python

2016-07-01 Thread Yaniv Kaul
On Wed, Jun 29, 2016 at 11:15 PM, Barak Korren wrote: > On 29 June 2016 at 21:45, Yaniv Kaul wrote: > > On Mon, Jun 27, 2016 at 9:45 AM, Barak Korren > wrote: > >> > >> > > >> > > >> > It means that packages will be fetched EVERY time

Re: [ovirt-devel] [lago-devel] ovirt tests failing on missing libxml2-python

2016-06-29 Thread Barak Korren
On 29 June 2016 at 21:45, Yaniv Kaul wrote: > On Mon, Jun 27, 2016 at 9:45 AM, Barak Korren wrote: >> >> > >> > >> > It means that packages will be fetched EVERY time from outside, which >> > may be >> > slow(er). >> > Y. >> > >> >> We can (and mostly

Re: [ovirt-devel] [lago-devel] ovirt tests failing on missing libxml2-python

2016-06-29 Thread Yaniv Kaul
On Mon, Jun 27, 2016 at 9:45 AM, Barak Korren wrote: > > > > > > It means that packages will be fetched EVERY time from outside, which > may be > > slow(er). > > Y. > > > > We can (and mostly already have) setup simple caches to prevent that. > How do you set up cache on a

Re: [ovirt-devel] [lago-devel] ovirt tests failing on missing libxml2-python

2016-06-27 Thread Barak Korren
> > > It means that packages will be fetched EVERY time from outside, which may be > slow(er). > Y. > We can (and mostly already have) setup simple caches to prevent that. AFAIK CI slaves are cleaned every time anyway, so in practice there wouldn`t be much difference except we will have less