On Tue, Apr 25, 2017 at 12:50:45PM -0400, Jeff Darcy wrote:
>
>
>
> 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
On Tue, 25 Apr 2017 at 10:21 PM, Jeff Darcy wrote:
>
>
>
> 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 regr
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 enab
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
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
