On 05/14/2018 02:13 AM, Nigel Babu wrote: > Merging this in and deploying on builders based on Kotresh's +1 to > unblock builds and merges. Ack, checked it 5 minutes ago, let's go with this for now. > > On Mon, May 14, 2018 at 9:49 AM, Nigel Babu <nigelb@xxxxxxxxxx > <mailto:nigelb@xxxxxxxxxx>> wrote: > > This is because of a new warning by liblvm2app. I have a hacky fix > to the compilation process to get rid of the warning. Please review: > https://github.com/gluster/glusterfs-patch-acceptance-tests/pull/130 > <https://github.com/gluster/glusterfs-patch-acceptance-tests/pull/130> > > However, this will soon become more than just a warning. We should > either fix this or completely get rid of bd xlator unless someone > owns it up. > > On Mon, May 14, 2018 at 2:51 AM, Shyam Ranganathan > <srangana@xxxxxxxxxx <mailto:srangana@xxxxxxxxxx>> wrote: > > Hi, > > The builds are failing due to the following, > > https://bugzilla.redhat.com/show_bug.cgi?id=1577668 > <https://bugzilla.redhat.com/show_bug.cgi?id=1577668> > > Nigel/Misc, can you take a stab at finding out what is new that is > causing these warnings to appear? > > Failing a quick resolution there, anyone from maintainers, could you > look at supressing the warnings or fixing them? (bd has no > assigned owners) > > This is important, as quite a few patches are not getting through. > > Shyam > P.S: The bug is marked as a release blocker as well! > > > > > -- > nigelb > > > > > -- > nigelb _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
