Re: [Gluster-devel] [Gluster-Maintainers] Master branch lock down for stabilization (unlocking the same)

On Mon, Aug 13, 2018 at 6:05 AM Shyam Ranganathan wrote: > Hi, > > So we have had master locked down for a week to ensure we only get fixes > for failing tests in order to stabilize the code base, partly for > release-5 branching as well. > > As of this weekend, we (Atin and myself) have been loo

Re: [Gluster-devel] Master branch lock down: RCA for tests (ec-1468261.t)

Correction. RCA - https://lists.gluster.org/pipermail/gluster-devel/2018-August/055167.html Patch - Mohit is working on this patch (server side) which is yet to be merged. We can put extra test to make sure bricks are connected to shd before heal begin. Will send a patch for that. --- Ashi

Re: [Gluster-devel] Master branch lock down: RCA for tests (ec-1468261.t)

RCA - https://lists.gluster.org/pipermail/gluster-devel/2018-August/055167.html Patch - https://review.gluster.org/#/c/glusterfs/+/20657/ should also fix this issue. Checking if we can put extra test to make sure bricks are connected to shd before heal begin. Will send a patch for that. ---

Re: [Gluster-devel] [Gluster-Maintainers] Master branch lock down: RCA for tests ( ./tests/bugs/quick-read/bug-846240.t)

Failure is tracked by bz: https://bugzilla.redhat.com/show_bug.cgi?id=1615096 Earlier this test did following things on M0 and M1 mounted on same volume: 1 create file M0/testfile 2 open an fd on M0/testfile 3 remove the file from M1, M1/testfile 4 echo "data" >> M0/testfile

Re: [Gluster-devel] [Gluster-Maintainers] Master branch lock down: RCA for tests (bugs/distribute/bug-1122443.t)

Initial RCA to point out commit 7131de81f72dda0ef685ed60d0887c6e14289b8c caused the issue was done by Nithya. Following was the conversation: With the latest master, I created a single brick volume and some files inside it. [root@rhgs313-6 ~]# umount -f /mnt/fuse1; mount -t glusterfs -s

Re: [Gluster-devel] gluster fuse comsumes huge memory

https://drive.google.com/file/d/1ZlttTzt4E56Qtk9j7b4I9GkZC2W3mJgp/view?usp=sharingHi exports:    I upload the statedump file to the google drive, could you please help me find what is the cause of gluster fuse comsuming huge memory? Thank you! huting3

Re: [Gluster-devel] [Gluster-Maintainers] Master branch lock down: RCA for tests (bug-1368312.t)

Failure of this test is tracked by bz https://bugzilla.redhat.com/ show_bug.cgi?id=1608158. I was trying to debug regression failures on [1] and observed that split-brain-resolution.t was failing consistently. = TEST 45 (line 88): 0 get_pending_heal_count patchy ./tests/

Re: [Gluster-devel] [Gluster-Maintainers] bug-1368312.t

Failure of this test is tracked by bz https://bugzilla.redhat.com/show_bug.cgi?id=1608158. I was trying to debug regression failures on [1] and observed that split-brain-resolution.t was failing consistently. = TEST 45 (line 88): 0 get_pending_heal_count patchy ./tests/b

[Gluster-devel] Weekly Untriaged Bugs

[...truncated 6 lines...] https://bugzilla.redhat.com/1601356 / core: Problem with SSL/TLS encryption on Gluster 4.0 & 4.1 https://bugzilla.redhat.com/1605066 / disperse: RFE: Need to optimize on time taken by heal info to display o/p when large number of entries exist https://bugzilla.redhat.com

Re: [Gluster-devel] Master branch lock down: RCA for tests (testname.t)

As a means of keeping the focus going and squashing the remaining tests that were failing sporadically, request each test/component owner to, - respond to this mail changing the subject (testname.t) to the test name that they are responding to (adding more than one in case they have the same RCA)

[Gluster-devel] Master branch lock down for stabilization (unlocking the same)

Hi, So we have had master locked down for a week to ensure we only get fixes for failing tests in order to stabilize the code base, partly for release-5 branching as well. As of this weekend, we (Atin and myself) have been looking at the pass/fail rates on the tests, and whether we are discoverin

Re: [Gluster-devel] Master branch lock down status (Aug 12th, 2018) (patchset 12)

Patch set 12 results: ./tests/bugs/glusterd/quorum-validation.t (3 retries, 1 core) ./tests/bugs/glusterd/validating-server-quorum.t (1 core) (NEW) ./tests/basic/distribute/rebal-all-nodes-migrate.t (1 retry) ./tests/basic/stats-dump.t (1 retry) ./tests/bugs/shard/bug-1251824.t (1 retry) ./tests/b

Re: [Gluster-devel] Master branch lock down status (Patch set 11, Aug 12, 2018)

Patch set 11 report: line coverage: 4/8 PASS, 7/8 with retries, 1 core CentOS regression: 5/8 PASS, 8/8 PASS-With-RETRIES Mux regression: 7/8 PASS, 1 core No NEW failures, sheet [1] updated with run details, and so is the WIP patch with the same data [2]. Cores: - ./tests/bugs/glusterd/validatin

Re: [Gluster-devel] Master branch lock down status (Wed, August 08th)

On Sun, Aug 12, 2018 at 9:11 AM, Raghavendra Gowdappa wrote: > > > On Sat, Aug 11, 2018 at 10:33 PM, Shyam Ranganathan > wrote: > >> On 08/09/2018 10:58 PM, Raghavendra Gowdappa wrote: >> > >> > >> > On Fri, Aug 10, 2018 at 1:38 AM, Shyam Ranganathan > > > wrote: >> >

[Gluster-devel] Trello may automatically add comments to GitHub Issues/PRs/...

Hi, Today I just noticed that my Trello updates to a private board (for an internal Red Hat project) added comments to GitHub PRs. In this case, it was not really much of a problem, except that non-board members would not have access to the linked card. This is obviously very community unfriendly.