[Gluster-infra] Nightly regression job with enabling brick multiplexing

Jeff Darcy jeff at pl.atyp.us
Tue Apr 25 16:50:45 UTC 2017

On Mon, Apr 24, 2017, at 11:52 AM, Jeff Darcy wrote:
> On Fri, Apr 21, 2017, at 09:17 AM, Atin Mukherjee wrote:
>> As we don't run our .t files with brick mux being enabled for every
>> patches can we ensure that there is a nightly regression trigger with
>> brick multiplexing feature being enabled. The reason for this ask is
>> very simple, we have no control on the regression for this feature.
>> I've already seen a very basic test (volume status not reflecting
>> bricks online after glusterd restart) breaking recently which used to
>> work earlier.> 
> +100

FWIW, the way I ran these tests during development was to have a patch
that makes multiplexing the default.  I'd periodically rebase that on
top of whatever else was current, then run regressions on that.  To do
that as part of a periodic test, we'd need the regression scripts to
look for that same patch in some "well known place" and apply it before
building.  Is that something that somebody else would feel comfortable
implementing, or should I look into it?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-infra/attachments/20170425/c323caac/attachment.html>

More information about the Gluster-infra mailing list