Le samedi 02 avril 2016 à 16:36 +0200, Niels de Vos a écrit : > 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 causing > > failures. FreeBSD smoke is now succeeding. > > Please make sure that this change also gets included in the repository: > > https://github.com/gluster/glusterfs-patch-acceptance-tests > > I always thought the bd-xlator was Linux only because it depends on LVM. > Does anyone have an idea why this suddenly(?) got enabled on FreeBSD? Likely me, I did merge most of the changes that diverged from the checkout, since people did change the slave without committing back. 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. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
