[Gluster-devel] [Gluster-Maintainers] Master branch lock down status
Pranith Kumar Karampuri
pkarampu at redhat.com
Wed Aug 8 10:30:52 UTC 2018
On Wed, Aug 8, 2018 at 5:08 AM Shyam Ranganathan <srangana at redhat.com>
> Deserves a new beginning, threads on the other mail have gone deep enough.
> NOTE: (5) below needs your attention, rest is just process and data on
> how to find failures.
> 1) We are running the tests using the patch .
> 2) Run details are extracted into a separate sheet in  named "Run
> Failures" use a search to find a failing test and the corresponding run
> that it failed in.
> 3) Patches that are fixing issues can be found here , if you think
> you have a patch out there, that is not in this list, shout out.
> 4) If you own up a test case failure, update the spreadsheet  with
> your name against the test, and also update other details as needed (as
> comments, as edit rights to the sheet are restricted).
> 5) Current test failures
> We still have the following tests failing and some without any RCA or
> attention, (If something is incorrect, write back).
> ./tests/bugs/replicate/bug-1290965-detect-bitrotten-objects.t (needs
> ./tests/00-geo-rep/georep-basic-dr-tarssh.t (Kotresh)
> ./tests/bugs/ec/bug-1236065.t (Ashish)
> ./tests/00-geo-rep/georep-basic-dr-rsync.t (Kotresh)
> ./tests/basic/ec/ec-1468261.t (needs attention)
> ./tests/basic/afr/add-brick-self-heal.t (needs attention)
> ./tests/basic/afr/granular-esh/replace-brick.t (needs attention)
Sent https://review.gluster.org/#/c/glusterfs/+/20681 for the failure
above. Because it was retried there were no logs. Entry heal succeeded but
data/metadata heal after that didn't succeed. Found only one case based on
code reading and the point at which it failed in .t
> ./tests/bugs/core/multiplex-limit-issue-151.t (needs attention)
> ./tests/bugs/glusterd/validating-server-quorum.t (Atin)
> ./tests/bugs/replicate/bug-1363721.t (Ravi)
> Here are some newer failures, but mostly one-off failures except cores
> in ec-5-2.t. All of the following need attention as these are new.
> 6) Tests that are addressed or are not occurring anymore are,
> Shyam (and Atin)
> On 08/05/2018 06:24 PM, Shyam Ranganathan wrote:
> > Health on master as of the last nightly run  is still the same.
> > Potential patches that rectify the situation (as in ) are bunched in
> > a patch  that Atin and myself have put through several regressions
> > (mux, normal and line coverage) and these have also not passed.
> > Till we rectify the situation we are locking down master branch commit
> > rights to the following people, Amar, Atin, Shyam, Vijay.
> > The intention is to stabilize master and not add more patches that my
> > destabilize it.
> > Test cases that are tracked as failures and need action are present here
> > .
> > @Nigel, request you to apply the commit rights change as you see this
> > mail and let the list know regarding the same as well.
> > Thanks,
> > Shyam
> >  Patches that address regression failures:
> > https://review.gluster.org/#/q/starredby:srangana%2540redhat.com
> >  Bunched up patch against which regressions were run:
> > https://review.gluster.org/#/c/20637
> >  Failing tests list:
> >  Nightly run dashboard: https://build.gluster.org/job/nightly-master/
> maintainers mailing list
> maintainers at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-devel