Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-06 Thread Roman Bogorodskiy
Daniel P. Berrange wrote: > On Mon, Jul 03, 2017 at 05:20:13PM +0400, Roman Bogorodskiy wrote: > > Ján Tomko wrote: > > > > > [cc: Guido] > > > > > > On Sat, Jul 01, 2017 at 02:18:58PM +0400, Roman Bogorodskiy wrote: > > > > Andrea Bolognani wrote: > > > >> virnetsockettest also fails prett

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-06 Thread Daniel P. Berrange
On Mon, Jul 03, 2017 at 05:20:13PM +0400, Roman Bogorodskiy wrote: > Ján Tomko wrote: > > > [cc: Guido] > > > > On Sat, Jul 01, 2017 at 02:18:58PM +0400, Roman Bogorodskiy wrote: > > > Andrea Bolognani wrote: > > >> virnetsockettest also fails pretty often for me, certainly > > >> more than yo

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-06 Thread Guido Günther
On Tue, Jul 04, 2017 at 12:27:19PM +0200, Andrea Bolognani wrote: > On Mon, 2017-07-03 at 18:47 +0200, Guido Günther wrote: > > > > Anyway, I'll try to find a way to debug what's going on with > > > > virnetsockettest. > > >  > > > IIRC Debian disabled this test years ago. > > >  > > > Guido, have

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-04 Thread Daniel P. Berrange
On Tue, Jul 04, 2017 at 06:26:22PM +0100, Daniel P. Berrange wrote: > On Tue, Jul 04, 2017 at 05:32:03PM +0100, Daniel P. Berrange wrote: > > On Tue, Jul 04, 2017 at 12:21:21PM +0100, Daniel P. Berrange wrote: > > So I did some debugging and this is wierder than I can imagine possible. > > > > I p

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-04 Thread Daniel P. Berrange
On Tue, Jul 04, 2017 at 05:32:03PM +0100, Daniel P. Berrange wrote: > On Tue, Jul 04, 2017 at 12:21:21PM +0100, Daniel P. Berrange wrote: > > On Tue, Jul 04, 2017 at 01:03:52PM +0200, Andrea Bolognani wrote: > > > On Sat, 2017-07-01 at 14:18 +0400, Roman Bogorodskiy wrote: > > > > > qemuxml2argvtes

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-04 Thread Daniel P. Berrange
On Tue, Jul 04, 2017 at 12:21:21PM +0100, Daniel P. Berrange wrote: > On Tue, Jul 04, 2017 at 01:03:52PM +0200, Andrea Bolognani wrote: > > On Sat, 2017-07-01 at 14:18 +0400, Roman Bogorodskiy wrote: > > > > qemuxml2argvtest fails consistently in my FreeBSD guest. > > >  > > > I guess that's caused

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-04 Thread Daniel P. Berrange
On Tue, Jul 04, 2017 at 01:03:52PM +0200, Andrea Bolognani wrote: > On Sat, 2017-07-01 at 14:18 +0400, Roman Bogorodskiy wrote: > > > qemuxml2argvtest fails consistently in my FreeBSD guest. > >  > > I guess that's caused by clang inlining functions that are mocked > > (specifically, some numa rela

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-04 Thread Andrea Bolognani
On Sat, 2017-07-01 at 14:18 +0400, Roman Bogorodskiy wrote: > > qemuxml2argvtest fails consistently in my FreeBSD guest. >  > I guess that's caused by clang inlining functions that are mocked > (specifically, some numa related stuff); I think that was discussed > several times already. Anyway, it s

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-04 Thread Andrea Bolognani
On Mon, 2017-07-03 at 18:47 +0200, Guido Günther wrote: > > > Anyway, I'll try to find a way to debug what's going on with > > > virnetsockettest. > >  > > IIRC Debian disabled this test years ago. > >  > > Guido, have you ever discovered the cause? >  > No, sorry. I diabled it ages ago since it fa

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-03 Thread Guido Günther
On Mon, Jul 03, 2017 at 10:49:46AM +0200, Ján Tomko wrote: > [cc: Guido] > > On Sat, Jul 01, 2017 at 02:18:58PM +0400, Roman Bogorodskiy wrote: > > Andrea Bolognani wrote: > > > virnetsockettest also fails pretty often for me, certainly > > > more than your figure; even if that wasn't the case, 1

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-03 Thread Roman Bogorodskiy
Ján Tomko wrote: > [cc: Guido] > > On Sat, Jul 01, 2017 at 02:18:58PM +0400, Roman Bogorodskiy wrote: > > Andrea Bolognani wrote: > >> virnetsockettest also fails pretty often for me, certainly > >> more than your figure; even if that wasn't the case, 1/5 > >> failure rate is way too high for

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-03 Thread Ján Tomko
[cc: Guido] On Sat, Jul 01, 2017 at 02:18:58PM +0400, Roman Bogorodskiy wrote: Andrea Bolognani wrote: virnetsockettest also fails pretty often for me, certainly more than your figure; even if that wasn't the case, 1/5 failure rate is way too high for a CI job. I played a little more with vi

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-07-01 Thread Roman Bogorodskiy
Andrea Bolognani wrote: > On Fri, 2017-06-30 at 14:19 +0100, Daniel P. Berrange wrote: > > > > Not all builders run all jobs, eg. the test suite is skipped > > > > on FreeBSD, but they all at least compile the library. > > >  > > > Is there any specific reason why it doesn't run test suite on Fr

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-06-30 Thread Andrea Bolognani
On Fri, 2017-06-30 at 14:19 +0100, Daniel P. Berrange wrote: > > > Not all builders run all jobs, eg. the test suite is skipped > > > on FreeBSD, but they all at least compile the library. > >  > > Is there any specific reason why it doesn't run test suite on FreeBSD? > > Generally, '(g)make check'

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-06-30 Thread Daniel P. Berrange
On Fri, Jun 30, 2017 at 05:45:04PM +0200, Andrea Bolognani wrote: > On Fri, 2017-06-30 at 14:19 +0100, Daniel P. Berrange wrote: > > > > Not all builders run all jobs, eg. the test suite is skipped > > > > on FreeBSD, but they all at least compile the library. > > >  > > > Is there any specific rea

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-06-30 Thread Daniel P. Berrange
On Fri, Jun 30, 2017 at 05:11:09PM +0400, Roman Bogorodskiy wrote: > Andrea Bolognani wrote: > > > On Thu, 2017-06-29 at 09:04 +0200, Daniel Veillard wrote: > > > BTW what is the list of platfdorms we compile on in CentOS CI ? > > > >   * CentOS 6 and 7 > >   * Fedora 23, 24, 25 and rawhide > >

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-06-30 Thread Roman Bogorodskiy
Andrea Bolognani wrote: > On Thu, 2017-06-29 at 09:04 +0200, Daniel Veillard wrote: > > BTW what is the list of platfdorms we compile on in CentOS CI ? > >   * CentOS 6 and 7 >   * Fedora 23, 24, 25 and rawhide >   * Debian (oldstable?) >   * FreeBSD (11?) > > https://ci.centos.org/view/libvir

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-06-29 Thread Daniel P. Berrange
On Thu, Jun 29, 2017 at 12:13:40PM +0200, Andrea Bolognani wrote: > On Thu, 2017-06-29 at 09:04 +0200, Daniel Veillard wrote: > > BTW what is the list of platfdorms we compile on in CentOS CI ? > >   * CentOS 6 and 7 >   * Fedora 23, 24, 25 and rawhide >   * Debian (oldstable?) >   * FreeBSD (11?)

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-06-29 Thread Andrea Bolognani
On Thu, 2017-06-29 at 09:04 +0200, Daniel Veillard wrote: > BTW what is the list of platfdorms we compile on in CentOS CI ?   * CentOS 6 and 7   * Fedora 23, 24, 25 and rawhide   * Debian (oldstable?)   * FreeBSD (11?) https://ci.centos.org/view/libvirt/job/libvirt-master-build/ Not all builders

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-06-29 Thread Daniel Veillard
On Thu, Jun 29, 2017 at 08:39:45AM +0200, Andrea Bolognani wrote: > On Wed, 2017-06-28 at 22:23 +0200, Daniel Veillard wrote: > >   Slightly late so little advance warning see my mail earlier today, > > I have now tagged RC1 in git head and pushed signed tarball and rpms > > to the usual place: > >

Re: [libvirt] Entering freeze for libvirt-3.5.0

2017-06-28 Thread Andrea Bolognani
On Wed, 2017-06-28 at 22:23 +0200, Daniel Veillard wrote: >   Slightly late so little advance warning see my mail earlier today, > I have now tagged RC1 in git head and pushed signed tarball and rpms > to the usual place: >  >ftp://libvirt.org/libvirt/ >  >   Seems to work well in my limited te

[libvirt] Entering freeze for libvirt-3.5.0

2017-06-28 Thread Daniel Veillard
Slightly late so little advance warning see my mail earlier today, I have now tagged RC1 in git head and pushed signed tarball and rpms to the usual place: ftp://libvirt.org/libvirt/ Seems to work well in my limited testing, https://ci.centos.org/view/libvirt/ is all green except one faile