> 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-infra mailing list
Glu
- 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 to
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 causi
> 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.
___
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 configure;
but looks lik
