Re: [Gluster-devel] Release 6.2: Expected tagging on May 15th

These patches were dependent on each other, so a merge was not required to get regression passing, that analysis seems incorrect. A patch series when tested, will pull in all the dependent patches anyway, so please relook at what the failure could be. (I assume you would anyway). Shyam On 5/17

[Gluster-devel] Announcing Gluster release 6.1

The Gluster community is pleased to announce the release of Gluster 6.1 (packages available at [1]). Release notes for the release can be found at [2]. Major changes, features and limitations addressed in this release: None Thanks, Gluster community [1] Packages for 6.1:

Re: [Gluster-devel] Release 6.1: Tagged!

Is now tagged and being packaged. If anyone gets a chance, please test the packages from CentOS SIG, as I am unavailable for the next 4 days. Thanks, Shyam On 4/16/19 9:53 AM, Shyam Ranganathan wrote: > Status: Tagging pending > > Waiting on patches: > (Kotresh/Atin) - glusterd:

Re: [Gluster-devel] Release 6.1: Expected tagging on April 10th

a disperse volume when replace-brick is executed Very recent bug (15th April), does not seem to have any critical data corruption or service availability issues, planning on not waiting for the fix in 6.1 - Shyam On 4/6/19 4:38 AM, Atin Mukherjee wrote: > Hi Mohit, > > https://review.glust

[Gluster-devel] Release 6.1: Expected tagging on April 10th

Hi, Expected tagging date for release-6.1 is on April, 10th, 2019. Please ensure required patches are backported and also are passing regressions and are appropriately reviewed for easy merging and tagging on the date. Thanks, Shyam ___ Gluster-devel

[Gluster-devel] Announcing Gluster release 4.1.8

The Gluster community is pleased to announce the release of Gluster 4.1.8 (packages available at [1]). Release notes for the release can be found at [2]. Major changes, features and limitations addressed in this release: None Thanks, Gluster community [1] Packages for 4.1.8:

[Gluster-devel] Announcing Gluster Release 6

The Gluster community is pleased to announce the release of 6.0, our latest release. This is a major release that includes a range of code improvements and stability fixes along with a few features as noted below. A selection of the key features and bugs addressed are documented in this [1]

Re: [Gluster-devel] Gluster version EOL date

for the release. Shyam [1] Release schedule: https://www.gluster.org/release-schedule/ On 3/22/19 6:45 AM, ABHISHEK PALIWAL wrote: > Hi, > > As per gluster community seems the latest version is 5.5. Could any one > tell me what would be the EOL date for version 5.5? is it after 12 month >

[Gluster-devel] Release 6: Tagged and ready for packaging

up, we would be writing the upgrade guide for the release as well, before announcing the release for general consumption. Shyam ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-Maintainers] GlusterFS - 6.0RC - Test days (27th, 28th Feb)

On 3/4/19 12:33 PM, Shyam Ranganathan wrote: > On 3/4/19 10:08 AM, Atin Mukherjee wrote: >> >> >> On Mon, 4 Mar 2019 at 20:33, Amar Tumballi Suryanarayan >> mailto:atumb...@redhat.com>> wrote: >> >> Thanks to those who participated. >> >

Re: [Gluster-devel] [Gluster-Maintainers] GlusterFS - 6.0RC - Test days (27th, 28th Feb)

On 3/4/19 10:08 AM, Atin Mukherjee wrote: > > > On Mon, 4 Mar 2019 at 20:33, Amar Tumballi Suryanarayan > mailto:atumb...@redhat.com>> wrote: > > Thanks to those who participated. > > Update at present: > > We found 3 blocker bugs in upgrade scenarios, and hence have marked >

Re: [Gluster-devel] [Gluster-Maintainers] glusterfs-6.0rc0 released

during the test phase. Please take this time to help make the release effective, by testing the same. Thanks, Shyam NOTE: CentOS StorageSIG packages for the same are still pending and should be available in due course. On 2/23/19 9:41 AM, Kaleb Keithley wrote: > > GlusterFS 6.0rc0 is built in

Re: [Gluster-devel] Release 6: Branched and next steps

On 2/20/19 7:45 AM, Amar Tumballi Suryanarayan wrote: > > > On Tue, Feb 19, 2019 at 1:37 AM Shyam Ranganathan <mailto:srang...@redhat.com>> wrote: > > In preparation for RC0 I have put up an intial patch for the release > notes [1]. Request the following

Re: [Gluster-devel] Release 6: Branched and next steps

used in the brick process" and the actual status of the same in the notes RC0 build target would be tomorrow or by Wednesday. Thanks, Shyam [1] Release notes patch: https://review.gluster.org/c/glusterfs/+/6 On 2/5/19 8:25 PM, Shyam Ranganathan wrote: > Hi, > > Release 6 is br

[Gluster-devel] Release 6: Branched and next steps

and other testing close to mid-week next week (around 13th Feb), and the release is slated for the first week of March for GA. I will post updates to this thread around release notes and other related activity. Thanks, Shyam [1] Tracker: https://bugzilla.redhat.com/show_bug.cgi?id=gluster

Re: [Gluster-devel] Release 6: Kick off!

On 1/24/19 3:23 AM, Soumya Koduri wrote: > Hi Shyam, > > Sorry for the late response. I just realized that we had two more new > APIs glfs_setattr/fsetattr which uses 'struct stat' made public [1]. As > mentioned in one of the patchset review comments, since the goal is to >

Re: [Gluster-devel] Release 6: Kick off!

On 1/23/19 6:03 AM, Ashish Pandey wrote: > > Following is the patch I am working and targeting -  > https://review.gluster.org/#/c/glusterfs/+/21933/ This is a bug fix, and the patch size at the moment is also small in lines changed. Hence, even if it misses branching the fix can be backported.

Re: [Gluster-devel] Release 6: Kick off!

On 1/23/19 5:52 AM, RAFI KC wrote: > There are three patches that I'm working for Gluster-6. > > [1] : https://review.gluster.org/#/c/glusterfs/+/22075/ We discussed mux for shd in the maintainers meeting, and decided that this would be for the next release, as the patchset is not ready

Re: [Gluster-devel] Release 6: Kick off!

On 12/6/18 9:34 AM, Shyam Ranganathan wrote: > On 11/6/18 11:34 AM, Shyam Ranganathan wrote: >> ## Schedule > > We have decided to postpone release-6 by a month, to accommodate for > late enhancements and the drive towards getting what is required for the > GCS project [1] d

Re: [Gluster-devel] Regression health for release-5.next and release-6

-replicated-volume-options.t Shyam On 1/10/19 6:20 AM, Mohit Agrawal wrote: > I think we should consider regression-builds after merged the patch > (https://review.gluster.org/#/c/glusterfs/+/21990/)  > as we know this patch introduced some delay. > > Thanks, > Mohit Agrawal &

[Gluster-devel] Regression health for release-5.next and release-6

this issue as a response to this mail. Thanks, Shyam [1] Regression failures: https://hackmd.io/wsPgKjfJRWCP8ixHnYGqcA?view ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] https://review.gluster.org/#/c/glusterfs/+/19778/

On 1/8/19 8:33 AM, Nithya Balachandran wrote: > Shyam, what is your take on this? > An upstream user has tried it out and reported that it seems to fix the > issue , however cpu utilization doubles. We usually do not backport big fixes unless they are critical. My first answer would

[Gluster-devel] Announcing Gluster release 5.2

The Gluster community is pleased to announce the release of Gluster 5.2 (packages available at [1]). Release notes can be found at [2]. Major changes, features and limitations addressed in this release: - Several bugs as listed in the release notes have been addressed Thanks, Gluster community

Re: [Gluster-devel] Release 6: Kick off!

On 11/6/18 11:34 AM, Shyam Ranganathan wrote: > ## Schedule We have decided to postpone release-6 by a month, to accommodate for late enhancements and the drive towards getting what is required for the GCS project [1] done in core glusterfs. This puts the (modified) schedule for Releas

[Gluster-devel] Patches in merge conflict

, using the gerrit UI, or manually if that fails. Thanks, Shyam ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Geo-rep tests failing on master Cent7-regressions

Hi Kotresh, Multiple geo-rep tests are failing on master on various patch regressions. Looks like you have put in https://review.gluster.org/c/glusterfs/+/21794 for review, to address the issue at present. Would that be correct? Thanks, Shyam

[Gluster-devel] Problem: Include libglusterfs files in gfapi headers

tree, and also help with providing a pkgconfig for glusterffs-devel IMO. Comments and other thoughts? Shyam [1] Commit introducing statx: https://review.gluster.org/c/glusterfs/+/19802 [2] Inclusion of the header: https://review.gluster.org/c/glusterfs/+/19802/9/api/src/glfs.h#54 [3] Include

[Gluster-devel] Release 4.1.7 & 5.2

://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.2 - Deadline for fixes: 2018-12-10 Thanks, Shyam ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Regression failure: https://build.gluster.org/job/centos7-regression/3678/

On 11/14/2018 10:04 AM, Nithya Balachandran wrote: > Hi Mohit, > > The regression run in the subject has failed because a brick has crashed in  > > bug-1432542-mpx-restart-crash.t > > > *06:03:38* 1 test(s) generated core > *06:03:38* ./tests/bugs/core/bug-1432542-mpx-restart-crash.t >

Re: [Gluster-devel] Gluster Weekly Report : Static Analyser

On 11/06/2018 02:08 PM, Shyam Ranganathan wrote: > Hi, > > I was attempting to fix a class of "Insecure data handling" defects in > coverity around GF_FREE accessing tainted strings. Below is a short > writeup of the same (pasted into the notes for each issue as we

Re: [Gluster-devel] Gluster Weekly Report : Static Analyser

ccessing the same. As a result, these instances are marked as false positives An older thread discussing this from Xavi can be found here: https://lists.gluster.org/pipermail/gluster-devel/2014-December/043314.html Shyam On 11/02/2018 01:07 PM, Sunny Kumar wrote: > Hello folks, > >

[Gluster-devel] Release 6: Kick off!

do consider. We need more hands this time, and possibly some time sharing during the end of the year owing to the holidays. Thanks, Shyam [1] Release-6 github milestone: https://github.com/gluster/glusterfs/milestone/8 [2] Release-6 enhancement wishlist: https://hackmd.io/sP5GsZ-uQpqnmGZmFKuWIg

Re: [Gluster-devel] Consolidating Feature Requests in github

On 11/05/2018 08:29 AM, Vijay Bellur wrote: > Hi All, > > I am triaging the open RFEs in bugzilla [1]. Since our new(er) workflow > involves managing RFEs as github issues, I am considering migrating > relevant open RFEs from bugzilla to github. Once migrated, a RFE in > bugzilla would be closed

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: GA Tagged and release tarball generated

). Thanks, Shyam ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: GA tomorrow!

On 10/15/2018 02:29 PM, Shyam Ranganathan wrote: > On 10/11/2018 11:25 AM, Shyam Ranganathan wrote: >> So we are through with a series of checks and tasks on release-5 (like >> ensuring all backports to other branches are present in 5, upgrade >> testing, basic performance tes

Re: [Gluster-devel] [Gluster-users] Announcing Glusterfs release 3.12.15 (Long Term Maintenance)

On 10/17/2018 07:08 AM, Paolo Margara wrote: > Hi, > > this release will be the last of the 3.12.x branch prior it reach the EOL? Yes that is true, this would be the last minor release, as release-5 comes out. > > > Greetings, > >     Paolo > > Il 16/10/18 17:41, Jiffin Tony Thottan ha

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: GA and what are we waiting on

On 10/11/2018 11:25 AM, Shyam Ranganathan wrote: > So we are through with a series of checks and tasks on release-5 (like > ensuring all backports to other branches are present in 5, upgrade > testing, basic performance testing, Package testing, etc.), but still > need the following r

[Gluster-devel] Maintainer meeting minutes : 15th Oct, 2018

### BJ Link * Bridge: https://bluejeans.com/217609845 * Watch: ### Attendance * Nigel, Nithya, Deepshikha, Akarsha, Kaleb, Shyam, Sunny ### Agenda * AI from previous meeting: - Glusto-Test completion on release-5 branch - On Glusto team - Vijay will take this on. - He

[Gluster-devel] Release 5: GA and what are we waiting on

are attempting to get a regression run on a Python3 platform, but that maybe a little ways away from the release (see: https://bugzilla.redhat.com/show_bug.cgi?id=1638030 ) Request attention to the above, to ensure we are not breaking things with the release. Thanks, Shyam

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: Missing option documentation (need inputs)

On 10/10/2018 11:20 PM, Atin Mukherjee wrote: > > > On Wed, 10 Oct 2018 at 20:30, Shyam Ranganathan <mailto:srang...@redhat.com>> wrote: > > The following options were added post 4.1 and are part of 5.0 as the > first release for the same. They we

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: Branched and further dates

On 09/26/2018 10:21 AM, Shyam Ranganathan wrote: > 3. Upgrade testing > - Need *volunteers* to do the upgrade testing as stated in the 4.1 > upgrade guide [3] to note any differences or changes to the same > - Explicit call out on *disperse* volumes, as we continue to state >

[Gluster-devel] Nightly build status (week of 01 - 07 Oct, 2018)

We have a set of 4 cores which seem to originate from 2 bugs as filed and referenced below. Bug 1: https://bugzilla.redhat.com/show_bug.cgi?id=1636570 Cleanup sequence issues in posix xlator. Mohit/Xavi/Du/Pranith are we handling this as a part of addressing cleanup in brick mux, or should we?

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: Branched and further dates

On 10/05/2018 10:59 AM, Shyam Ranganathan wrote: > On 10/04/2018 11:33 AM, Shyam Ranganathan wrote: >> On 09/13/2018 11:10 AM, Shyam Ranganathan wrote: >>> RC1 would be around 24th of Sep. with final release tagging around 1st >>> of Oct. >> RC1 now stands t

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: Branched and further dates

On 10/04/2018 11:33 AM, Shyam Ranganathan wrote: > On 09/13/2018 11:10 AM, Shyam Ranganathan wrote: >> RC1 would be around 24th of Sep. with final release tagging around 1st >> of Oct. > > RC1 now stands to be tagged tomorrow, and patches that are being > targeted for

Re: [Gluster-devel] Release 5: Branched and further dates

On 10/04/2018 12:01 PM, Atin Mukherjee wrote: > 4) This bug [2] was filed when we released 4.0. > > The issue has not bitten us in 4.0 or in 4.1 (yet!) (i.e the options > missing and hence post-upgrade clients failing the mount). This is > possibly the last chance to fix it. > >

Re: [Gluster-devel] Release 5: Branched and further dates

On 09/13/2018 11:10 AM, Shyam Ranganathan wrote: > RC1 would be around 24th of Sep. with final release tagging around 1st > of Oct. RC1 now stands to be tagged tomorrow, and patches that are being targeted for a back port include, 1) https://review.gluster.org/c/glusterfs/+/21314 (sn

Re: [Gluster-devel] [Gluster-Maintainers] Memory overwrites due to processing vol files???

We tested with ASAN and without the fix at [1], and it consistently crashes at the mdcache xlator when brick mux is enabled. On 09/28/2018 03:50 PM, FNU Raghavendra Manjunath wrote: > > I was looking into the issue and  this is what I could find while > working with shyam. > > The

Re: [Gluster-devel] Python3 build process

On 09/28/2018 09:11 AM, Niels de Vos wrote: > On Fri, Sep 28, 2018 at 08:57:06AM -0400, Shyam Ranganathan wrote: >> On 09/28/2018 06:12 AM, Niels de Vos wrote: >>> On Thu, Sep 27, 2018 at 08:40:54AM -0400, Shyam Ranganathan wrote: >>>> On 09/27/2018 08:

Re: [Gluster-devel] Python3 build process

On 09/28/2018 12:36 AM, Kotresh Hiremath Ravishankar wrote: > > - All regression hosts are currently py2 and so if we do not run > the py > > shebang correction during configure (as we do not build and test from > > RPMS), we would be running with incorrect py3 shebangs (although

Re: [Gluster-devel] Python3 build process

On 09/28/2018 06:12 AM, Niels de Vos wrote: > On Thu, Sep 27, 2018 at 08:40:54AM -0400, Shyam Ranganathan wrote: >> On 09/27/2018 08:07 AM, Kaleb S. KEITHLEY wrote: >>>> The thought is, >>>> - Add a configure option "--enable-py-version-correction" to

Re: [Gluster-devel] Python3 build process

On 09/27/2018 08:07 AM, Kaleb S. KEITHLEY wrote: >> The thought is, >> - Add a configure option "--enable-py-version-correction" to configure, >> that is disabled by default > "correction" implies there's something that's incorrect. How about > "conversion" or perhaps just --enable-python2 > I

Re: [Gluster-devel] [Gluster-Maintainers] Memory overwrites due to processing vol files???

On 09/26/2018 10:21 AM, Shyam Ranganathan wrote: > 2. Testing dashboard to maintain release health (new, thanks Nigel) > - Dashboard at [2] > - We already have 3 failures here as follows, needs attention from > appropriate *maintainers*, > (a) > https://build.gluster.

[Gluster-devel] Python3 build process

the right python shebangs on these machines. - The packaging jobs will now run the py version detection and shebang correction during actual build and packaging, Kaleb already has put up a patch for the same [2]. Thoughts? Shyam [1] Release tarball: https://build.gluster.org/job/release-new/69/

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: Branched and further dates

support around changed python files, if there is not enough coverage in the regression test suite for the same Thanks, Shyam [1] Packages for RC0: https://lists.gluster.org/pipermail/maintainers/2018-September/005044.html [2] Release testing health dashboard: https://build.gluster.org/job/nightly

[Gluster-devel] Release 5: Branched and further dates

be around 24th of Sep. with final release tagging around 1st of Oct. I would like to encourage everyone to test out the bits as appropriate and post updates to this thread. Thanks, Shyam [1] 5.0 tracker: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.0

Re: [Gluster-devel] Release 5: Release calendar and status updates

On 08/22/2018 02:03 PM, Shyam Ranganathan wrote: > On 08/14/2018 02:28 PM, Shyam Ranganathan wrote: >> 2) Branching date: (Monday) Aug-20-2018 (~40 days before GA tagging) > > We are postponing branching to 2nd week of September (10th), as the > entire effort in this relea

Re: [Gluster-devel] Proposal to change Gerrit -> Bugzilla updates

On 09/10/2018 08:37 AM, Nigel Babu wrote: > Hello folks, > > We now have review.gluster.org as an > external tracker on Bugzilla. Our current automation when there is a > bugzilla attached to a patch is as follows: > > 1. When a new patchset has "Fixes: bz#1234" or

[Gluster-devel] Test health report (week ending 26th Aug, 2018)

/regression-test-with-multiplex/839/consoleText Multiple failures, look related to some infra issue at that point, not recording the same in the mail. Shyam ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster

Re: [Gluster-devel] Release 5: Release calendar and status updates

On 08/14/2018 02:28 PM, Shyam Ranganathan wrote: > 2) Branching date: (Monday) Aug-20-2018 (~40 days before GA tagging) We are postponing branching to 2nd week of September (10th), as the entire effort in this release has been around stability and fixing issues across the board. Thus,

[Gluster-devel] Test health report (week ending 19th Aug. 2018)

-validation.t https://build.gluster.org/job/regression-test-with-multiplex/831/console 18:20:49 1 test(s) generated core 18:20:49 ./tests/basic/ec/ec-5-2.t Shyam ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman

[Gluster-devel] Release 5: Release calendar and status updates

This mail is to solicit the following, Features/enhancements planned for Gluster 5 needs the following from contributors: - Open/Use relevant issue - Mark issue with the "Release 5" milestone [1] - Post to the devel lists issue details, requesting addition to track the same for the release

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

On 08/14/2018 12:51 AM, Pranith Kumar Karampuri wrote: > > > On Mon, Aug 13, 2018 at 10:55 PM Shyam Ranganathan <mailto:srang...@redhat.com>> wrote: > > On 08/13/2018 02:20 AM, Pranith Kumar Karampuri wrote: > >     - At the end of 2 weeks, reassess master

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

On 08/12/2018 08:42 PM, Shyam Ranganathan wrote: > 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

Re: [Gluster-devel] Master branch lock down: RCA for tests (UNSOLVED ./tests/basic/stats-dump.t)

On 08/13/2018 02:32 PM, Shyam Ranganathan wrote: > I will be adding a bug and a fix that tries this in a loop to avoid the > potential race that I see above as the cause. Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1615582 Potential fix: https://review.gluster.org/c/glusterfs/+/20726

Re: [Gluster-devel] Master branch lock down: RCA for tests (UNSOLVED ./tests/basic/stats-dump.t)

On 08/12/2018 08:42 PM, Shyam Ranganathan wrote: > 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

Re: [Gluster-devel] Master branch lock down: RCA for tests (./tests/bugs/core/bug-1432542-mpx-restart-crash.t)

On 08/12/2018 08:42 PM, Shyam Ranganathan wrote: > 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

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

On 08/12/2018 08:42 PM, Shyam Ranganathan wrote: > 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

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

On 08/12/2018 08:42 PM, Shyam Ranganathan wrote: > 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

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

r those components when a test in a > particular component starts to fail. Also I suggest we move this to the maintainers thread, to keep the noise levels across lists in check. Thanks, Shyam ___ Gluster-devel mailing list Gluster-devel@gluster.org

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

-operations-in-single-node.t TBD ./tests/bugs/replicate/bug-1386188-sbrain-fav-child.t TBD ./tests/bitrot/bug-1373520.tKotresh ./tests/bugs/distribute/bug-1117851.t Shyam/Nigel ./tests/bugs/glusterd/quorum-validation.t Atin ./tests/bugs/distribute/bug-1042725.t

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

here: https://review.gluster.org/c/glusterfs/+/20637/12#message-186adbee76d6999385022239cb2daba589f0a81f Shyam On 08/07/2018 07:37 PM, Shyam Ranganathan wrote: > Deserves a new beginning, threads on the other mail have gone deep enough. > > NOTE: (5) below needs your attention, rest is jus

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

://review.gluster.org/c/glusterfs/+/20637/12#message-1f8f94aaa88be276229f20eb25a650381bc37543 On 08/07/2018 07:37 PM, Shyam Ranganathan wrote: > 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 >

Re: [Gluster-devel] Master branch lock down status (Sat. Aug 10th)

-quorum.t (2 fail/retry) Sheet [1] has run details and also comment on patch [2] has run details. Atin/Shyam [1] Sheet: https://docs.google.com/spreadsheets/d/1IF9GhpKah4bto19RQLr0y_Kkw26E_-crKALHSaSjZMQ/edit#gid=552922579 [2] Comment on patch: https://review.gluster.org/c/glusterfs/+/20637

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

On 08/09/2018 10:58 PM, Raghavendra Gowdappa wrote: > > > On Fri, Aug 10, 2018 at 1:38 AM, Shyam Ranganathan <mailto:srang...@redhat.com>> wrote: > > On 08/08/2018 09:04 PM, Shyam Ranganathan wrote: > > Today's patch set 7 [1], included fixes

Re: [Gluster-devel] tests/bugs/core/multiplex-limit-issue-151.t timed out

On 08/11/2018 12:43 AM, Mohit Agrawal wrote: > File a bug https://bugzilla.redhat.com/show_bug.cgi?id=1615003, I am not > able to extract logs > specific to this test case from the log dump. This is because the test is calling cleanup twice in its exit bash traps. - First, the test itself sets a

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

On 08/10/2018 09:59 PM, Shyam Ranganathan wrote: > Today's patch set is 9 [1]. > > Total of 7 runs for line-coverage, mux regressions, centos7 regressions > are running (some are yet to complete). > > Test failure summary is as follows, Updating this section 1. ./tests/bugs/g

Re: [Gluster-devel] [Gluster-Maintainers] Master branch lock down status (Fri, August 9th)

d from run-tests.sh (when there are retries) then the logs will be archived. We do not call out a run as a failure in case there were retries, hence no logs. I will add this today to the WIP testing patchset. > > > On Sat, Aug 11, 2018 at 9:40 AM Ravishankar N <mailto:ravishan...@redhat

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

]. [2] will be updated as runs that are still ongoing complete. Shyam [1] Patch set: https://review.gluster.org/c/glusterfs/+/20637/9 [2] Sheet recording failures: https://docs.google.com/spreadsheets/d/1IF9GhpKah4bto19RQLr0y_Kkw26E_-crKALHSaSjZMQ/edit#gid=1535799585 [3] Comment on patch set 9

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

and passed, as the logs for the initial runs should be preserved from this run onward. Otherwise nothing else to report on the run status, if you are averse to spreadsheets look at this comment in gerrit [1]. Shyam [1] Patch set 8 run status: https://review.gluster.org/c/glusterfs/+/20637

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

On 08/08/2018 09:04 PM, Shyam Ranganathan wrote: > Today's patch set 7 [1], included fixes provided till last evening IST, > and its runs can be seen here [2] (yay! we can link to comments in > gerrit now). > > New failures: (added to the spreadsheet) > ./tests/bugs/quick

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

logs to look at with these runs Test ./tests/bugs/glusterd/quorum-validation.t dumped core again Atin/Amar, we may need to merge some of the patches that have proven to be holding up and fixing issues today, so that we do not leave everything to the last. Check and move them along or lmk. Shyam [1

Re: [Gluster-devel] [Gluster-Maintainers] Master branch lock down status

On 08/08/2018 09:43 AM, Shyam Ranganathan wrote: > On 08/08/2018 09:41 AM, Kotresh Hiremath Ravishankar wrote: >> For geo-rep test retrials. Could you take this instrumentation patch [1] >> and give a run? >> I am have tried thrice on the patch with brick mux enabled and wi

Re: [Gluster-devel] [Gluster-Maintainers] Master branch lock down status

On 08/08/2018 04:56 AM, Nigel Babu wrote: > Also, Shyam was saying that in case of retries, the old (failure) logs > get overwritten by the retries which are successful. Can we disable > re-trying the .ts when they fail just for this lock down period > alone so >

Re: [Gluster-devel] [Gluster-Maintainers] Master branch lock down status

On 08/08/2018 09:41 AM, Kotresh Hiremath Ravishankar wrote: > For geo-rep test retrials. Could you take this instrumentation patch [1] > and give a run? > I am have tried thrice on the patch with brick mux enabled and without > but couldn't hit > geo-rep failure. May be some race and it's not

Re: [Gluster-devel] Test: ./tests/bugs/ec/bug-1236065.t

On 08/07/2018 07:37 PM, Shyam Ranganathan wrote: > 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/ec/bug-1236065.t (Ashish) Ashish/Atin, the above test faile

Re: [Gluster-devel] Test: ./tests/bugs/distribute/bug-1042725.t

On 08/07/2018 07:37 PM, Shyam Ranganathan wrote: > 6) Tests that are addressed or are not occurring anymore are, > > ./tests/bugs/distribute/bug-1042725.t The above test fails, I think due to cleanup not completing in the previous test failure. The failed runs are: https://build.gluste

[Gluster-devel] Master branch lock down status

tests/bugs/distribute/bug-1122443.t ./tests/bugs/core/bug-1432542-mpx-restart-crash.t Shyam (and Atin) On 08/05/2018 06:24 PM, Shyam Ranganathan wrote: > Health on master as of the last nightly run [4] is still the same. > > Potential patches that rectify the situation (as in [1]) are bunc

Re: [Gluster-devel] Release 5: Master branch health report (Week of 30th July)

eping the backlog low (merging weekly) in these cases as per the dashboard [1]. Allowing for the above 2 reasons this patch was found, - Not on master - Not stabilizing or destabilizing the release branch and hence was merged. If maintainers disagree I can revert the same. Shyam [1] Release

Re: [Gluster-devel] Release 5: Master branch health report (Week of 30th July)

On 07/31/2018 07:16 AM, Shyam Ranganathan wrote: > 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 vari

Re: [Gluster-devel] Release 5: Nightly test failures tracking

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 As we have quite a few jobs failing and quite a few tests failing, to enable tracking this better I have created the

Re: [Gluster-devel] bug-1432542-mpx-restart-crash.t failures

On 08/01/2018 11:10 PM, Nigel Babu wrote: > Hi Shyam, > > Amar and I sat down to debug this failure[1] this morning. There was a > bit of fun looking at the logs. It looked like the test restarted > itself. The first log entry is at 16:20:03. This test has a timeout of >

Re: [Gluster-devel] Release 5: Master branch health report (Week of 30th July)

-EMLINK-handling.t, 405 tests/bugs/replicate/bug-1386188-sbrain-fav-child.t, 4048 tests/bugs/replicate/bug-1433571-undo-pending-only-on-up-bricks.t, 813 Thanks, Shyam On 07/30/2018 03:21 PM, Shyam Ranganathan wrote: > On 07/24/2018 03:12 PM, Sh

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: Master branch health report (Week of 30th July)

a little further the manner of cleanup_func and traps used in this test seem *interesting* and maybe needs a closer look to arrive at possible issues here. @Mohit, request you to take a look at the line coverage failures as well, as you handle the failures in this test. Thanks, Shyam

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: Master branch health report (Week of 30th July)

On 08/01/2018 12:13 AM, Sankarshan Mukhopadhyay wrote: >> 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

Re: [Gluster-devel] FreeBSD smoke test may fail for older changes, rebase needed

On 07/31/2018 02:12 AM, Niels de Vos wrote: > On Mon, Jul 30, 2018 at 02:44:57PM -0400, Shyam Ranganathan wrote: >> On 07/28/2018 12:45 PM, Niels de Vos wrote: >>> On Sat, Jul 28, 2018 at 03:37:46PM +0200, Niels de Vos wrote: >>>> This Friday argp-standalone got in

Re: [Gluster-devel] Release 5: Master branch health report (Week of 30th July)

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

Re: [Gluster-devel] Release 5: Master branch health report (Week of 30th July)

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.

Re: [Gluster-devel] FreeBSD smoke test may fail for older changes, rebase needed

venience that this caused, >> Niels > > It just occured to me that the argp-standalone installation also affects > the release-4.1 and release-3.12 branches. Jiffin, Shyam, do you want to > cherry-pick https://review.gluster.org/20581 to fix that, or do you > prefer an alternati

Re: [Gluster-devel] Release 5: Master branch health report (Week of 23rd July)

On 07/26/2018 12:53 AM, Nigel Babu wrote: > 3) bug-1432542-mpx-restart-crash.t times out consistently: > https://bugzilla.redhat.com/show_bug.cgi?id=1608568 > > @nigel is there a way to on-demand request lcov tests through gerrit? I > am thinking of pushing a patch that increases

Re: [Gluster-devel] Release 5: Master branch health report (Week of 23rd July)

On 07/25/2018 04:18 PM, Shyam Ranganathan wrote: > 2) glusterd crash in test sdfs-sanity.t: > https://bugzilla.redhat.com/show_bug.cgi?id=1608566 > > glusterd folks, request you to take a look to correct this. Persisted with this a little longer and the fix is pos

  1   2   3   4   5   6   >