Re: [Gluster-infra] [Gluster-devel] Gerrit and Jenkins likely unavailable most of Sunday

On 04/20/2015 08:35 AM, Vijay Bellur wrote: On 04/20/2015 04:25 AM, Justin Clift wrote: The good news: 1) Gerrit is kind of :/ updated. The very very latest versions (released friday) don't work properly for us. So, we're running on the slightly older v2.9.4 release of Gerrit.

Re: [Gluster-infra] [Gluster-devel] gerrit seems to be down?

On 06/25/2015 08:50 AM, Atin Mukherjee wrote: Infra guys, Could you check and get back? Its back to life now!! -- ~Atin ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Need an account in build.gluster.org

On 06/19/2015 08:02 PM, Justin Clift wrote: On 19 Jun 2015, at 10:01, Atin Mukherjee amukh...@redhat.com wrote: Folks, Can I get an account created for me in build.gluster.org? Yep. What kind of account do you need? ssh/jenkins/etc ? My primary requirement is to re-trigger regression

Re: [Gluster-infra] [Gluster-devel] Reduce regression runs wait time - New gerrit/review work flow

On 06/15/2015 04:19 PM, Kaushal M wrote: Hi all, The recent rush of reviews being sent due to the release of 3.7 was a cause of frustration for many of us because of the regression tests (gerrit troubles themselves are another thing). W.R.T regression 3 main sources of frustration were,

Re: [Gluster-infra] [Gluster-devel] NetBSD regressions not being triggered for patches

On 06/11/2015 08:04 PM, Emmanuel Dreyfus wrote: On Thu, Jun 11, 2015 at 04:04:44PM +0200, Niels de Vos wrote: Michael installed and configured dnsmasq on build.gluster.org yesterday. If that does not help today, we need other ideas... Just to confirm the problem: [manu@build ~]$ time

Re: [Gluster-infra] [Gluster-devel] Reduce regression runs wait time - New gerrit/review work flow

On 15 Jun 2015 19:23, Kaushal M kshlms...@gmail.com wrote: I like this idea. One tweak I'd make is to introduce the idea of Verified+1 for smoke and Verified+2 for regressions. Why? Because it seems like a lot of people won't even review a patch until they can see that it has been

Re: [Gluster-infra] [Gluster-devel] NetBSD regression failures

need to move tests/geo-rep/georep-basic-dr-tarssh.t as well to the bad test? Regards, Avra On 08/17/2015 02:12 PM, Atin Mukherjee wrote: tests/basic/mount-nfs-auth.t has been already been added to bad test by http://review.gluster.org/11933 ~Atin On 08/17/2015 02:09 PM, Avra Sengupta

Re: [Gluster-infra] [Gluster-devel] NetBSD regression failures

tests/basic/mount-nfs-auth.t has been already been added to bad test by http://review.gluster.org/11933 ~Atin On 08/17/2015 02:09 PM, Avra Sengupta wrote: Will send a patch moving ./tests/basic/mount-nfs-auth.t and ./tests/geo-rep/georep-basic-dr-rsync.t to bad test. Regards, Avra On

[Gluster-infra] gerrit seems to be down, please cross check

___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Gluster testing matrix

need to sanitize it w.r.t IPv6 and check it really works and that requires infra support. [1] http://review.gluster.org/#/c/11988/ Thanks, Atin On 11/25/2015 07:43 PM, Sankarshan Mukhopadhyay wrote: > On Wed, Nov 25, 2015 at 7:37 PM, Atin Mukherjee > <atin.mukherje...@gmail.com> wr

Re: [Gluster-infra] freebsd smoke failure

On 01/12/2016 01:37 PM, Niels de Vos wrote: > On Tue, Jan 12, 2016 at 11:19:30AM +0530, Atin Mukherjee wrote: >> I've been observing freebsd smoke failure for all the patches for last >> few days with the following error: >> >> mkdir: /usr/local/lib/python2.7/site-p

[Gluster-infra] freebsd smoke failure

I've been observing freebsd smoke failure for all the patches for last few days with the following error: mkdir: /usr/local/lib/python2.7/site-packages/gluster: Permission denied mkdir: /usr/local/lib/python2.7/site-packages/gluster: Permission denied Can any one from infra team can help here?

Re: [Gluster-infra] [Gluster-devel] freebsd smoke failure

On 01/12/2016 04:10 PM, Rajesh Joseph wrote: > > > - Original Message - >> From: "Niels de Vos" <nde...@redhat.com> >> To: "Rajesh Joseph" <rjos...@redhat.com> >> Cc: "Atin Mukherjee" <amukh...@redhat.com>, &

[Gluster-infra] All NetBSD slaves look offline

___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] All NetBSD slaves look offline

figuration file .git/config.lock On 06/09/2016 09:31 PM, Atin Mukherjee wrote: ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Gerrit (review.gluster.org/git.gluster.org) downtime in 15 mins

On 06/01/2016 08:40 AM, Nigel Babu wrote: > Hello folks, > > The upgrade is now complete! Please let me know if you notice anything > wrong. It does appear slow to me compared to previous version. > > On Wed, Jun 1, 2016 at 7:45 AM, Nigel Babu >

Re: [Gluster-infra] Different version of run-tests.sh in jenkin slaves?

On 01/28/2016 12:00 PM, Raghavendra Talur wrote: > Ok, RCA: > > In NetBSD cores are being generated in /d/backends/*/*.core > run-tests.sh looks only for "/core*" when looking for cores. > > So, at the end of test run when regression.sh looks for core everywhere, > it finds one and errors out.

[Gluster-infra] Different version of run-tests.sh in jenkin slaves?

Are we running a different version of run-tests.sh in jenkin slaves. The reason of suspection is beacuse in last couple of runs [1] & [2] in NetBSD I am seeing no failures apart from bad tests but the regression voted failure and I can not make out any valid reason out of it. [1]

[Gluster-infra] r.g.o not responding or too slow

As $subj ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] r.g.o not responding or too slow

On 02/26/2016 06:10 PM, Niels de Vos wrote: > On Fri, Feb 26, 2016 at 05:40:00PM +0530, Atin Mukherjee wrote: >> As $subj > > Please check the infra list archive before sending reports like this :) I'd say that some other guy who sent it should have copied gluster-devel

Re: [Gluster-infra] [Gluster-devel] Is anyone paying attention to centos regressions on jenkins?

I think Raghavendra Talur is already aware of the problem and he sent a mail on devel to disable regression trigger on code review +2 or verified +1. -Atin Sent from one plus one On 04-Mar-2016 6:49 pm, "Kaleb Keithley" wrote: > There are a handful of centos regressions

Re: [Gluster-infra] [Gluster-devel] Smoke results voting

we get all the positive votes, web interface doesn't provide a submit button. > > ~kaushal > > > On Mon, Apr 4, 2016 at 10:39 PM, Prasanna Kalever <pkale...@redhat.com> wrote: >> On Mon, Apr 4, 2016 at 9:58 PM, Atin Mukherjee >> <atin.mukherje...@gmail.com>

[Gluster-infra] Smoke results voting

Did anyone notice that for few of the patches smoke results are not voted back? http://review.gluster.org/#/c/13869 is one of them. -Atin Sent from one plus one ___ Gluster-infra mailing list Gluster-infra@gluster.org

Re: [Gluster-infra] [Gluster-Maintainers] Request to provide PASS flags to a patch in gerrit

On Wed, Aug 31, 2016 at 4:23 PM, Raghavendra Talur wrote: > Hi All, > > We have a test [1] which is causing hangs in NetBSD. We have not been able > to debug the issue yet. > It could be because the bash script does not comply with posix guidelines > or that there is a bug in

[Gluster-infra] centos-5 build failures on mainline

As of now we don't check for build sanity on RHEL5/centos-5 distros. I believe Gluster still has legacy support for these distros. Here we could either add a glusterfs-devrpms script for el5 for every patch submission or at worst have a

[Gluster-infra] r.g.o seems to be down?

-- ~ Atin (atinm) ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] r.g.o seems to be down?

BZ filed :https://bugzilla.redhat.com/show_bug.cgi?id=1389282 2016-10-27 16:46 GMT+05:30 Atin Mukherjee <amukh...@redhat.com>: > > > -- > > ~ Atin (atinm) > -- ~ Atin (atinm) ___ Gluster-infra mailing list Gluste

[Gluster-infra] Nightly regression job with enabling brick multiplexing

As we don't run our .t files with brick mux being enabled for every patches can we ensure that there is a nightly regression trigger with brick multiplexing feature being enabled. The reason for this ask is very simple, we have no control on the regression for this feature. I've already seen a

Re: [Gluster-infra] [Gluster-users] lists.gluster.org issues this weekend

On Fri, 22 Sep 2017 at 18:54, Ravishankar N wrote: > Hello, > Are our servers still facing the overload issue? My replies to > gluster-users ML are not getting delivered to the list. > Same here. Even this is true for gluster-devel as well. > Regards, > Ravi > > > On

[Gluster-infra] r.g.o - invalid certificate

r.g.o is inaccessible to me with following error: review.gluster.org uses an invalid security certificate. The certificate expired on October 8, 2017, 5:17 PM. The current time is October 8, 2017, 7:38 PM. Error code: SEC_ERROR_EXPIRED_CERTIFICATE Bug filed at

Re: [Gluster-infra] [Gluster-devel] Infra-related Regression Failures and What We're Doing

On Mon, Jan 22, 2018 at 5:13 PM, Nigel Babu wrote: > Update: All the nodes that had problems with geo-rep are now fixed. > Waiting on the patch to be merged before we switch over to Centos 7. If > things go well, we'll replace nodes one by one as soon as we have one green > on

Re: [Gluster-infra] [Gluster-devel] Recent regression failures

On Thu, Jan 11, 2018 at 10:15 AM, Nigel Babu wrote: > Hello folks, > > We may have been a little too quick to blame Meltdown on the Jenkins > failures yesterday. In any case, we've open a ticket with our provider and > they're looking into the failures. I've looked at the last

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

I saw the same behaviour for https://build.gluster.org/job/regression-on-demand-full-run/47/consoleFull as well. In both the cases the common pattern is if a test was retried but overall the job succeeded. Is this a bug which got introduced recently? At the moment, this is blocking us to debug any

Re: [Gluster-infra] [Gluster-devel] Master branch is closed

Nigel, Now that mater branch is reopened, can you please revoke the commit access restrictions? On Mon, 6 Aug 2018 at 09:12, Nigel Babu wrote: > Hello folks, > > Master branch is now closed. Only a few people have commit access now and > it's to be exclusively used to merge fixes to make

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

https://build.gluster.org/job/regression-test-with-multiplex/794/display/redirect has the same test failing. Is the reason of the failure different given this is on jenkins? On Sat, 7 Jul 2018 at 19:12, Deepshikha Khandelwal wrote: > Hi folks, > > The issue[1] has been resolved. Now the

Re: [Gluster-infra] [Gluster-devel] Announcing Softserve- serve yourself a VM

On Wed, Feb 28, 2018 at 6:56 PM, Deepshikha Khandelwal wrote: > Hi, > > We have launched the alpha version of SOFTSERVE[1], which allows Gluster > Github organization members to provision virtual machines for a specified > duration of time. These machines will be deleted

Re: [Gluster-infra] [Gluster-devel] is_nfs_export_available from nfs.rc failing too often?

t; can happen or not. > That's precisely what the question is. Why suddenly we're seeing this happening too frequently. Today I saw atleast 4 to 5 such failures already. Deepshika - Can you please help in inspecting this? > Regards, > Jiffin > > > - Original Message -

[Gluster-infra] rebal-all-nodes-migrate.t always fails now

Based on what I have seen that any multi node test case will fail and the above one is picked first from that group and If I am correct none of the code fixes will go through the regression until this is fixed. I suspect it to be an infra issue again. If we look at

Re: [Gluster-infra] [Gluster-devel] rebal-all-nodes-migrate.t always fails now

ael Scherer a écrit : > > Le jeudi 04 avril 2019 à 13:53 +0200, Michael Scherer a écrit : > > > Le jeudi 04 avril 2019 à 16:13 +0530, Atin Mukherjee a écrit : > > > > Based on what I have seen that any multi node test case will fail > > > > and > >

[Gluster-infra] https://build.gluster.org/job/centos7-regression/6404/consoleFull - Problem accessing //job/centos7-regression/6404/consoleFull. Reason: Not found

https://bugzilla.redhat.com/show_bug.cgi?id=1719174 The patch which failed the regression is https://review.gluster.org/22851 . ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] New workflow proposal for glusterfs repo

On Wed, 12 Jun 2019 at 18:04, Amar Tumballi Suryanarayan < atumb...@redhat.com> wrote: > > Few bullet points: > > * Let smoke job sequentially for below, and if successful, in parallel for > others. > - Sequential: > -- clang-format check > -- compare-bugzilla-version-git-branch > --

Re: [Gluster-infra] [Gluster-devel] is_nfs_export_available from nfs.rc failing too often?

On Wed, May 8, 2019 at 7:38 PM Atin Mukherjee wrote: > builder204 needs to be fixed, too many failures, mostly none of the > patches are passing regression. > And with that builder201 joins the pool, https://build.gluster.org/job/centos7-regression/5943/consoleFull > On Wed, May

Re: [Gluster-infra] [Gluster-devel] is_nfs_export_available from nfs.rc failing too often?

ion tonight, so if I find nothing, >>> until I leave, I guess Deepshika will have to look. >>> >>> > On Wed, Apr 24, 2019 at 5:30 PM Yaniv Kaul wrote: >>> > >>> > > >>> > > >>> > > On Tue, Apr

Re: [Gluster-infra] [Gluster-devel] Weekly Untriaged Bugs

While I understand this report captured bugs filed since last 1 week and do not have ‘Triaged’ keyword, does it make better sense to exclude bugs which aren’t in NEW state? I believe the intention of this report is to check what all bugs haven’t been looked at by maintainers/developers yet. BZs

Re: [Gluster-infra] [Gluster-devel] is_nfs_export_available from nfs.rc failing too often?

builder204 needs to be fixed, too many failures, mostly none of the patches are passing regression. On Wed, May 8, 2019 at 9:53 AM Atin Mukherjee wrote: > > > On Wed, May 8, 2019 at 7:16 AM Sanju Rakonde wrote: > >> Deepshikha, >> >> I see the failure here[1] w

Re: [Gluster-infra] [Gluster-devel] is_nfs_export_available from nfs.rc failing too often?

Is this back again? The recent patches are failing regression :-\ . On Wed, 3 Apr 2019 at 19:26, Michael Scherer wrote: > Le mercredi 03 avril 2019 à 16:30 +0530, Atin Mukherjee a écrit : > > On Wed, Apr 3, 2019 at 11:56 AM Jiffin Thottan > > wrot

[Gluster-infra] Fwd: [Gluster-Maintainers] Build failed in Jenkins: regression-test-burn-in #4710

Since last few days I was trying to understand the nightly failures we were seeing even after addressing the port already in use issue. So here's the analysis: >From console output of https://build.gluster.org/job/regression-test-burn-in/4710/consoleFull *19:51:56* Started by upstream project

[Gluster-infra] rpm rawhide is failing since last few days!

One of them is https://build.gluster.org/job/rpm-rawhide/3084/ -- - Atin (atinm) ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra