[Gluster-devel] upstream regression suite is broken

[Nigel Babu]

Hello,

I've spoken to Atin, Ravi, and Amar and we agreed on a solution that I've just
completed.

1. I've landed a patch directly on master bypassing review. This patch will
   disabling the test that is currently failing. Now patches that are waiting
   to land in master can be landed safely while we get regressions to run on
   Ravi's patch
2. Ravi can rebase his patch on HEAD of master and re-enable the test along
   with his fix.

We've talked about this use-case in the past and how to best handle a broken
master. I'll work on a guide to handling this sort of incidents in the future.

On Fri, Jul 07, 2017 at 10:48:42AM +0530, Ravishankar N wrote:
> I've sent a fix @ https://review.gluster.org/#/c/17721
>
> On 07/07/2017 09:51 AM, Atin Mukherjee wrote:
> > Krutika,
> >
> > tests/basis/stats-dump.t is failing all the time and as per my initial
> > analysis after https://review.gluster.org/#/c/17709/ got into the
> > mainline the failures are seen and reverting this patch makes the test
> > to run successfully. I do understand that the centos vote for this patch
> > was green but the last run was on 5th June which was 1 month back. So
> > some other changes have gone into in between which is now causing this
> > patch to break the test.
> >
> > This makes me think as a maintainer we do need to ensure the if the
> > regression vote on the patch is quite old, a rebase of the patch is must
> > to be on the safer side?
> >

--
nigelb