Re: [vpp-dev] openSUSE build fails

[Dave Wallace]

Actually you do ;)

The VPP vagrant environment supports OpenSUSE in addition to ubuntu16.04 
and centos7:


cd .../vpp/extras/vagrant
export VPP_VAGRANT_DISTRO=opensuse
vagrant up

Thanks,
-daw-

On 1/26/18 1:52 AM, Ole Troan wrote:

Hi Hongjun,


I have no OpenSUSE at hand, and could not give it a try.



Neither do I.

Ole



*From:* Ole Troan [mailto:otr...@employees.org]
*Sent:* Friday, January 26, 2018 2:08 PM
*To:* Ni, Hongjun mailto:hongjun...@intel.com>>
*Cc:* Dave Barach (dbarach) <mailto:dbar...@cisco.com>>; Marco Varlese <mailto:mvarl...@suse.de>>; Gabriel Ganne <mailto:gabriel.ga...@enea.com>>; Billy McFall <mailto:bmcf...@redhat.com>>; Damjan Marion (damarion) 
mailto:damar...@cisco.com>>; vpp-dev 
mailto:vpp-dev@lists.fd.io>>

*Subject:* Re: [vpp-dev] openSUSE build fails

Hongjun,

This looks suspect:

*03:32:31*APIGEN vlibmemory/memclnt.api.h *03:32:31* JSON API 
vlibmemory/memclnt.api.json *03:32:31* SyntaxError: invalid syntax 
(vppapigentab.py, line 11) *03:32:31* 
WARNING:vppapigen:/w/workspace/vpp-verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-data/../src/vlibmemory/memclnt.api:0:1: 
Old Style VLA: u8 data[0]; *03:32:31* Makefile:8794: recipe for 
target 'vlibmemory/memclnt.api.h' failed *03:32:31* make[5]: *** 
[vlibmemory/memclnt.api.h] Error 1 *03:32:31* make[5]: *** Waiting 
for unfinished jobs *03:32:31*

**

Can you try running vppapigen manually on that platform?

Vppapigen —debug —input memclnt.api ...

Cheers

Ole


On 26 Jan 2018, at 06:38, Ni, Hongjun <mailto:hongjun...@intel.com>> wrote:


Hi all,

It seems that OpenSUSE build failed for this patch:

https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console

Please help to take a

*From:* vpp-dev-boun...@lists.fd.io
<mailto:vpp-dev-boun...@lists.fd.io>
[mailto:vpp-dev-boun...@lists.fd.io] *On Behalf Of *Dave Barach
(dbarach)
*Sent:* Friday, December 15, 2017 11:19 PM
*To:* Marco Varlese mailto:mvarl...@suse.de>>;
Gabriel Ganne mailto:gabriel.ga...@enea.com>>; Billy McFall
mailto:bmcf...@redhat.com>>
*Cc:* Damjan Marion (damarion) mailto:damar...@cisco.com>>; vpp-dev mailto:vpp-dev@lists.fd.io>>
*Subject:* Re: [vpp-dev] openSUSE build fails

Dear Marco,

Thanks very much...

Dave

*From:* Marco Varlese [mailto:mvarl...@suse.de]
*Sent:* Friday, December 15, 2017 9:06 AM
*To:* Dave Barach (dbarach) mailto:dbar...@cisco.com>>; Gabriel Ganne
mailto:gabriel.ga...@enea.com>>; Billy
McFall mailto:bmcf...@redhat.com>>
    *Cc:* Damjan Marion (damarion) mailto:damar...@cisco.com>>; vpp-dev mailto:vpp-dev@lists.fd.io>>
*Subject:* Re: [vpp-dev] openSUSE build fails

We (at SUSE) are currently pushing an update to 2.2.11 for
openSUSE in our repositories.

Once that's confirmed to be upstream, I will push a new patch to
the ci-management repo to have the indent package upgraded to the
latest version and re-enable the "checkstyle".

Cheers,

Marco

On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:

With a bit of fiddling, I was able to fix gerrit 9440 so that
indent 2.2.10 and 2.2.11 appear to produce identical results...

HTH... Dave

*From:* vpp-dev-boun...@lists.fd.io
<mailto:vpp-dev-boun...@lists.fd.io>
[mailto:vpp-dev-boun...@lists.fd.io] *On Behalf Of *Gabriel Ganne
*Sent:* Friday, December 15, 2017 8:42 AM
*To:* Billy McFall mailto:bmcf...@redhat.com>>; Marco Varlese mailto:mvarl...@suse.de>>
*Cc:* Damjan Marion (damarion) mailto:damar...@cisco.com>>; vpp-dev mailto:vpp-dev@lists.fd.io>>
*Subject:* Re: [vpp-dev] openSUSE build fails

Hi,

If you browse the source
http://hg.savannah.gnu.org/hgweb/indent/
<http://hg.savannah.gnu.org/hgweb/indent/>

The tag 2.2.11  is there, the source seems updated regularly.

Best regards,

--

Gabriel Ganne



*From:*vpp-dev-boun...@lists.fd.io
<mailto:vpp-dev-boun...@lists.fd.io>
mailto:vpp-dev-boun...@lists.fd.io>> on behalf of Billy
    McFall mailto:bmcf...@redhat.com>>
*Sent:* Friday, December 15, 2017 2:26:42 PM
*To:* Marco Varlese
*Cc:* Damjan Marion (damarion); vpp-dev
*Subject:* Re: [vpp-dev] openSUSE build fails

On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese
mailto:mvarl...@suse.de>> wrote:

Hi Damjan,

On Fri, 2017-12-15 at 09:06 +, Damjan Marion
(damarion) wrote:

On 15 Dec 2017, at 08:52, Marco Varlese
mailto:mvarl...@suse.de>&g

Re: [vpp-dev] openSUSE build fails

[Dave Barach (dbarach)]

As Marco wrote: we’ve experienced sporadic, inexplicable LF infra-related build 
failures since the project started more than two years ago. It’s unusual for an 
otherwise correct patch to require more than one “recheck” for validation, but 
it’s absolutely not unknown.

To mitigate these problems, Ed Kern has built a containerized Jenkins minion 
system which runs on physical hardware, instead of the current setup which 
relies on cloud-hosted Openstack VMs. As soon as practicable – post 18.01 CSIT 
report – we’ll switch to it.

Given a failure which isn’t obviously related to a specific patch, please press 
the “recheck” button. No need to ask, just do it. In case of persistent 
failure, please email vpp-dev.

Thanks… Dave

From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Friday, January 26, 2018 3:25 AM
To: Marco Varlese ; Ole Troan 
Cc: Dave Barach (dbarach) ; Gabriel Ganne 
; Billy McFall ; Damjan Marion 
(damarion) ; vpp-dev 
Subject: RE: [vpp-dev] openSUSE build fails

Hi Marco,

Thank you for your explanation.  Would contact you if I ran into similar issue 
again.

Thanks,
Hongjun

From: Marco Varlese [mailto:mvarl...@suse.de]
Sent: Friday, January 26, 2018 4:21 PM
To: Ni, Hongjun mailto:hongjun...@intel.com>>; Ole Troan 
mailto:otr...@employees.org>>
Cc: Dave Barach (dbarach) mailto:dbar...@cisco.com>>; 
Gabriel Ganne mailto:gabriel.ga...@enea.com>>; Billy 
McFall mailto:bmcf...@redhat.com>>; Damjan Marion 
(damarion) mailto:damar...@cisco.com>>; vpp-dev 
mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

On Fri, 2018-01-26 at 06:58 +, Ni, Hongjun wrote:
I rechecked this patch twice, and it built successfully now.

But why need to recheck twice?
If a "recheck" fixed that then it must be an infrastructure glitch; that's the 
only thing I can think of...

That would not be a surprise either since it does happen from time-to-time to 
see random build failures which get fixed by a "recheck".

Having said that, if you happen to have again this sort of problems (and which 
do not go away with a recheck) feel free to drop me an email and I will look 
into it. Just take into account I'm based at UTC+1.



-Hongjun
- Marco


From: Ole Troan [mailto:otr...@employees.org]
Sent: Friday, January 26, 2018 2:53 PM
To: Ni, Hongjun mailto:hongjun...@intel.com>>
Cc: Dave Barach (dbarach) mailto:dbar...@cisco.com>>; Marco 
Varlese mailto:mvarl...@suse.de>>; Gabriel Ganne 
mailto:gabriel.ga...@enea.com>>; Billy McFall 
mailto:bmcf...@redhat.com>>; Damjan Marion (damarion) 
mailto:damar...@cisco.com>>; vpp-dev 
mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

Hi Hongjun,

I have no OpenSUSE at hand, and could not give it a try.

Neither do I.

Ole



From: Ole Troan [mailto:otr...@employees.org]
Sent: Friday, January 26, 2018 2:08 PM
To: Ni, Hongjun mailto:hongjun...@intel.com>>
Cc: Dave Barach (dbarach) mailto:dbar...@cisco.com>>; Marco 
Varlese mailto:mvarl...@suse.de>>; Gabriel Ganne 
mailto:gabriel.ga...@enea.com>>; Billy McFall 
mailto:bmcf...@redhat.com>>; Damjan Marion (damarion) 
mailto:damar...@cisco.com>>; vpp-dev 
mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

Hongjun,

This looks suspect:

03:32:31 APIGEN vlibmemory/memclnt.api.h 03:32:31 JSON API 
vlibmemory/memclnt.api.json 03:32:31 SyntaxError: invalid syntax 
(vppapigentab.py, line 11) 03:32:31 
WARNING:vppapigen:/w/workspace/vpp-verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-data/../src/vlibmemory/memclnt.api:0:1:
 Old Style VLA: u8 data[0]; 03:32:31 Makefile:8794: recipe for target 
'vlibmemory/memclnt.api.h' failed 03:32:31 make[5]: *** 
[vlibmemory/memclnt.api.h] Error 1 03:32:31 make[5]: *** Waiting for unfinished 
jobs 03:32:31




Can you try running vppapigen manually on that platform?
Vppapigen —debug —input memclnt.api ...

Cheers
Ole


On 26 Jan 2018, at 06:38, Ni, Hongjun 
mailto:hongjun...@intel.com>> wrote:
Hi all,

It seems that OpenSUSE build failed for this patch:
https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console

Please help to take a

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Dave Barach (dbarach)
Sent: Friday, December 15, 2017 11:19 PM
To: Marco Varlese mailto:mvarl...@suse.de>>; Gabriel Ganne 
mailto:gabriel.ga...@enea.com>>; Billy McFall 
mailto:bmcf...@redhat.com>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

Dear Marco,

Thanks very much...

Dave

From: Marco Varlese [mailto:mvarl...@suse.de]
Sent: Friday, December 15, 2017 9:06 AM
To: Dave Barach (dbarach) mailto:dbar...@cisco.com>>; 
Gabriel Ganne mailto:gabriel.ga.

Re: [vpp-dev] openSUSE build fails

[Ni, Hongjun]

Hi Marco,

Thank you for your explanation.  Would contact you if I ran into similar issue 
again.

Thanks,
Hongjun

From: Marco Varlese [mailto:mvarl...@suse.de]
Sent: Friday, January 26, 2018 4:21 PM
To: Ni, Hongjun ; Ole Troan 
Cc: Dave Barach (dbarach) ; Gabriel Ganne 
; Billy McFall ; Damjan Marion 
(damarion) ; vpp-dev 
Subject: Re: [vpp-dev] openSUSE build fails

On Fri, 2018-01-26 at 06:58 +, Ni, Hongjun wrote:
I rechecked this patch twice, and it built successfully now.

But why need to recheck twice?
If a "recheck" fixed that then it must be an infrastructure glitch; that's the 
only thing I can think of...

That would not be a surprise either since it does happen from time-to-time to 
see random build failures which get fixed by a "recheck".

Having said that, if you happen to have again this sort of problems (and which 
do not go away with a recheck) feel free to drop me an email and I will look 
into it. Just take into account I'm based at UTC+1.



-Hongjun
- Marco


From: Ole Troan [mailto:otr...@employees.org]
Sent: Friday, January 26, 2018 2:53 PM
To: Ni, Hongjun mailto:hongjun...@intel.com>>
Cc: Dave Barach (dbarach) mailto:dbar...@cisco.com>>; Marco 
Varlese mailto:mvarl...@suse.de>>; Gabriel Ganne 
mailto:gabriel.ga...@enea.com>>; Billy McFall 
mailto:bmcf...@redhat.com>>; Damjan Marion (damarion) 
mailto:damar...@cisco.com>>; vpp-dev 
mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

Hi Hongjun,

I have no OpenSUSE at hand, and could not give it a try.

Neither do I.

Ole



From: Ole Troan [mailto:otr...@employees.org]
Sent: Friday, January 26, 2018 2:08 PM
To: Ni, Hongjun mailto:hongjun...@intel.com>>
Cc: Dave Barach (dbarach) mailto:dbar...@cisco.com>>; Marco 
Varlese mailto:mvarl...@suse.de>>; Gabriel Ganne 
mailto:gabriel.ga...@enea.com>>; Billy McFall 
mailto:bmcf...@redhat.com>>; Damjan Marion (damarion) 
mailto:damar...@cisco.com>>; vpp-dev 
mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

Hongjun,

This looks suspect:

03:32:31 APIGEN vlibmemory/memclnt.api.h 03:32:31 JSON API 
vlibmemory/memclnt.api.json 03:32:31 SyntaxError: invalid syntax 
(vppapigentab.py, line 11) 03:32:31 
WARNING:vppapigen:/w/workspace/vpp-verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-data/../src/vlibmemory/memclnt.api:0:1:
 Old Style VLA: u8 data[0]; 03:32:31 Makefile:8794: recipe for target 
'vlibmemory/memclnt.api.h' failed 03:32:31 make[5]: *** 
[vlibmemory/memclnt.api.h] Error 1 03:32:31 make[5]: *** Waiting for unfinished 
jobs 03:32:31




Can you try running vppapigen manually on that platform?
Vppapigen —debug —input memclnt.api ...

Cheers
Ole


On 26 Jan 2018, at 06:38, Ni, Hongjun 
mailto:hongjun...@intel.com>> wrote:
Hi all,

It seems that OpenSUSE build failed for this patch:
https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console

Please help to take a

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Dave Barach (dbarach)
Sent: Friday, December 15, 2017 11:19 PM
To: Marco Varlese mailto:mvarl...@suse.de>>; Gabriel Ganne 
mailto:gabriel.ga...@enea.com>>; Billy McFall 
mailto:bmcf...@redhat.com>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

Dear Marco,

Thanks very much...

Dave

From: Marco Varlese [mailto:mvarl...@suse.de]
Sent: Friday, December 15, 2017 9:06 AM
To: Dave Barach (dbarach) mailto:dbar...@cisco.com>>; 
Gabriel Ganne mailto:gabriel.ga...@enea.com>>; Billy 
McFall mailto:bmcf...@redhat.com>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our 
repositories.
Once that's confirmed to be upstream, I will push a new patch to the 
ci-management repo to have the indent package upgraded to the latest version 
and re-enable the "checkstyle".


Cheers,
Marco

On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 and 
2.2.11 appear to produce identical results...

HTH... Dave

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Gabriel Ganne
Sent: Friday, December 15, 2017 8:42 AM
To: Billy McFall mailto:bmcf...@redhat.com>>; Marco Varlese 
mailto:mvarl...@suse.de>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails


Hi,



If you browse the source http://hg.savannah.gnu.org/hgweb/indent/

The

Re: [vpp-dev] openSUSE build fails

[Marco Varlese]

On Fri, 2018-01-26 at 06:58 +, Ni, Hongjun wrote:
> I rechecked this patch twice, and it built successfully now.
> 
>  
> 
> But why need to recheck twice?
If a "recheck" fixed that then it must be an infrastructure glitch; that's the
only thing I can think of...
That would not be a surprise either since it does happen from time-to-time to
see random build failures which get fixed by a "recheck".
Having said that, if you happen to have again this sort of problems (and which
do not go away with a recheck) feel free to drop me an email and I will look
into it. Just take into account I'm based at UTC+1.
>  
> 
> -Hongjun
- Marco
>  
> 
> 
> From: Ole Troan [mailto:otr...@employees.org]
> 
> 
> Sent: Friday, January 26, 2018 2:53 PM
> 
> To: Ni, Hongjun 
> 
> Cc: Dave Barach (dbarach) ; Marco Varlese  >; Gabriel Ganne ; Billy McFall ;
> Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
> 
> 
>  
> 
> Hi Hongjun,
> 
> 
>  
> 
> > I have no OpenSUSE at hand, and could not give it a try.
> > 
> 
>  
> 
> 
> Neither do I. 
> 
> 
>  
> 
> 
> Ole
> 
> 
>  
> 
> 
>  
> 
> >  
> > 
> > 
> > From: Ole Troan [mailto:otr...@employees.org]
> > 
> > 
> > Sent: Friday, January 26, 2018 2:08 PM
> > 
> > To: Ni, Hongjun 
> > 
> > Cc: Dave Barach (dbarach) ; Marco Varlese  > de>; Gabriel Ganne ; Billy McFall
> >  ; Damjan Marion (damarion) ; vpp-
> > dev 
> > 
> > Subject: Re: [vpp-dev] openSUSE build fails
> > 
> > 
> >  
> > 
> > Hongjun,
> > 
> > 
> >  
> > 
> > 
> > This looks suspect:
> > 
> > 
> > 03:32:31 APIGEN vlibmemory/memclnt.api.h 03:32:31 JSON API
> > vlibmemory/memclnt.api.json 03:32:31 SyntaxError: invalid syntax
> > (vppapigentab.py, line 11) 03:32:31 WARNING:vppapigen:/w/workspace/vpp-
> > verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-
> > data/../src/vlibmemory/memclnt.api:0:1: Old Style VLA: u8 data[0]; 03:32:31
> > Makefile:8794: recipe for target 'vlibmemory/memclnt.api.h' failed 03:32:31
> > make[5]: *** [vlibmemory/memclnt.api.h] Error 1 03:32:31 make[5]: ***
> > Waiting for unfinished jobs 03:32:31 
> > 
> > 
> > 
> > 
> >  
> > 
> > 
> > Can you try running vppapigen manually on that platform?
> > 
> > 
> > Vppapigen —debug —input memclnt.api ...
> > 
> > 
> >  
> > 
> > 
> > Cheers 
> > 
> > 
> > Ole
> > 
> > 
> >  
> > 
> > 
> > 
> > 
> > On 26 Jan 2018, at 06:38, Ni, Hongjun  wrote:
> > 
> > > Hi all,
> > >  
> > > It seems that OpenSUSE build failed for this patch:
> > > https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console
> > >  
> > > Please help to take a 
> > >  
> > > 
> > > 
> > > From:
> > > vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io]
> > > On Behalf Of Dave Barach (dbarach)
> > > 
> > > Sent: Friday, December 15, 2017 11:19 PM
> > > 
> > > To: Marco Varlese ; Gabriel Ganne  > > m>; Billy McFall 
> > > 
> > > Cc: Damjan Marion (damarion) ; vpp-dev  > > fd.io>
> > > 
> > > Subject: Re: [vpp-dev] openSUSE build fails
> > > 
> > > 
> > >  
> > > Dear Marco,
> > >  
> > > Thanks very much...
> > >  
> > > 
> > > Dave
> > > 
> > >  
> > > 
> > > 
> > > From: Marco Varlese [mailto:mvarl...@suse.de]
> > > 
> > > 
> > > Sent: Friday, December 15, 2017 9:06 AM
> > > 
> > > To: Dave Barach (dbarach) ; Gabriel Ganne  > > e...@enea.com>; Billy McFall 
> > > 
> > > Cc: Damjan Marion (damarion) ; vpp-dev  > > fd.io>
> > > 
> > > Subject: Re: [vpp-dev] openSUSE build fails
> > > 
> > > 
> > >  
> > > 
> > > We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our
> > > repositories.
> > > 
> > > 
> > > 
> > > Once that's confirmed to be upstream, I will push a new patch to the ci-
> > > management repo to have the indent package upgraded to the latest version
> > > and re-enable the "checkstyle".
> > > 
> > > 
> > >  
> > > 
>

Re: [vpp-dev] openSUSE build fails

[Ni, Hongjun]

I rechecked this patch twice, and it built successfully now.

But why need to recheck twice?

-Hongjun

From: Ole Troan [mailto:otr...@employees.org]
Sent: Friday, January 26, 2018 2:53 PM
To: Ni, Hongjun 
Cc: Dave Barach (dbarach) ; Marco Varlese 
; Gabriel Ganne ; Billy McFall 
; Damjan Marion (damarion) ; vpp-dev 

Subject: Re: [vpp-dev] openSUSE build fails

Hi Hongjun,

I have no OpenSUSE at hand, and could not give it a try.

Neither do I.

Ole



From: Ole Troan [mailto:otr...@employees.org]
Sent: Friday, January 26, 2018 2:08 PM
To: Ni, Hongjun mailto:hongjun...@intel.com>>
Cc: Dave Barach (dbarach) mailto:dbar...@cisco.com>>; Marco 
Varlese mailto:mvarl...@suse.de>>; Gabriel Ganne 
mailto:gabriel.ga...@enea.com>>; Billy McFall 
mailto:bmcf...@redhat.com>>; Damjan Marion (damarion) 
mailto:damar...@cisco.com>>; vpp-dev 
mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

Hongjun,

This looks suspect:

03:32:31 APIGEN vlibmemory/memclnt.api.h 03:32:31 JSON API 
vlibmemory/memclnt.api.json 03:32:31 SyntaxError: invalid syntax 
(vppapigentab.py, line 11) 03:32:31 
WARNING:vppapigen:/w/workspace/vpp-verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-data/../src/vlibmemory/memclnt.api:0:1:
 Old Style VLA: u8 data[0]; 03:32:31 Makefile:8794: recipe for target 
'vlibmemory/memclnt.api.h' failed 03:32:31 make[5]: *** 
[vlibmemory/memclnt.api.h] Error 1 03:32:31 make[5]: *** Waiting for unfinished 
jobs 03:32:31





Can you try running vppapigen manually on that platform?
Vppapigen —debug —input memclnt.api ...

Cheers
Ole


On 26 Jan 2018, at 06:38, Ni, Hongjun 
mailto:hongjun...@intel.com>> wrote:
Hi all,

It seems that OpenSUSE build failed for this patch:
https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console

Please help to take a

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Dave Barach (dbarach)
Sent: Friday, December 15, 2017 11:19 PM
To: Marco Varlese mailto:mvarl...@suse.de>>; Gabriel Ganne 
mailto:gabriel.ga...@enea.com>>; Billy McFall 
mailto:bmcf...@redhat.com>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

Dear Marco,

Thanks very much...

Dave

From: Marco Varlese [mailto:mvarl...@suse.de]
Sent: Friday, December 15, 2017 9:06 AM
To: Dave Barach (dbarach) mailto:dbar...@cisco.com>>; 
Gabriel Ganne mailto:gabriel.ga...@enea.com>>; Billy 
McFall mailto:bmcf...@redhat.com>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our 
repositories.
Once that's confirmed to be upstream, I will push a new patch to the 
ci-management repo to have the indent package upgraded to the latest version 
and re-enable the "checkstyle".


Cheers,
Marco

On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 and 
2.2.11 appear to produce identical results...

HTH... Dave

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Gabriel Ganne
Sent: Friday, December 15, 2017 8:42 AM
To: Billy McFall mailto:bmcf...@redhat.com>>; Marco Varlese 
mailto:mvarl...@suse.de>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails


Hi,



If you browse the source http://hg.savannah.gnu.org/hgweb/indent/

The tag 2.2.11  is there, the source seems updated regularly.



Best regards,



--

Gabriel Ganne


From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
mailto:vpp-dev-boun...@lists.fd.io>> on behalf of 
Billy McFall mailto:bmcf...@redhat.com>>
Sent: Friday, December 15, 2017 2:26:42 PM
To: Marco Varlese
Cc: Damjan Marion (damarion); vpp-dev
Subject: Re: [vpp-dev] openSUSE build fails



On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:
Hi Damjan,

On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:


On 15 Dec 2017, at 08:52, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:

Damjan,

On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
Folks,

I'm hearing from multiple people that OpenSUSE verify job is failing (again).
I haven't heard (or read) anything over the mailing list otherwise I would have
looked into it.
Also, if you hear anything like that you can always ping me directly and I will
look into it...

yes, people pinging me...
See
https://gerrit.fd.io/r/#/c/9440/<

Re: [vpp-dev] openSUSE build fails

[Ole Troan]

Hi Hongjun,

> I have no OpenSUSE at hand, and could not give it a try.

Neither do I. 

Ole


>  
> From: Ole Troan [mailto:otr...@employees.org] 
> Sent: Friday, January 26, 2018 2:08 PM
> To: Ni, Hongjun 
> Cc: Dave Barach (dbarach) ; Marco Varlese 
> ; Gabriel Ganne ; Billy McFall 
> ; Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> Hongjun,
>  
> This looks suspect:
> 03:32:31 APIGEN vlibmemory/memclnt.api.h 03:32:31 JSON API 
> vlibmemory/memclnt.api.json 03:32:31 SyntaxError: invalid syntax 
> (vppapigentab.py, line 11) 03:32:31 
> WARNING:vppapigen:/w/workspace/vpp-verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-data/../src/vlibmemory/memclnt.api:0:1:
>  Old Style VLA: u8 data[0]; 03:32:31 Makefile:8794: recipe for target 
> 'vlibmemory/memclnt.api.h' failed 03:32:31 make[5]: *** 
> [vlibmemory/memclnt.api.h] Error 1 03:32:31 make[5]: *** Waiting for 
> unfinished jobs 03:32:31 
> 
> 
>  
> Can you try running vppapigen manually on that platform?
> Vppapigen —debug —input memclnt.api ...
>  
> Cheers 
> Ole
>  
> 
> On 26 Jan 2018, at 06:38, Ni, Hongjun  wrote:
> 
> Hi all,
>  
> It seems that OpenSUSE build failed for this patch:
> https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console
>  
> Please help to take a 
>  
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
> Behalf Of Dave Barach (dbarach)
> Sent: Friday, December 15, 2017 11:19 PM
> To: Marco Varlese ; Gabriel Ganne ; 
> Billy McFall 
> Cc: Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> Dear Marco,
>  
> Thanks very much...
>  
> Dave
>  
> From: Marco Varlese [mailto:mvarl...@suse.de] 
> Sent: Friday, December 15, 2017 9:06 AM
> To: Dave Barach (dbarach) ; Gabriel Ganne 
> ; Billy McFall 
> Cc: Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our 
> repositories.
> Once that's confirmed to be upstream, I will push a new patch to the 
> ci-management repo to have the indent package upgraded to the latest version 
> and re-enable the "checkstyle".
>  
>  
> Cheers,
> Marco
>  
> On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
> With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 
> and 2.2.11 appear to produce identical results...
>  
> HTH... Dave
>  
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
> Behalf Of Gabriel Ganne
> Sent: Friday, December 15, 2017 8:42 AM
> To: Billy McFall ; Marco Varlese 
> Cc: Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> Hi,
> 
>  
> 
> If you browse the source http://hg.savannah.gnu.org/hgweb/indent/
> 
> The tag 2.2.11  is there, the source seems updated regularly.
> 
>  
> 
> Best regards,
> 
>  
> 
> --
> 
> Gabriel Ganne
> 
> From: vpp-dev-boun...@lists.fd.io  on behalf of 
> Billy McFall 
> Sent: Friday, December 15, 2017 2:26:42 PM
> To: Marco Varlese
> Cc: Damjan Marion (damarion); vpp-dev
> Subject: Re: [vpp-dev] openSUSE build fails
>  
>  
>  
> On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese  wrote:
> Hi Damjan,
>  
> On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:
>  
>  
> 
> On 15 Dec 2017, at 08:52, Marco Varlese  wrote:
>  
> Damjan,
> 
> On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
> 
> Folks,
> 
> I'm hearing from multiple people that OpenSUSE verify job is failing (again).
> I haven't heard (or read) anything over the mailing list otherwise I would 
> have
> looked into it.
> Also, if you hear anything like that you can always ping me directly and I 
> will
> look into it...
>  
> yes, people pinging me...
> See 
> https://gerrit.fd.io/r/#/c/9440/
>  
> also:
>  
> https://gerrit.fd.io/r/#/c/9813/ - abandoned but it shows that something was 
> wrong
>  
> Ok, so just summarizing our conversation on IRC for others too.
>  
> That issue is connected to the different versions of INDENT (C checkstyle) 
> installed on the different distros.
>  
> openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11
>  
> What strikes me is that the upstream repo https://ftp.gnu.org/gnu/indent/ has 
> 2.2.10 as last revision.
> Our indent package maintainer is looking at possible other sources where 
> Indent could "live" these days and will let me know as soon as she finds out.
>  

Re: [vpp-dev] openSUSE build fails

[Ni, Hongjun]

Hi Ole,

I have no OpenSUSE at hand, and could not give it a try.

-Hongjun

From: Ole Troan [mailto:otr...@employees.org]
Sent: Friday, January 26, 2018 2:08 PM
To: Ni, Hongjun 
Cc: Dave Barach (dbarach) ; Marco Varlese 
; Gabriel Ganne ; Billy McFall 
; Damjan Marion (damarion) ; vpp-dev 

Subject: Re: [vpp-dev] openSUSE build fails

Hongjun,

This looks suspect:

03:32:31 APIGEN vlibmemory/memclnt.api.h 03:32:31 JSON API 
vlibmemory/memclnt.api.json 03:32:31 SyntaxError: invalid syntax 
(vppapigentab.py, line 11) 03:32:31 
WARNING:vppapigen:/w/workspace/vpp-verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-data/../src/vlibmemory/memclnt.api:0:1:
 Old Style VLA: u8 data[0]; 03:32:31 Makefile:8794: recipe for target 
'vlibmemory/memclnt.api.h' failed 03:32:31 make[5]: *** 
[vlibmemory/memclnt.api.h] Error 1 03:32:31 make[5]: *** Waiting for unfinished 
jobs 03:32:31




Can you try running vppapigen manually on that platform?
Vppapigen —debug —input memclnt.api ...

Cheers
Ole


On 26 Jan 2018, at 06:38, Ni, Hongjun 
mailto:hongjun...@intel.com>> wrote:
Hi all,

It seems that OpenSUSE build failed for this patch:
https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console

Please help to take a

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Dave Barach (dbarach)
Sent: Friday, December 15, 2017 11:19 PM
To: Marco Varlese mailto:mvarl...@suse.de>>; Gabriel Ganne 
mailto:gabriel.ga...@enea.com>>; Billy McFall 
mailto:bmcf...@redhat.com>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

Dear Marco,

Thanks very much...

Dave

From: Marco Varlese [mailto:mvarl...@suse.de]
Sent: Friday, December 15, 2017 9:06 AM
To: Dave Barach (dbarach) mailto:dbar...@cisco.com>>; 
Gabriel Ganne mailto:gabriel.ga...@enea.com>>; Billy 
McFall mailto:bmcf...@redhat.com>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our 
repositories.
Once that's confirmed to be upstream, I will push a new patch to the 
ci-management repo to have the indent package upgraded to the latest version 
and re-enable the "checkstyle".


Cheers,
Marco

On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 and 
2.2.11 appear to produce identical results...

HTH... Dave

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Gabriel Ganne
Sent: Friday, December 15, 2017 8:42 AM
To: Billy McFall mailto:bmcf...@redhat.com>>; Marco Varlese 
mailto:mvarl...@suse.de>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails


Hi,



If you browse the source http://hg.savannah.gnu.org/hgweb/indent/

The tag 2.2.11  is there, the source seems updated regularly.



Best regards,



--

Gabriel Ganne


From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
mailto:vpp-dev-boun...@lists.fd.io>> on behalf of 
Billy McFall mailto:bmcf...@redhat.com>>
Sent: Friday, December 15, 2017 2:26:42 PM
To: Marco Varlese
Cc: Damjan Marion (damarion); vpp-dev
Subject: Re: [vpp-dev] openSUSE build fails



On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:
Hi Damjan,

On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:


On 15 Dec 2017, at 08:52, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:

Damjan,

On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
Folks,

I'm hearing from multiple people that OpenSUSE verify job is failing (again).
I haven't heard (or read) anything over the mailing list otherwise I would have
looked into it.
Also, if you hear anything like that you can always ping me directly and I will
look into it...

yes, people pinging me...
See
https://gerrit.fd.io/r/#/c/9440/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=68TFeWozfVWr0cOeQcoSLfj_6UOcLVL45-kDlIThNR_ycQZG5LOgi7NnZMJtDMUAmhIPtu-lSoEuMy-6KVT4RlufdWPa2MdfXzb_ObzIVcMVqAGqH7isJhFQHsNuaRick9gGwiEgwUQHltVsqpH-j4MwmcVniuBLxSiCuh2d9gPyZ9J_DeIXB9ebiI349MT3YFcKCmnf4x6PSEKrRYEoXYvyBIR1brcxBEL7qox2rRo>

also:

https://gerrit.fd.io/r/#/c/9813/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=CrMjX_E-jo7WRmm-sopHZy5U_DhywlV7a5A369OJyOow2Mnl2gcRxDLpcasYhpTRR5BtPvolweaLRScakJLx-NDgwKa8ITMZEpYTSnZ33x76qqlb_GnK382fDZNMYQn6KPDthHl7JZPOslzVKjUVDmvIaFaOxiQgDYkMHw02f9pC0xMMRtuuURi0fwbx8lfGUi64rlyZBA0T4tJOBYSPjV

Re: [vpp-dev] openSUSE build fails

[Ole Troan]

Hongjun,

This looks suspect:
03:32:31 APIGEN vlibmemory/memclnt.api.h 03:32:31 JSON API 
vlibmemory/memclnt.api.json 03:32:31 SyntaxError: invalid syntax 
(vppapigentab.py, line 11) 03:32:31 
WARNING:vppapigen:/w/workspace/vpp-verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-data/../src/vlibmemory/memclnt.api:0:1:
 Old Style VLA: u8 data[0]; 03:32:31 Makefile:8794: recipe for target 
'vlibmemory/memclnt.api.h' failed 03:32:31 make[5]: *** 
[vlibmemory/memclnt.api.h] Error 1 03:32:31 make[5]: *** Waiting for unfinished 
jobs 03:32:31


Can you try running vppapigen manually on that platform?
Vppapigen —debug —input memclnt.api ...

Cheers 
Ole


> On 26 Jan 2018, at 06:38, Ni, Hongjun  wrote:
> 
> Hi all,
>  
> It seems that OpenSUSE build failed for this patch:
> https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console
>  
> Please help to take a 
>  
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
> Behalf Of Dave Barach (dbarach)
> Sent: Friday, December 15, 2017 11:19 PM
> To: Marco Varlese ; Gabriel Ganne ; 
> Billy McFall 
> Cc: Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> Dear Marco,
>  
> Thanks very much...
>  
> Dave
>  
> From: Marco Varlese [mailto:mvarl...@suse.de] 
> Sent: Friday, December 15, 2017 9:06 AM
> To: Dave Barach (dbarach) ; Gabriel Ganne 
> ; Billy McFall 
> Cc: Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our 
> repositories.
> Once that's confirmed to be upstream, I will push a new patch to the 
> ci-management repo to have the indent package upgraded to the latest version 
> and re-enable the "checkstyle".
>  
>  
> Cheers,
> Marco
>  
> On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
> With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 
> and 2.2.11 appear to produce identical results...
>  
> HTH... Dave
>  
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
> Behalf Of Gabriel Ganne
> Sent: Friday, December 15, 2017 8:42 AM
> To: Billy McFall ; Marco Varlese 
> Cc: Damjan Marion (damarion) ; vpp-dev 
> 
> Subject: Re: [vpp-dev] openSUSE build fails
>  
> Hi,
> 
>  
> 
> If you browse the source http://hg.savannah.gnu.org/hgweb/indent/
> 
> The tag 2.2.11  is there, the source seems updated regularly.
> 
>  
> 
> Best regards,
> 
>  
> 
> --
> 
> Gabriel Ganne
> 
> From: vpp-dev-boun...@lists.fd.io  on behalf of 
> Billy McFall 
> Sent: Friday, December 15, 2017 2:26:42 PM
> To: Marco Varlese
> Cc: Damjan Marion (damarion); vpp-dev
> Subject: Re: [vpp-dev] openSUSE build fails
>  
>  
>  
> On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese  wrote:
> Hi Damjan,
>  
> On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:
>  
>  
> 
> On 15 Dec 2017, at 08:52, Marco Varlese  wrote:
>  
> Damjan,
> 
> On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
> 
> Folks,
> 
> I'm hearing from multiple people that OpenSUSE verify job is failing (again).
> I haven't heard (or read) anything over the mailing list otherwise I would 
> have
> looked into it.
> Also, if you hear anything like that you can always ping me directly and I 
> will
> look into it...
>  
> yes, people pinging me...
> See 
> https://gerrit.fd.io/r/#/c/9440/
>  
> also:
>  
> https://gerrit.fd.io/r/#/c/9813/ - abandoned but it shows that something was 
> wrong
>  
> Ok, so just summarizing our conversation on IRC for others too.
>  
> That issue is connected to the different versions of INDENT (C checkstyle) 
> installed on the different distros.
>  
> openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11
>  
> What strikes me is that the upstream repo https://ftp.gnu.org/gnu/indent/ has 
> 2.2.10 as last revision.
> Our indent package maintainer is looking at possible other sources where 
> Indent could "live" these days and will let me know as soon as she finds out.
>  
> @Thomas Herbert, would you know the source where the Indent package on CentOS 
> come from? Maybe that could help...
>  
> Marco, I can't find the source. I'll look around a little more. From CentoOS 
> 7.4:
>  
> $ sudo yum provides indent
> :
> indent-2.2.11-13.el7.x86_64 : A GNU program for formatting C code
> Repo: base
> :
>  
> $ sudo repoquery -i indent
> Name: indent
> Version : 2.2.11
> Release : 13.el7
> Architecture: x86_64
&

Re: [vpp-dev] openSUSE build fails

[Ni, Hongjun]

Hi all,

It seems that OpenSUSE build failed for this patch:
https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console

Please help to take a look at it.  Thanks a lot.

Thanks,
Hongjun

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Dave Barach (dbarach)
Sent: Friday, December 15, 2017 11:19 PM
To: Marco Varlese ; Gabriel Ganne ; 
Billy McFall 
Cc: Damjan Marion (damarion) ; vpp-dev 
Subject: Re: [vpp-dev] openSUSE build fails

Dear Marco,

Thanks very much...

Dave

From: Marco Varlese [mailto:mvarl...@suse.de]
Sent: Friday, December 15, 2017 9:06 AM
To: Dave Barach (dbarach) mailto:dbar...@cisco.com>>; 
Gabriel Ganne mailto:gabriel.ga...@enea.com>>; Billy 
McFall mailto:bmcf...@redhat.com>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails

We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our 
repositories.
Once that's confirmed to be upstream, I will push a new patch to the 
ci-management repo to have the indent package upgraded to the latest version 
and re-enable the "checkstyle".


Cheers,
Marco

On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 and 
2.2.11 appear to produce identical results...

HTH... Dave

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Gabriel Ganne
Sent: Friday, December 15, 2017 8:42 AM
To: Billy McFall mailto:bmcf...@redhat.com>>; Marco Varlese 
mailto:mvarl...@suse.de>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails


Hi,



If you browse the source http://hg.savannah.gnu.org/hgweb/indent/

The tag 2.2.11  is there, the source seems updated regularly.



Best regards,



--

Gabriel Ganne


From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
mailto:vpp-dev-boun...@lists.fd.io>> on behalf of 
Billy McFall mailto:bmcf...@redhat.com>>
Sent: Friday, December 15, 2017 2:26:42 PM
To: Marco Varlese
Cc: Damjan Marion (damarion); vpp-dev
Subject: Re: [vpp-dev] openSUSE build fails



On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:
Hi Damjan,

On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:


On 15 Dec 2017, at 08:52, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:

Damjan,

On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
Folks,

I'm hearing from multiple people that OpenSUSE verify job is failing (again).
I haven't heard (or read) anything over the mailing list otherwise I would have
looked into it.
Also, if you hear anything like that you can always ping me directly and I will
look into it...

yes, people pinging me...
See
https://gerrit.fd.io/r/#/c/9440/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=68TFeWozfVWr0cOeQcoSLfj_6UOcLVL45-kDlIThNR_ycQZG5LOgi7NnZMJtDMUAmhIPtu-lSoEuMy-6KVT4RlufdWPa2MdfXzb_ObzIVcMVqAGqH7isJhFQHsNuaRick9gGwiEgwUQHltVsqpH-j4MwmcVniuBLxSiCuh2d9gPyZ9J_DeIXB9ebiI349MT3YFcKCmnf4x6PSEKrRYEoXYvyBIR1brcxBEL7qox2rRo>

also:

https://gerrit.fd.io/r/#/c/9813/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=CrMjX_E-jo7WRmm-sopHZy5U_DhywlV7a5A369OJyOow2Mnl2gcRxDLpcasYhpTRR5BtPvolweaLRScakJLx-NDgwKa8ITMZEpYTSnZ33x76qqlb_GnK382fDZNMYQn6KPDthHl7JZPOslzVKjUVDmvIaFaOxiQgDYkMHw02f9pC0xMMRtuuURi0fwbx8lfGUi64rlyZBA0T4tJOBYSPjVrm_yF86cI4X2Cc5I7XB8s>
 - abandoned but it shows that something was wrong

Ok, so just summarizing our conversation on IRC for others too.

That issue is connected to the different versions of INDENT (C checkstyle) 
installed on the different distros.

openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11

What strikes me is that the upstream repo 
https://ftp.gnu.org/gnu/indent/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=SSiBFtZ5JbQhgjd9dEVXNEBYOdVo_Zo1ALr23wlHN44ValS-HDgjsawWJnWi-UHq0Pe9bgVnD5fLzJs6yISu-7ZkpGlAUgLW-IeDY4i6dsSzbSrCQ97iLT5lh93ItR7CCJtRvXBazqKbU6mxvPD_UTUCxm8qPdLPUdki9viMke3Q_tIJAReRf4KOT37lCP3T5tgGg3r1OT86tvKq2dovxDIjSQuPwKrDpiZ8AsSTB5w>
 has 2.2.10 as last revision.
Our indent package maintainer is looking at possible other sources where Indent 
could "live" these days and will let me know as soon as she finds out.

@Thomas Herbert, would you know the source where the Indent package on CentOS 
come from? Maybe that could help...

Marco, I can't find the source. I'll look around a little more. From CentoOS 
7.4:

$ sudo yum provides indent
:
indent-2.2.11-13.el7.x86_64 : A GNU program for formatting C code
Repo: base
:

$ sudo repoquery -i indent
Name: indent

Re: [vpp-dev] openSUSE build fails

[Dave Barach (dbarach)]

Dear Marco,

Thanks very much...

Dave

From: Marco Varlese [mailto:mvarl...@suse.de]
Sent: Friday, December 15, 2017 9:06 AM
To: Dave Barach (dbarach) ; Gabriel Ganne 
; Billy McFall 
Cc: Damjan Marion (damarion) ; vpp-dev 
Subject: Re: [vpp-dev] openSUSE build fails

We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our 
repositories.
Once that's confirmed to be upstream, I will push a new patch to the 
ci-management repo to have the indent package upgraded to the latest version 
and re-enable the "checkstyle".


Cheers,
Marco

On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 and 
2.2.11 appear to produce identical results...

HTH... Dave

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Gabriel Ganne
Sent: Friday, December 15, 2017 8:42 AM
To: Billy McFall mailto:bmcf...@redhat.com>>; Marco Varlese 
mailto:mvarl...@suse.de>>
Cc: Damjan Marion (damarion) mailto:damar...@cisco.com>>; 
vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] openSUSE build fails


Hi,



If you browse the source http://hg.savannah.gnu.org/hgweb/indent/

The tag 2.2.11  is there, the source seems updated regularly.



Best regards,



--

Gabriel Ganne


From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
mailto:vpp-dev-boun...@lists.fd.io>> on behalf of 
Billy McFall mailto:bmcf...@redhat.com>>
Sent: Friday, December 15, 2017 2:26:42 PM
To: Marco Varlese
Cc: Damjan Marion (damarion); vpp-dev
Subject: Re: [vpp-dev] openSUSE build fails



On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:
Hi Damjan,

On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:


On 15 Dec 2017, at 08:52, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:

Damjan,

On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
Folks,

I'm hearing from multiple people that OpenSUSE verify job is failing (again).
I haven't heard (or read) anything over the mailing list otherwise I would have
looked into it.
Also, if you hear anything like that you can always ping me directly and I will
look into it...

yes, people pinging me...
See
https://gerrit.fd.io/r/#/c/9440/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=68TFeWozfVWr0cOeQcoSLfj_6UOcLVL45-kDlIThNR_ycQZG5LOgi7NnZMJtDMUAmhIPtu-lSoEuMy-6KVT4RlufdWPa2MdfXzb_ObzIVcMVqAGqH7isJhFQHsNuaRick9gGwiEgwUQHltVsqpH-j4MwmcVniuBLxSiCuh2d9gPyZ9J_DeIXB9ebiI349MT3YFcKCmnf4x6PSEKrRYEoXYvyBIR1brcxBEL7qox2rRo>

also:

https://gerrit.fd.io/r/#/c/9813/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=CrMjX_E-jo7WRmm-sopHZy5U_DhywlV7a5A369OJyOow2Mnl2gcRxDLpcasYhpTRR5BtPvolweaLRScakJLx-NDgwKa8ITMZEpYTSnZ33x76qqlb_GnK382fDZNMYQn6KPDthHl7JZPOslzVKjUVDmvIaFaOxiQgDYkMHw02f9pC0xMMRtuuURi0fwbx8lfGUi64rlyZBA0T4tJOBYSPjVrm_yF86cI4X2Cc5I7XB8s>
 - abandoned but it shows that something was wrong

Ok, so just summarizing our conversation on IRC for others too.

That issue is connected to the different versions of INDENT (C checkstyle) 
installed on the different distros.

openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11

What strikes me is that the upstream repo 
https://ftp.gnu.org/gnu/indent/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=SSiBFtZ5JbQhgjd9dEVXNEBYOdVo_Zo1ALr23wlHN44ValS-HDgjsawWJnWi-UHq0Pe9bgVnD5fLzJs6yISu-7ZkpGlAUgLW-IeDY4i6dsSzbSrCQ97iLT5lh93ItR7CCJtRvXBazqKbU6mxvPD_UTUCxm8qPdLPUdki9viMke3Q_tIJAReRf4KOT37lCP3T5tgGg3r1OT86tvKq2dovxDIjSQuPwKrDpiZ8AsSTB5w>
 has 2.2.10 as last revision.
Our indent package maintainer is looking at possible other sources where Indent 
could "live" these days and will let me know as soon as she finds out.

@Thomas Herbert, would you know the source where the Indent package on CentOS 
come from? Maybe that could help...

Marco, I can't find the source. I'll look around a little more. From CentoOS 
7.4:

$ sudo yum provides indent
:
indent-2.2.11-13.el7.x86_64 : A GNU program for formatting C code
Repo: base
:

$ sudo repoquery -i indent
Name: indent
Version : 2.2.11
Release : 13.el7
Architecture: x86_64
Size: 359131
Packager: CentOS BuildSystem 
<http://bugs.centos.org<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=Oxgo1-3NKrvdr09W1lYMqTengBfLr3NBV2FFVNtp8fYGuDtJWoThOJlSD8GJqvFV073z9nD7sN8CIc6cGMY5Ktf0s2dmicXgEpxSpJ-1vWF3HJzKuKhaong1C79JraHgpv_RMkyn1Ti3ea_6V8IRf2brmeHyPuhEYTWSI_QG6AqFtjvX0aPRaSumejPxEeXCAykFMtWiapGJkmDmUsNaddheKgKeaLKrV5Dta5pVn40>>
Group   : Applications/Text
URL : 
http://indent.isidore-it.eu/beautify.html<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=ZsJ-B8LyIX_mcc1N

Re: [vpp-dev] openSUSE build fails

[Marco Varlese]

We (at SUSE) are currently pushing an update to 2.2.11 for openSUSE in our
repositories. Once that's confirmed to be upstream, I will push a new patch to
the ci-management repo to have the indent package upgraded to the latest version
and re-enable the "checkstyle".

Cheers,Marco
On Fri, 2017-12-15 at 13:51 +, Dave Barach (dbarach) wrote:
> With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10
> and 2.2.11 appear to produce identical results...
>  
> 
> HTH... Dave
> 
>  
> 
> 
> 
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io]
> On Behalf Of Gabriel Ganne
> 
> Sent: Friday, December 15, 2017 8:42 AM
> 
> To: Billy McFall ; Marco Varlese 
> 
> Cc: Damjan Marion (damarion) ; vpp-dev  o>
> 
> Subject: Re: [vpp-dev] openSUSE build fails
> 
> 
>  
> 
> Hi,
>  
> If you browse the source 
> http://hg.savannah.gnu.org/hgweb/indent/
> The tag 2.2.11  is there, the source seems updated regularly.
>  
> Best regards,
>  
> 
> 
> --
> Gabriel Ganne
> 
> 
> 
> 
> 
> 
> 
> From:
> vpp-dev-boun...@lists.fd.io  on behalf of Billy
> McFall 
> 
> Sent: Friday, December 15, 2017 2:26:42 PM
> 
> To: Marco Varlese
> 
> Cc: Damjan Marion (damarion); vpp-dev
> 
> Subject: Re: [vpp-dev] openSUSE build fails 
> 
>  
> 
> 
> 
> 
>  
> 
>  
> 
> On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese  wrote:
> > 
> > Hi Damjan,
> > 
> > 
> >  
> > 
> > 
> > On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:
> > 
> > >  
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > > On 15 Dec 2017, at 08:52, Marco Varlese  wrote:
> > > > 
> > > >  
> > > > 
> > > > 
> > > > Damjan,
> > > > 
> > > > 
> > > > 
> > > > On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > Folks,
> > > > > 
> > > > > 
> > > > > 
> > > > > I'm hearing from multiple people that OpenSUSE verify job is failing
> > > > > (again).
> > > > 
> > > > I haven't heard (or read) anything over the mailing list otherwise I
> > > > would have
> > > > 
> > > > looked into it.
> > > > 
> > > > Also, if you hear anything like that you can always ping me directly and
> > > > I will
> > > > 
> > > > look into it...
> > > > 
> > > > 
> > > 
> > >  
> > > 
> > > 
> > > yes, people pinging me...
> > > 
> > > 
> > > See 
> > > 
> > > 
> > > https://gerrit.fd.io/r/#/c/9440/
> > > 
> > > 
> > >  
> > > 
> > > 
> > > also:
> > > 
> > > 
> > >  
> > > 
> > > 
> > > https://gerrit.fd.io/r/#/c/9813/3/ -
> > >  abandoned but it shows that something was wrong
> > > 
> > > 
> > 
> >  
> > 
> > 
> > Ok, so just summarizing our conversation on IRC for others too.
> > 
> > 
> >  
> > 
> > 
> > That issue is connected to the different versions of INDENT (C checkstyle)
> > installed on the different distros.
> > 
> > 
> >  
> > 
> > 
> > openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11
> > 
> > 
> >  
> > 
> > 
> > What strikes me is that the upstream repo 
> > https://ftp.gnu.org/gnu/indent/ has 2.2.10 as last revision.
> > 
> > 
> > Our indent package maintainer is looking at possible other sources where
> > Indent could "live" these days and will let me know as soon as she finds
> > out.
> > 
> > 
> >  
> > 
> > 
> > @Thomas Herbert, would you know the source where the Indent package on
> > CentOS come from? Maybe that could help...
> > 
> > 
> 
>  
> 
> 
> Marco, I can't find the source. I'll look around a little more. From CentoOS
> 7.4:
> 
> 
>  
> 
> 
> $ sudo yum provides indent
> 
> 
> :
> 
> 
> 
> indent-2.2.11-13.el7.x86_64 : A GNU program for formatting C code
> 
> 
> Repo: base
> 
> 
> 
> :
> 
> 
>  
> 
> 
> $ sudo repoquery -i indent
> 
> 
> Nam

Re: [vpp-dev] openSUSE build fails

[Dave Barach (dbarach)]

With a bit of fiddling, I was able to fix gerrit 9440 so that indent 2.2.10 and 
2.2.11 appear to produce identical results...

HTH... Dave

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Gabriel Ganne
Sent: Friday, December 15, 2017 8:42 AM
To: Billy McFall ; Marco Varlese 
Cc: Damjan Marion (damarion) ; vpp-dev 
Subject: Re: [vpp-dev] openSUSE build fails


Hi,



If you browse the source http://hg.savannah.gnu.org/hgweb/indent/

The tag 2.2.11  is there, the source seems updated regularly.



Best regards,



--

Gabriel Ganne


From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
mailto:vpp-dev-boun...@lists.fd.io>> on behalf of 
Billy McFall mailto:bmcf...@redhat.com>>
Sent: Friday, December 15, 2017 2:26:42 PM
To: Marco Varlese
Cc: Damjan Marion (damarion); vpp-dev
Subject: Re: [vpp-dev] openSUSE build fails



On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:
Hi Damjan,

On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:



On 15 Dec 2017, at 08:52, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:

Damjan,

On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:

Folks,

I'm hearing from multiple people that OpenSUSE verify job is failing (again).
I haven't heard (or read) anything over the mailing list otherwise I would have
looked into it.
Also, if you hear anything like that you can always ping me directly and I will
look into it...

yes, people pinging me...
See
https://gerrit.fd.io/r/#/c/9440/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=68TFeWozfVWr0cOeQcoSLfj_6UOcLVL45-kDlIThNR_ycQZG5LOgi7NnZMJtDMUAmhIPtu-lSoEuMy-6KVT4RlufdWPa2MdfXzb_ObzIVcMVqAGqH7isJhFQHsNuaRick9gGwiEgwUQHltVsqpH-j4MwmcVniuBLxSiCuh2d9gPyZ9J_DeIXB9ebiI349MT3YFcKCmnf4x6PSEKrRYEoXYvyBIR1brcxBEL7qox2rRo>

also:

https://gerrit.fd.io/r/#/c/9813/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=CrMjX_E-jo7WRmm-sopHZy5U_DhywlV7a5A369OJyOow2Mnl2gcRxDLpcasYhpTRR5BtPvolweaLRScakJLx-NDgwKa8ITMZEpYTSnZ33x76qqlb_GnK382fDZNMYQn6KPDthHl7JZPOslzVKjUVDmvIaFaOxiQgDYkMHw02f9pC0xMMRtuuURi0fwbx8lfGUi64rlyZBA0T4tJOBYSPjVrm_yF86cI4X2Cc5I7XB8s>
 - abandoned but it shows that something was wrong

Ok, so just summarizing our conversation on IRC for others too.

That issue is connected to the different versions of INDENT (C checkstyle) 
installed on the different distros.

openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11

What strikes me is that the upstream repo 
https://ftp.gnu.org/gnu/indent/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=SSiBFtZ5JbQhgjd9dEVXNEBYOdVo_Zo1ALr23wlHN44ValS-HDgjsawWJnWi-UHq0Pe9bgVnD5fLzJs6yISu-7ZkpGlAUgLW-IeDY4i6dsSzbSrCQ97iLT5lh93ItR7CCJtRvXBazqKbU6mxvPD_UTUCxm8qPdLPUdki9viMke3Q_tIJAReRf4KOT37lCP3T5tgGg3r1OT86tvKq2dovxDIjSQuPwKrDpiZ8AsSTB5w>
 has 2.2.10 as last revision.
Our indent package maintainer is looking at possible other sources where Indent 
could "live" these days and will let me know as soon as she finds out.

@Thomas Herbert, would you know the source where the Indent package on CentOS 
come from? Maybe that could help...

Marco, I can't find the source. I'll look around a little more. From CentoOS 
7.4:

$ sudo yum provides indent
:
indent-2.2.11-13.el7.x86_64 : A GNU program for formatting C code
Repo: base
:

$ sudo repoquery -i indent
Name: indent
Version : 2.2.11
Release : 13.el7
Architecture: x86_64
Size: 359131
Packager: CentOS BuildSystem 
<http://bugs.centos.org<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=Oxgo1-3NKrvdr09W1lYMqTengBfLr3NBV2FFVNtp8fYGuDtJWoThOJlSD8GJqvFV073z9nD7sN8CIc6cGMY5Ktf0s2dmicXgEpxSpJ-1vWF3HJzKuKhaong1C79JraHgpv_RMkyn1Ti3ea_6V8IRf2brmeHyPuhEYTWSI_QG6AqFtjvX0aPRaSumejPxEeXCAykFMtWiapGJkmDmUsNaddheKgKeaLKrV5Dta5pVn40>>
Group   : Applications/Text
URL : 
http://indent.isidore-it.eu/beautify.html<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=ZsJ-B8LyIX_mcc1NX7wX4Kz57W648StYyqnjXbWD3QB20zhg9sd-OE6uScITWGKPDbg3FdfOIcmaGdewo2XSUck4otKAX5pyaWrAGli_LgaJNiL2fVH3-_g_lpB-3bQcL8W1ZlpPrbqD68TvAI6C6z7tcNwHg0U_FIw8kpDJOMSsgSyNZUCsqnzwkIgeZe790v-TLfFaLYfMKISLfgPJ1n3pylMyG4MyoPbPaxa7ujz76HRn4NLQhDlQ-T3OQMlI>
   <-- BUSTED LINK
Repository  : base
Summary : A GNU program for formatting C code
Source  : indent-2.2.11-13.el7.src.rpm
Description :
Indent is a GNU program for beautifying C code, so that it is easier to
read.  Indent can also convert from one C writing style to a different
one.  Indent understands correct C syntax and tries to handle incorrect
C syntax.

Install the indent package if you are developing applications in C and
you want a program to format your code.






So generally speaking i would like to question having verify jobs for mult

Re: [vpp-dev] openSUSE build fails

[Gabriel Ganne]

Hi,


If you browse the source 
http://hg.savannah.gnu.org/hgweb/indent/<http://hg.savannah.gnu.org/hgweb/indent>

The tag 2.2.11  is there, the source seems updated regularly.


Best regards,


--

Gabriel Ganne


From: vpp-dev-boun...@lists.fd.io  on behalf of 
Billy McFall 
Sent: Friday, December 15, 2017 2:26:42 PM
To: Marco Varlese
Cc: Damjan Marion (damarion); vpp-dev
Subject: Re: [vpp-dev] openSUSE build fails



On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:
Hi Damjan,

On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:


On 15 Dec 2017, at 08:52, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:

Damjan,

On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
Folks,

I'm hearing from multiple people that OpenSUSE verify job is failing (again).
I haven't heard (or read) anything over the mailing list otherwise I would have
looked into it.
Also, if you hear anything like that you can always ping me directly and I will
look into it...

yes, people pinging me...
See
https://gerrit.fd.io/r/#/c/9440/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=68TFeWozfVWr0cOeQcoSLfj_6UOcLVL45-kDlIThNR_ycQZG5LOgi7NnZMJtDMUAmhIPtu-lSoEuMy-6KVT4RlufdWPa2MdfXzb_ObzIVcMVqAGqH7isJhFQHsNuaRick9gGwiEgwUQHltVsqpH-j4MwmcVniuBLxSiCuh2d9gPyZ9J_DeIXB9ebiI349MT3YFcKCmnf4x6PSEKrRYEoXYvyBIR1brcxBEL7qox2rRo>

also:

https://gerrit.fd.io/r/#/c/9813/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=CrMjX_E-jo7WRmm-sopHZy5U_DhywlV7a5A369OJyOow2Mnl2gcRxDLpcasYhpTRR5BtPvolweaLRScakJLx-NDgwKa8ITMZEpYTSnZ33x76qqlb_GnK382fDZNMYQn6KPDthHl7JZPOslzVKjUVDmvIaFaOxiQgDYkMHw02f9pC0xMMRtuuURi0fwbx8lfGUi64rlyZBA0T4tJOBYSPjVrm_yF86cI4X2Cc5I7XB8s>
 - abandoned but it shows that something was wrong

Ok, so just summarizing our conversation on IRC for others too.

That issue is connected to the different versions of INDENT (C checkstyle) 
installed on the different distros.

openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11

What strikes me is that the upstream repo 
https://ftp.gnu.org/gnu/indent/<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=SSiBFtZ5JbQhgjd9dEVXNEBYOdVo_Zo1ALr23wlHN44ValS-HDgjsawWJnWi-UHq0Pe9bgVnD5fLzJs6yISu-7ZkpGlAUgLW-IeDY4i6dsSzbSrCQ97iLT5lh93ItR7CCJtRvXBazqKbU6mxvPD_UTUCxm8qPdLPUdki9viMke3Q_tIJAReRf4KOT37lCP3T5tgGg3r1OT86tvKq2dovxDIjSQuPwKrDpiZ8AsSTB5w>
 has 2.2.10 as last revision.
Our indent package maintainer is looking at possible other sources where Indent 
could "live" these days and will let me know as soon as she finds out.

@Thomas Herbert, would you know the source where the Indent package on CentOS 
come from? Maybe that could help...

Marco, I can't find the source. I'll look around a little more. From CentoOS 
7.4:

$ sudo yum provides indent
:
indent-2.2.11-13.el7.x86_64 : A GNU program for formatting C code
Repo: base
:

$ sudo repoquery -i indent
Name: indent
Version : 2.2.11
Release : 13.el7
Architecture: x86_64
Size: 359131
Packager: CentOS BuildSystem 
<http://bugs.centos.org<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=Oxgo1-3NKrvdr09W1lYMqTengBfLr3NBV2FFVNtp8fYGuDtJWoThOJlSD8GJqvFV073z9nD7sN8CIc6cGMY5Ktf0s2dmicXgEpxSpJ-1vWF3HJzKuKhaong1C79JraHgpv_RMkyn1Ti3ea_6V8IRf2brmeHyPuhEYTWSI_QG6AqFtjvX0aPRaSumejPxEeXCAykFMtWiapGJkmDmUsNaddheKgKeaLKrV5Dta5pVn40>>
Group   : Applications/Text
URL : 
http://indent.isidore-it.eu/beautify.html<https://url10.mailanyone.net/v1/?m=1ePq0t-0001Fl-6M&i=57e1b682&c=ZsJ-B8LyIX_mcc1NX7wX4Kz57W648StYyqnjXbWD3QB20zhg9sd-OE6uScITWGKPDbg3FdfOIcmaGdewo2XSUck4otKAX5pyaWrAGli_LgaJNiL2fVH3-_g_lpB-3bQcL8W1ZlpPrbqD68TvAI6C6z7tcNwHg0U_FIw8kpDJOMSsgSyNZUCsqnzwkIgeZe790v-TLfFaLYfMKISLfgPJ1n3pylMyG4MyoPbPaxa7ujz76HRn4NLQhDlQ-T3OQMlI>
   <-- BUSTED LINK
Repository  : base
Summary : A GNU program for formatting C code
Source  : indent-2.2.11-13.el7.src.rpm
Description :
Indent is a GNU program for beautifying C code, so that it is easier to
read.  Indent can also convert from one C writing style to a different
one.  Indent understands correct C syntax and tries to handle incorrect
C syntax.

Install the indent package if you are developing applications in C and
you want a program to format your code.





So generally speaking i would like to question having verify jobs for multiple
distros.
Is there really a value in compiling same code on different distros. Yes I
know gcc version can be different,
but that can be addressed in simpler way, if it needs to be addressed at all.

More distros means more moving parts and bigger chance that something will
fail.
Well, I am not sure how to interpret this but (in theory) a build should be
reproducible in the first place and I should not worry about problems with build
outcomes. It doesn't only affect op

Re: [vpp-dev] openSUSE build fails

[Billy McFall]

On Fri, Dec 15, 2017 at 5:15 AM, Marco Varlese  wrote:

> Hi Damjan,
>
> On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:
>
>
>
> On 15 Dec 2017, at 08:52, Marco Varlese  wrote:
>
> Damjan,
>
> On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
>
> Folks,
>
> I'm hearing from multiple people that OpenSUSE verify job is failing
> (again).
>
> I haven't heard (or read) anything over the mailing list otherwise I would
> have
> looked into it.
> Also, if you hear anything like that you can always ping me directly and I
> will
> look into it...
>
>
> yes, people pinging me...
> See
> https://gerrit.fd.io/r/#/c/9440/
>
> also:
>
> https://gerrit.fd.io/r/#/c/9813/ - abandoned but it shows that something
> was wrong
>
>
> Ok, so just summarizing our conversation on IRC for others too.
>
> That issue is connected to the different versions of INDENT (C checkstyle)
> installed on the different distros.
>
> openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11
>
> What strikes me is that the upstream repo https://ftp.gnu.org/gnu/indent/
> has 2.2.10 as last revision.
> Our indent package maintainer is looking at possible other sources where
> Indent could "live" these days and will let me know as soon as she finds
> out.
>
> @Thomas Herbert, would you know the source where the Indent package on
> CentOS come from? Maybe that could help...
>

Marco, I can't find the source. I'll look around a little more. From
CentoOS 7.4:

$ sudo yum provides indent
:
indent-2.2.11-13.el7.x86_64 : A GNU program for formatting C code
Repo: base
:

$ sudo repoquery -i indent
Name: indent
Version : 2.2.11
Release : 13.el7
Architecture: x86_64
Size: 359131
Packager: CentOS BuildSystem 
Group   : Applications/Text
URL : http://indent.isidore-it.eu/beautify.html   <-- BUSTED LINK
Repository  : base
Summary : A GNU program for formatting C code
Source  : indent-2.2.11-13.el7.src.rpm
Description :
Indent is a GNU program for beautifying C code, so that it is easier to
read.  Indent can also convert from one C writing style to a different
one.  Indent understands correct C syntax and tries to handle incorrect
C syntax.

Install the indent package if you are developing applications in C and
you want a program to format your code.


>
>
>
>
> So generally speaking i would like to question having verify jobs for
> multiple
> distros.
> Is there really a value in compiling same code on different distros. Yes I
> know gcc version can be different,
> but that can be addressed in simpler way, if it needs to be addressed at
> all.
>
> More distros means more moving parts and bigger chance that something will
> fail.
>
> Well, I am not sure how to interpret this but (in theory) a build should be
> reproducible in the first place and I should not worry about problems with
> build
> outcomes. It doesn't only affect openSUSE and I raised it many times over
> the
> mailing-list; when you need to run "recheck" multiple times to have a build
> succeed. IMHO the issue should be addressed and not solved by putting it
> under
> the carpet...
>
>
> We all know that we have extreme fragile system, as obviously we are not
> be able to
> fix that in almost 2 years, so as long as the system is as it increasing
> complexity doesn't help
> and just causes frustration.
>
> Also it cost resources
>
> That is a different matter and if that's the case then it should be
> discussed
> seriously; raising this argument now, after having had people investing
> their
> times in getting stuff up and running isn't really a cool thing...
>
>
> Marco, decision to have verify jobs on 2 distros was made much before you
> joined the project,
> and I don't remember serious decision on that topic, it might be that at
> that time
> we were simply unexperienced, or maybe we didn't expect infra to be so
> fragile.
>
> Fact is that now we have ridiculous situation, 2 verify jobs says patch is
> OK, 3rd one says
> it is not. Which one to trust?
>
> So please don't take this personal, i know you invested time to get suse
> build working, but still
> I think it is a valid question to ask, do we really need 3 verify jobs.
> Should we have 4 tomorrow
> if somebody invest his time to do verify job on Archlinux for example?
>
> Thanks,
>
> Damjan
>
>
>
> --
>
> Marco V
>
> SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
> HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] openSUSE build fails

[Dave Barach (dbarach)]

Guys,

I’ll take a look at e.g. gerrit 9440, ip_frag.c and see if I can fix it.

Under the circumstances, it seems perfectly OK to s/ON/OFF/ as needed in the 
per-file patch verification on/off switch:

/*
* fd.io coding-style-patch-verification: ON
*
* Local Variables:
* eval: (c-set-style "gnu")
* End:
*/

Thanks… Dave

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Marco Varlese
Sent: Friday, December 15, 2017 5:16 AM
To: Damjan Marion (damarion) 
Cc: vpp-dev 
Subject: Re: [vpp-dev] openSUSE build fails

Hi Damjan,

On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:



On 15 Dec 2017, at 08:52, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:

Damjan,

On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:

Folks,

I'm hearing from multiple people that OpenSUSE verify job is failing (again).
I haven't heard (or read) anything over the mailing list otherwise I would have
looked into it.
Also, if you hear anything like that you can always ping me directly and I will
look into it...

yes, people pinging me...
See
https://gerrit.fd.io/r/#/c/9440/

also:

https://gerrit.fd.io/r/#/c/9813/ - abandoned but it shows that something was 
wrong

Ok, so just summarizing our conversation on IRC for others too.

That issue is connected to the different versions of INDENT (C checkstyle) 
installed on the different distros.

openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11

What strikes me is that the upstream repo https://ftp.gnu.org/gnu/indent/ has 
2.2.10 as last revision.
Our indent package maintainer is looking at possible other sources where Indent 
could "live" these days and will let me know as soon as she finds out.

@Thomas Herbert, would you know the source where the Indent package on CentOS 
come from? Maybe that could help...





So generally speaking i would like to question having verify jobs for multiple
distros.
Is there really a value in compiling same code on different distros. Yes I
know gcc version can be different,
but that can be addressed in simpler way, if it needs to be addressed at all.

More distros means more moving parts and bigger chance that something will
fail.
Well, I am not sure how to interpret this but (in theory) a build should be
reproducible in the first place and I should not worry about problems with build
outcomes. It doesn't only affect openSUSE and I raised it many times over the
mailing-list; when you need to run "recheck" multiple times to have a build
succeed. IMHO the issue should be addressed and not solved by putting it under
the carpet...

We all know that we have extreme fragile system, as obviously we are not be 
able to
fix that in almost 2 years, so as long as the system is as it increasing 
complexity doesn't help
and just causes frustration.

Also it cost resources
That is a different matter and if that's the case then it should be discussed
seriously; raising this argument now, after having had people investing their
times in getting stuff up and running isn't really a cool thing...

Marco, decision to have verify jobs on 2 distros was made much before you 
joined the project,
and I don't remember serious decision on that topic, it might be that at that 
time
we were simply unexperienced, or maybe we didn't expect infra to be so fragile.

Fact is that now we have ridiculous situation, 2 verify jobs says patch is OK, 
3rd one says
it is not. Which one to trust?

So please don't take this personal, i know you invested time to get suse build 
working, but still
I think it is a valid question to ask, do we really need 3 verify jobs. Should 
we have 4 tomorrow
if somebody invest his time to do verify job on Archlinux for example?

Thanks,

Damjan



--
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] openSUSE build fails

[Marco Varlese]

Folks,

On Fri, 2017-12-15 at 11:15 +0100, Marco Varlese wrote:
[NIP]
> Ok, so just summarizing our conversation on IRC for others too.
> 
> That issue is connected to the different versions of INDENT (C checkstyle)
> installed on the different distros.
> 
> openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11

A patch has been submitted to circumvent this issue until we can have the same
version of Indent across distros...


[NIP]


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] openSUSE build fails

[Marco Varlese]

Hi Damjan,
On Fri, 2017-12-15 at 09:06 +, Damjan Marion (damarion) wrote:
> 
> 
> 
> > On 15 Dec 2017, at 08:52, Marco Varlese  wrote:
> > 
> > 
> > 
> > Damjan,
> > 
> > 
> > 
> > On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
> > 
> > > Folks,
> > > 
> > > 
> > > 
> > > I'm hearing from multiple people that OpenSUSE verify job is failing
> > > (again).
> > > 
> > 
> > I haven't heard (or read) anything over the mailing list otherwise I would
> > have
> > 
> > looked into it.
> > 
> > Also, if you hear anything like that you can always ping me directly and I
> > will
> > 
> > look into it...
> > 
> > 
> > 
> 
> 
> 
> 
> yes, people pinging me...
> 
> See 
> 
> https://gerrit.fd.io/r/#/c/9440/
> 
> 
> 
> 
> 
> also:
> 
> 
> 
> 
> 
> https://gerrit.fd.io/r/#/c/9813/3/ - abandoned but it shows that something was
> wrong

Ok, so just summarizing our conversation on IRC for others too.
That issue is connected to the different versions of INDENT (C checkstyle)
installed on the different distros.
openSUSE runs 2.2.10 whilst CentOS and Ubuntu run 2.2.11
What strikes me is that the upstream repo https://ftp.gnu.org/gnu/indent/ has
2.2.10 as last revision.Our indent package maintainer is looking at possible
other sources where Indent could "live" these days and will let me know as soon
as she finds out.
@Thomas Herbert, would you know the source where the Indent package on CentOS
come from? Maybe that could help...
> 
> 
> 
> 
> > 
> > > So generally speaking i would like to question having verify jobs for
> > > multiple
> > > 
> > > distros.
> > > 
> > > Is there really a value in compiling same code on different distros. Yes I
> > > 
> > > know gcc version can be different,
> > > 
> > > but that can be addressed in simpler way, if it needs to be addressed at
> > > all.
> > > 
> > > 
> > > 
> > > More distros means more moving parts and bigger chance that something will
> > > 
> > > fail.
> > > 
> > 
> > Well, I am not sure how to interpret this but (in theory) a build should be
> > 
> > reproducible in the first place and I should not worry about problems with
> > build
> > 
> > outcomes. It doesn't only affect openSUSE and I raised it many times over
> > the
> > 
> > mailing-list; when you need to run "recheck" multiple times to have a build
> > 
> > succeed. IMHO the issue should be addressed and not solved by putting it
> > under
> > 
> > the carpet...
> > 
> > 
> > 
> 
> 
> 
> We all know that we have extreme fragile system, as obviously we are not be
> able to
> fix that in almost 2 years, so as long as the system is as it increasing
> complexity doesn't help
> and just causes frustration.
> 
> 
> 
> > > Also it cost resources
> > > 
> > 
> > That is a different matter and if that's the case then it should be
> > discussed
> > 
> > seriously; raising this argument now, after having had people investing
> > their
> > 
> > times in getting stuff up and running isn't really a cool thing...
> > 
> 
> 
> 
> Marco, decision to have verify jobs on 2 distros was made much before you
> joined the project,
> and I don't remember serious decision on that topic, it might be that at that
> time
> we were simply unexperienced, or maybe we didn't expect infra to be so
> fragile.
> 
> 
> 
> Fact is that now we have ridiculous situation, 2 verify jobs says patch is OK,
> 3rd one says
> it is not. Which one to trust?
> 
> 
> 
> So please don't take this personal, i know you invested time to get suse build
> working, but still
> I think it is a valid question to ask, do we really need 3 verify jobs. Should
> we have 4 tomorrow
> if somebody invest his time to do verify job on Archlinux for example?
> 
> 
> 
> Thanks,
> 
> 
> 
> Damjan
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] openSUSE build fails

[Damjan Marion (damarion)]

On 15 Dec 2017, at 08:52, Marco Varlese 
mailto:mvarl...@suse.de>> wrote:

Damjan,

On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
Folks,

I'm hearing from multiple people that OpenSUSE verify job is failing (again).
I haven't heard (or read) anything over the mailing list otherwise I would have
looked into it.
Also, if you hear anything like that you can always ping me directly and I will
look into it...

yes, people pinging me...
See
https://gerrit.fd.io/r/#/c/9440/

also:

https://gerrit.fd.io/r/#/c/9813/ - abandoned but it shows that something was 
wrong



So generally speaking i would like to question having verify jobs for multiple
distros.
Is there really a value in compiling same code on different distros. Yes I
know gcc version can be different,
but that can be addressed in simpler way, if it needs to be addressed at all.

More distros means more moving parts and bigger chance that something will
fail.
Well, I am not sure how to interpret this but (in theory) a build should be
reproducible in the first place and I should not worry about problems with build
outcomes. It doesn't only affect openSUSE and I raised it many times over the
mailing-list; when you need to run "recheck" multiple times to have a build
succeed. IMHO the issue should be addressed and not solved by putting it under
the carpet...

We all know that we have extreme fragile system, as obviously we are not be 
able to
fix that in almost 2 years, so as long as the system is as it increasing 
complexity doesn't help
and just causes frustration.

Also it cost resources
That is a different matter and if that's the case then it should be discussed
seriously; raising this argument now, after having had people investing their
times in getting stuff up and running isn't really a cool thing...

Marco, decision to have verify jobs on 2 distros was made much before you 
joined the project,
and I don't remember serious decision on that topic, it might be that at that 
time
we were simply unexperienced, or maybe we didn't expect infra to be so fragile.

Fact is that now we have ridiculous situation, 2 verify jobs says patch is OK, 
3rd one says
it is not. Which one to trust?

So please don't take this personal, i know you invested time to get suse build 
working, but still
I think it is a valid question to ask, do we really need 3 verify jobs. Should 
we have 4 tomorrow
if somebody invest his time to do verify job on Archlinux for example?

Thanks,

Damjan



___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] openSUSE build fails

[Marco Varlese]

On Fri, 2017-12-15 at 08:52 +0100, Marco Varlese wrote:
> Damjan,
> 
> On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
> > Folks,
> > 
> > I'm hearing from multiple people that OpenSUSE verify job is failing
> > (again).
Would it be possible to have a list (few) of build logs which are failing (or
have failed)?
In that way I could at least see what's happening and come up with some idea...
I went through 3 pages of reviews ion gerrit (even the Verified+1 ones) and I
could find only a single review which failed (once) for openSUSE whilst there
are multiple failures for others.
Any input here would help to get to the bottom of it...
> 
> I haven't heard (or read) anything over the mailing list otherwise I would
> have
> looked into it.
> Also, if you hear anything like that you can always ping me directly and I
> will
> look into it...
> > 
> > So generally speaking i would like to question having verify jobs for
> > multiple
> > distros.
> > Is there really a value in compiling same code on different distros. Yes I
> > know gcc version can be different,
> > but that can be addressed in simpler way, if it needs to be addressed at
> > all.
> > 
> > More distros means more moving parts and bigger chance that something will
> > fail.
> 
> Well, I am not sure how to interpret this but (in theory) a build should be
> reproducible in the first place and I should not worry about problems with
> build
> outcomes. It doesn't only affect openSUSE and I raised it many times over the
> mailing-list; when you need to run "recheck" multiple times to have a build
> succeed. IMHO the issue should be addressed and not solved by putting it under
> the carpet...
> > Also it cost resources
> 
> That is a different matter and if that's the case then it should be discussed
> seriously; raising this argument now, after having had people investing their
> times in getting stuff up and running isn't really a cool thing...
> > 
> > Thoughts?
> > 
> > Damjan
> 
> /Marco
> > 
> > 
> > 
> > ___
> > vpp-dev mailing list
> > vpp-dev@lists.fd.io
> > https://lists.fd.io/mailman/listinfo/vpp-dev
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] openSUSE build fails

[Marco Varlese]

Dear David,
On Thu, 2017-12-14 at 10:01 -1000, David Cornejo wrote:
> I'm a newcomer to this list, so treat my opinion with suspicion...
> I think that there's a governance policy involved. I don't think that the
> committers should feel obligated to support something that is not in their
> interest. OpenSUSE verification needs a champion, and if that champion does
> not emerge than I'd think that the only rational thing to do is to drop it.

That champion would be myself and if it isn't clear to you then I can tell you
that over the past months I worked closely with people from LF to get openSUSE
up and running on FD.io Jenkins jobs. Beside that I am always keen and ready to
offert support to investigate issues with builds on openSUSE. As per my reply to
Damjan, I haven't heard anything this time and his email came out of the blue
for me this morning.
> FreeBSD, for example, has a policy of tiers (see https://www.freebsd.org/doc/e
> n_US.ISO8859-1/articles/committers-guide/archs.html) for platform support.
> Such a system allows for new platforms to get incorporated, but makes it clear
> how they relate to project and responsibilities. Things that exhibit developer
> support move up the tiers to where they are formally fully supported by the
> project. Platforms that fail to maintain developer support move down the tiers
> to their eventual demise. Perhaps a similar policy would work here.
> 
> dave c
> 
> 
> 
> On Thu, Dec 14, 2017 at 6:04 AM, Damjan Marion (damarion) 
> wrote:
> > Folks,
> > 
> > 
> > 
> > I'm hearing from multiple people that OpenSUSE verify job is failing
> > (again).
> > 
> > 
> > 
> > So generally speaking i would like to question having verify jobs for
> > multiple distros.
> > 
> > Is there really a value in compiling same code on different distros. Yes I
> > know gcc version can be different,
> > 
> > but that can be addressed in simpler way, if it needs to be addressed at
> > all.
> > 
> > 
> > 
> > More distros means more moving parts and bigger chance that something will
> > fail.
> > 
> > Also it cost resources
> > 
> > 
> > 
> > Thoughts?
> > 
> > 
> > 
> > Damjan
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > ___
> > 
> > vpp-dev mailing list
> > 
> > vpp-dev@lists.fd.io
> > 
> > https://lists.fd.io/mailman/listinfo/vpp-dev
> > 
> 
> 
> 
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] openSUSE build fails

[Marco Varlese]

Damjan,

On Thu, 2017-12-14 at 16:04 +, Damjan Marion (damarion) wrote:
> Folks,
> 
> I'm hearing from multiple people that OpenSUSE verify job is failing (again).
I haven't heard (or read) anything over the mailing list otherwise I would have
looked into it.
Also, if you hear anything like that you can always ping me directly and I will
look into it...
> 
> So generally speaking i would like to question having verify jobs for multiple
> distros.
> Is there really a value in compiling same code on different distros. Yes I
> know gcc version can be different,
> but that can be addressed in simpler way, if it needs to be addressed at all.
> 
> More distros means more moving parts and bigger chance that something will
> fail.
Well, I am not sure how to interpret this but (in theory) a build should be
reproducible in the first place and I should not worry about problems with build
outcomes. It doesn't only affect openSUSE and I raised it many times over the
mailing-list; when you need to run "recheck" multiple times to have a build
succeed. IMHO the issue should be addressed and not solved by putting it under
the carpet...
> Also it cost resources
That is a different matter and if that's the case then it should be discussed
seriously; raising this argument now, after having had people investing their
times in getting stuff up and running isn't really a cool thing...
> 
> Thoughts?
> 
> Damjan
/Marco
> 
> 
> 
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] openSUSE build fails

[Florin Coras]

Agreed, doing functional testing against one distro should suffice (famous last 
words :-)). 

What do people think about running the verify jobs for the debians and then 
periodically (once per day/week?) run for the other distros, to make sure 
they’re not broken? 

Florin

> On Dec 14, 2017, at 8:04 AM, Damjan Marion (damarion)  
> wrote:
> 
> 
> Folks,
> 
> I'm hearing from multiple people that OpenSUSE verify job is failing (again).
> 
> So generally speaking i would like to question having verify jobs for 
> multiple distros.
> Is there really a value in compiling same code on different distros. Yes I 
> know gcc version can be different,
> but that can be addressed in simpler way, if it needs to be addressed at all.
> 
> More distros means more moving parts and bigger chance that something will 
> fail.
> Also it cost resources
> 
> Thoughts?
> 
> Damjan
> 
> 
> 
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] openSUSE build fails

[David Cornejo]

I'm a newcomer to this list, so treat my opinion with suspicion...

I think that there's a governance policy involved. I don't think that the
committers should feel obligated to support something that is not in their
interest. OpenSUSE verification needs a champion, and if that champion does
not emerge than I'd think that the only rational thing to do is to drop it.

FreeBSD, for example, has a policy of tiers (see
https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/archs.html)
for platform support. Such a system allows for new platforms to get
incorporated, but makes it clear how they relate to project and
responsibilities. Things that exhibit developer support move up the tiers
to where they are formally fully supported by the project. Platforms that
fail to maintain developer support move down the tiers to their eventual
demise. Perhaps a similar policy would work here.

dave c


On Thu, Dec 14, 2017 at 6:04 AM, Damjan Marion (damarion) <
damar...@cisco.com> wrote:

>
> Folks,
>
> I'm hearing from multiple people that OpenSUSE verify job is failing
> (again).
>
> So generally speaking i would like to question having verify jobs for
> multiple distros.
> Is there really a value in compiling same code on different distros. Yes I
> know gcc version can be different,
> but that can be addressed in simpler way, if it needs to be addressed at
> all.
>
> More distros means more moving parts and bigger chance that something will
> fail.
> Also it cost resources
>
> Thoughts?
>
> Damjan
>
>
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>



-- 
Kailua, Hawaiʻi
US +1 (808) 728-3050
UK +44 (020) 3286 2808
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] openSUSE build fails

[Damjan Marion (damarion)]

Folks,

I'm hearing from multiple people that OpenSUSE verify job is failing (again).

So generally speaking i would like to question having verify jobs for multiple 
distros.
Is there really a value in compiling same code on different distros. Yes I know 
gcc version can be different,
but that can be addressed in simpler way, if it needs to be addressed at all.

More distros means more moving parts and bigger chance that something will fail.
Also it cost resources

Thoughts?

Damjan



___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev