On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan wrote:
>
> On 05/31/2018 09:22 AM, Shyam Ranganathan wrote:
> > As brick-mux tests were failing (and still are on master), this was
> > holding up the release activity.
> >
> > We now have a final fix [1] for the problem, and the situation has
> >
On 05/31/2018 09:22 AM, Shyam Ranganathan wrote:
> As brick-mux tests were failing (and still are on master), this was
> holding up the release activity.
>
> We now have a final fix [1] for the problem, and the situation has
> improved over a series of fixes and reverts on the 4.1 branch as well.
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-06-01-b21f742f
___
Gluster-devel mailing list
Gluster-devel@gluster.org
Thanks Nigel for initiating this email. This is a pending (and critical)
task for us to get back on to it and take it to completion as getting a
confidence on overall gluster features to work with GD2, its a very
important task for us. Its just that in 4.1 team was busy in finishing some
of the
Hello,
We're nearly at 4.1 release, I think now is a time to decide when to flip
the switch to default to GD2 server for all regressions or a nightly GD2
run against the current regression.
Can someone help with what tasks need to be done for this to be
accomplished and how the CI team can help.
