Re: [Gluster-devel] [Gluster-infra] freebsd-smoke failures

2016-04-22 Thread Polakis Vaggelis
thx for the support! by the way same problem also occurs in review http://review.gluster.org/#/c/14045/ br, vangelis On Tue, Apr 19, 2016 at 5:01 PM, Michael Scherer wrote: > Le mardi 19 avril 2016 à 09:58 -0400, Jeff Darcy a écrit : >> > So can a workable solution be

Re: [Gluster-devel] [Gluster-infra] freebsd-smoke failures

2016-04-19 Thread Michael Scherer
Le mardi 19 avril 2016 à 09:58 -0400, Jeff Darcy a écrit : > > So can a workable solution be pushed to git, because I plan to force the > > checkout to be like git, and it will break again (and this time, no > > workaround will be possible). > > > > It has been pushed to git, but AFAICT pull

Re: [Gluster-devel] [Gluster-infra] freebsd-smoke failures

2016-04-19 Thread Jeff Darcy
> So can a workable solution be pushed to git, because I plan to force the > checkout to be like git, and it will break again (and this time, no > workaround will be possible). > It has been pushed to git, but AFAICT pull requests for that repo go into a black hole.

Re: [Gluster-devel] [Gluster-infra] freebsd-smoke failures

2016-04-19 Thread Michael Scherer
Le samedi 02 avril 2016 à 07:53 -0400, Jeff Darcy a écrit : > > IIRC, this happens because in the build job use "--enable-bd-xlator" > > option while configure > > I came to the same conclusion, and set --enable-bd-xlator=no on the > slave. I also had to remove -Werror because that was also

Re: [Gluster-devel] [Gluster-infra] freebsd-smoke failures

2016-04-04 Thread Michael Scherer
Le lundi 04 avril 2016 à 08:54 -0400, Jeff Darcy a écrit : > > Once this was done, I pushed to use the regular upstream change, > > something that was not done before since the local change broke > > automation to deploy test suite on Freebsd. > > It looks like we have two options here: > > (1)

Re: [Gluster-devel] [Gluster-infra] freebsd-smoke failures

2016-04-04 Thread Jeff Darcy
> Once this was done, I pushed to use the regular upstream change, > something that was not done before since the local change broke > automation to deploy test suite on Freebsd. It looks like we have two options here: (1) Fix configure so that it accurately detects whether the system can/should

Re: [Gluster-devel] [Gluster-infra] freebsd-smoke failures

2016-04-04 Thread Niels de Vos
On Sat, Apr 02, 2016 at 11:04:48AM -0400, Jeff Darcy wrote: > > Please make sure that this change also gets included in the repository: > > > > https://github.com/gluster/glusterfs-patch-acceptance-tests > > Looks like we're getting a bit of a queue there. Who can merge some of > these? I

Re: [Gluster-devel] [Gluster-infra] freebsd-smoke failures

2016-04-02 Thread Jeff Darcy
> Please make sure that this change also gets included in the repository: > > https://github.com/gluster/glusterfs-patch-acceptance-tests Looks like we're getting a bit of a queue there. Who can merge some of these? ___ Gluster-devel mailing list

Re: [Gluster-devel] [Gluster-infra] freebsd-smoke failures

2016-04-02 Thread Jeff Darcy
- Original Message - > On Sat, Apr 02, 2016 at 07:53:32AM -0400, Jeff Darcy wrote: > > > IIRC, this happens because in the build job use "--enable-bd-xlator" > > > option while configure > > > > I came to the same conclusion, and set --enable-bd-xlator=no on the > > slave. I also had

Re: [Gluster-devel] [Gluster-infra] freebsd-smoke failures

2016-04-02 Thread Niels de Vos
On Sat, Apr 02, 2016 at 07:53:32AM -0400, Jeff Darcy wrote: > > IIRC, this happens because in the build job use "--enable-bd-xlator" > > option while configure > > I came to the same conclusion, and set --enable-bd-xlator=no on the > slave. I also had to remove -Werror because that was also

Re: [Gluster-devel] [Gluster-infra] freebsd-smoke failures

2016-04-02 Thread Jeff Darcy
> IIRC, this happens because in the build job use "--enable-bd-xlator" > option while configure I came to the same conclusion, and set --enable-bd-xlator=no on the slave. I also had to remove -Werror because that was also causing failures. FreeBSD smoke is now succeeding.

Re: [Gluster-devel] [Gluster-infra] freebsd-smoke failures

2016-04-02 Thread Prasanna Kalever
On Sat, Apr 2, 2016 at 2:13 AM, Jeff Darcy wrote: > > I've seen a lot of patches blocked lately by this: > > > BD xlator requested but required lvm2 development library not found. > Hi Jeff, IIRC, this happens because in the build job use "--enable-bd-xlator" option while