On 07/30/2018 03:21 PM, Shyam Ranganathan wrote: > On 07/24/2018 03:12 PM, Shyam Ranganathan wrote: >> 1) master branch health checks (weekly, till branching) >> - Expect every Monday a status update on various tests runs > > See https://build.gluster.org/job/nightly-master/ for a report on > various nightly and periodic jobs on master. Thinking aloud, we may have to stop merges to master to get these test failures addressed at the earliest and to continue maintaining them GREEN for the health of the branch. I would give the above a week, before we lockdown the branch to fix the failures. Let's try and get line-coverage and nightly regression tests addressed this week (leaving mux-regression open), and if addressed not lock the branch down. > > RED: > 1. Nightly regression (3/6 failed) > - Tests that reported failure: > ./tests/00-geo-rep/georep-basic-dr-rsync.t > ./tests/bugs/core/bug-1432542-mpx-restart-crash.t > ./tests/bugs/replicate/bug-1586020-mark-dirty-for-entry-txn-on-quorum-failure.t > ./tests/bugs/distribute/bug-1122443.t > > - Tests that needed a retry: > ./tests/00-geo-rep/georep-basic-dr-tarssh.t > ./tests/bugs/glusterd/quorum-validation.t > > 2. Regression with multiplex (cores and test failures) > > 3. line-coverage (cores and test failures) > - Tests that failed: > ./tests/bugs/core/bug-1432542-mpx-restart-crash.t (patch > https://review.gluster.org/20568 does not fix the timeout entirely, as > can be seen in this run, > https://build.gluster.org/job/line-coverage/401/consoleFull ) > > Calling out to contributors to take a look at various failures, and post > the same as bugs AND to the lists (so that duplication is avoided) to > get this to a GREEN status. > > GREEN: > 1. cpp-check > 2. RPM builds > > IGNORE (for now): > 1. clang scan (@nigel, this job requires clang warnings to be fixed to > go green, right?) > > Shyam > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > https://lists.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel