I've said on this thread before, none of this is easy to do. It needs us to
fork Gerrit to make our own changes. I would argue that depending on the
data from the commit message is folly.
On Fri, Oct 14, 2016 at 12:23 PM, Niels de Vos wrote:
> On Thu, Oct 13, 2016 at 11:01:43PM +0530, Pranith Ku
On Fri, Oct 14, 2016 at 10:44:02PM +0530, Pranith Kumar Karampuri wrote:
> How do we get the following tags in the commit message?
>
> > Smoke: Gluster Build System
> > NetBSD-regression: NetBSD Build System
> > CentOS-regression: Gluster Build System
We use Cherry-Pick merge strate
Hi Prashanth,
The last we talked about this failure, you mentioned you couldn't reproduce the
failure on your VM. Were you finally able to reproduce the failure?
If the tests are passing on the VM without being able to reproduce the failure
on the same VM, that doesn't give us any useful informat
eway. Once the network team is freed up, they'll fix it
permanently.
On Wed, Nov 02, 2016 at 05:02:07AM -0400, Prashanth Pai wrote:
>
> - Original Message -----
> > From: "Nigel Babu"
> > To: "Prashanth Pai"
> > Cc: "Niels de Vos" , gl
Hello,
I've been working on getting the Glusto tests to work and it appears that we're
stuck in a situation which Shewtha and Jonathan haven't been able to fully
arrive at a solution. Here are the two problems:
1. Originally, we ran into issues with NFS with an error that looked like this:
On Mon, Nov 07, 2016 at 12:18:41PM +0530, shwetha wrote:
> On 11/07/2016 11:55 AM, Nigel Babu wrote:
> > Hello,
k >
> > I've been working on getting the Glusto tests to work and it appears that
> > we're
> > stuck in a situation which Shewtha and Jonathan
On Mon, Nov 07, 2016 at 12:12:21PM +0530, Kaushal M wrote:
> On Mon, Nov 7, 2016 at 11:55 AM, Nigel Babu wrote:
> > Hello,
> >
> > I've been working on getting the Glusto tests to work and it appears that
> > we're
> > stuck in a situation which Shew
Hello folks,
Shwetha and I have gotten far enough to get the Glusto tests to pass for Fuse
mounts, NFS, and Samba. Well the fix for Samba isn't in yet, but we know what
we need to do. Thanks to help from Kaushal, Shyam, Nithya, Jiffin, and
Raghavendra Talur.
Shwetha is also working on documentati
Short answer: Yes, but not right away.
I discussed this with Kaleb at the summit. I'd like to own packaging
entirely (and automate it), but once I have more time to do so. My primary
concern right now is lack of time.
On Thu, Nov 10, 2016 at 9:33 PM, Vijay Bellur wrote:
> On Wed, Oct 19, 2016 a
On Mon, Nov 14, 2016 at 11:03:51AM +0530, Nithya Balachandran wrote:
> Hi,
>
> Our smoke tests have been failing quite frequently of late. While
> re-triggering smoke several times in order to get a +1 works eventually,
> this does not really help anything IMO.
>
> I believe Jeff has already propos
It looks like. Nithya asked me to get some numbers.
The first failure was on Aug 2nd [1]. Here are the monthly numbers since
August:
Aug: 31
Sep: 59
Oct: 107
Nov: 43 (in 14 days)
[1]: https://build.gluster.org/job/smoke/29605/consoleText
On Sun, Nov 13, 2016 at 10:04:58PM -0800, Joe Julian wrot
Hello,
I've been working on a dashboard for test failure statistics. This is built on
the work done by Poornima on `extras/failed-tests.py`. The site can be viewed
at http://fstat.gluster.org. Please file any bugs against the Github project
here: http://github.com/gluster/fstat/issues
--
nigelb
_
Hello,
I'm taking Gerrit offline now. I'll post an update when it's online and ready
again.
--
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
Migration completed successfully!
On Sat, Nov 19, 2016 at 12:05:18PM +0530, Nigel Babu wrote:
> Hello,
>
> I'm taking Gerrit offline now. I'll post an update when it's online and ready
> again.
>
> --
> nigelb
--
nigelb
__
Hello folks,
I've pushed a few updates to fstat[1]:
Here are the visible updates:
* Add back the code for catching duplicate failure instance entry.
* Show review and patchset (linked to review).
* Show actual dates for the duration.
* Duration will now count from 00:00 of the date
* Show failure
Hello folks,
We've made quite a lot of progress in the last few weeks with Glusto-based
tests. It's time for us to provide an update. Here's what has happened:
* Thanks to Poornima and Raghavendra Talur, we figured the issues we had with
CIFS. I'll be fixing Gluster documentation so that it has
Hello folks,
This is a request for feedback for this plan to build a pipeline that will go
from a commit to builds that are tested and signed. While the
nightly.gluster.org site will be up by the time 3.10 is released, we will not
yet be automating releases with this pipeline by then.
# Why
* Cre
On Thu, Dec 15, 2016 at 01:13:05PM +0100, Niels de Vos wrote:
> On Thu, Dec 15, 2016 at 05:20:26PM +0530, Nigel Babu wrote:
> > Hello folks,
> >
> > This is a request for feedback for this plan to build a pipeline that will
> > go
> > from a commit to builds that
On Thu, Dec 15, 2016 at 07:50:53AM -0500, Kaleb S. KEITHLEY wrote:
> On 12/15/2016 07:13 AM, Niels de Vos wrote:
> > On Thu, Dec 15, 2016 at 05:20:26PM +0530, Nigel Babu wrote:
> > > Hello folks,
> > >
> > > This is a request for feedback for this plan to
Thank you Kaleb. Shall we start somwhere in terms of automation?
The cppcheck results look the shortest[1]. If we can commit to fixing all of
them in the next 1 month, I can kick off a non-voting smoke job. We'll make it
vote after 1 month. I guss the cli and experimental xlator (and a few more
xl
On Mon, Dec 19, 2016 at 12:56:27PM -0500, Kaleb S. KEITHLEY wrote:
> On 12/19/2016 12:49 PM, Nigel Babu wrote:
> > Thank you Kaleb. Shall we start somwhere in terms of automation?
> >
> > The cppcheck results look the shortest[1]. If we can commit to fixing all of
> >
On Mon, Dec 19, 2016 at 01:06:35PM -0500, Jeff Darcy wrote:
> Before we get to automation, shouldn't we have a discussion about what
> "defects" we should filter out? For example, we already have a problem
> with compilers spitting out warnings about unused variables in generated
> code, and then
Hello folks,
There's a few conversations I've been having about reducing regressions
workloads. Is it useful to have a mechanism to suggest in a commit message to
skip regressions on a job? For instance, you'd say [ci-skip] and it would skip
your commit.
My assumption is that we may have a genuin
Hello folks,
Here are the top 5 failures in the last 4 weeks:
Test: basic/quota-rename.t - 23 failures
URL: http://fstat.gluster.org/weeks/4/failure/82
Note: Almost always on NetBSD. Fails with socket not connected
Test: basic/gfapi/bug1291259.t - 18
URL: http://fstat.gluster.org/weeks/4/failure
Hello,
I've had to restart Jenkins today because of a very long running job that
couldn't be killed through any other means. If you had any jobs in progress or
pending, you'll have to retrigger them. Apologies for the inconvinience. I will
make sure that we have better ways of dealing with this in
Hello folks,
We're announcing a downtime window for Gerrit (review.gluster.org) on Saturday
21st Jan 2017 for 8 hours. This outage will be used to move Gerrit to CentOS
7 from the existing infrastructure.
# Date and Time
Saturday, 21st Jan 2017
1000 - 1800 UTC
1100 - 1900 CET
1530 - 2330 IST
# I
Hello folks,
Last week's community meeting had a discussion about Developer Workflow Issues.
If you missed the meeting, it's worth reading up on the logs[1]. Raghavendra
Talur and I had a followup chat on Friday about tests. I've created a
proposal[2] with what we agreed is the best way forward.
Hi folks,
Thanks to some fantastic work by Ashish, Anoop, and Xavi, we now have Glusto
tests passing upstream[1]. We were running into a crash that was triggered by
an selinux failure. As far as infrastructure goes, we're set to run more tests.
Shwetha and others have been working on writing test
Quick reminder about this outage window. It's this weekend.
On Mon, Jan 09, 2017 at 04:28:02PM +0530, Nigel Babu wrote:
> Hello folks,
>
> We're announcing a downtime window for Gerrit (review.gluster.org) on Saturday
> 21st Jan 2017 for 8 hours. This outage will be used to
Hello folks,
The cage is seeing a network issue at the moment with packet loss for all
servers hosted in there. We're likely to see a noticable problem with Gerrit
and Jenkins today.
Additionally, on Tuesday, 24th Jan at 24 Jan 2017 from 13:00 to 13:15 (UTC)
there's a scheduled failover testing.
Hello folks,
We're beginning the Gerrit outage now. Gerrit will not be fully operational
until the end of downtime. I'll send out an announce when it is ready. We will
be disabling pushes until everything is set.
--
nigelb
signature.asc
Description: PGP signature
___
Sat, Jan 21, 2017 at 03:48:59PM +0530, Nigel Babu wrote:
> Hello folks,
>
> We're beginning the Gerrit outage now. Gerrit will not be fully operational
> until the end of downtime. I'll send out an announce when it is ready. We will
> be disabling pushes until ev
Hello,
Some of you may have noticed that we've been particularly plagued with RPM
build failures for the past couple of days. The failure looks like a Java error
from Jenkins[1]. I first noticed the error on Tuesday, 31st January. I narrowed
down the issue with a problem with permissions. Jenkins
Hello folks,
Here are the top failures for January:
All failurs in last month's list have been fixed/disabled except for one. I've
filed bugs for the top failures as we agreed last month[1]. I've also modified
fstat to show 12 weeks of results.
I've been adding test-failure to the whiteboard of
Hello,
Atin pointed out that the self-heald.t failures have this error in the console:
ERROR: failed to create logfile "/dev/stderr" (Permission denied)
Anyone know
* Why we're writing to /dev/stderr?
* What's going wrong here?
I can't find any permission difference, but I do notice that th
Hi folks,
Jeff pointed out that the netbsd6-smoke jobs are failing with random errors as
though multiple jobs are running simultaneously[1]. I'm disabling netbsd6-smoke
until I can figure out what's going wrong.
I'll renable it once I can figure out what's wrong and fix it.
[1]: https://bugzilla
Hello,
I've made some changes to the Jenkins jobs over yesterday and today.
* Centos regression jobs now timeout in 360 mins rather than 300 mins. The
release 3.8 jobs were running afoul of the limits prompting this change.
* Aborting Centos regression and NetBSD regression will trigger a reboo
Hello folks,
Michael and I have brought up the community cage outage at the last meeting.
The details are now confirmed. There will be a major outage window for the
community cage on March 14-16 2017. The migration will begin around 1000 EST /
1600 CET / 2030 IST. During this time, servers will mo
Hello folks,
Do we have problems moving to Centos 7 for regressions and smoke testing?
I plan to do this in two parts.
# Step 1
* Move builds to Centos 7.
* Have a nightly Centos 7 regression run.
# Step 2
* Switch regressions to Centos 7.
* Have a nightly Centos 6 regression run.
I'd like to g
Hello folks,
I know we've had Jenkins voting issues for a while and I'd like to offer tips
to avoid the worst of it.
1. Do not set a Verified +1 flag until smoke tests have reported back. If you
do, all jobs will vote together. This will cause smoke tests or regressions
to vote incorrectly.
Thank you Michael for taking care of this restart and fixing up the new
problems that came up :)
On Sat, Feb 25, 2017 at 8:54 PM, Michael Scherer
wrote:
> Le samedi 25 février 2017 à 16:21 +0100, Michael Scherer a écrit :
> > Le samedi 25 février 2017 à 15:45 +0100, Michael Scherer a écrit :
> >
Hello folks,
At some point in the distant future, we want to be able to say definitively
that we have a good Gluster build. This conviction needs to be backed by tests
that we run on our builds to confirm that it is good. This conversation is
meant to tease out a definition of good build. This def
Hello,
A reminder that this outage is next Tuesday, i.e. 14th March. Please make sure
anything urgent is done before then.
On Sun, Feb 19, 2017 at 09:10:42PM +0530, Nigel Babu wrote:
> Hello folks,
>
> Michael and I have brought up the community cage outage at the last meeting.
>
We don't currently save the logs for aborted jos, but I can set that up for
you. What files do you want logged?
On Fri, Mar 10, 2017 at 1:15 PM, Xavier Hernandez
wrote:
> Hi,
>
> I've posted a patch [1] to fix a memory leak in locks xlator. The fix
> seems quite straightforward, however I've see
Hello folks,
We had this discussion a while ago about having dashboards inside Gerrit.
I tried to get it working and couldn't back then. I've finally got it working.
It seems to be very useful for release maintainers after a release has been
branched. I have two dashboards for 3.10 and 3.8, both o
Hello folks,
Our big infra outage starts today. At around 1630 IST / 1200 CET / 1100 UTC
/ 0700 EDT, I will prepare Jenkins for shutdown. From this point onwards, you
cannot schedule new jobs. I'll let jobs that can finish before the shutdown run
it's course and stop the remaining at the time of s
All servers are now shutdown in preparation for the move. We will have services
restored (hopefully) by the end of EDT working day today. Michael or I will
post updates when we have one.
--
nigelb
On Tue, Mar 14, 2017 at 10:24:38AM +0530, Nigel Babu wrote:
> Hello folks,
>
> Our big inf
Hello folks,
I put this up for discussion at the last community meeting, but I was unable to
attend the meeting. We have a lot of reviews that are quite old[1]. They have,
at some point, become unmergable or the person who proposed them lost interest.
This is on us. We've let reviews slip through
Hello folks,
You may have noticed that the RPM jobs failed quite often since the migration.
This should finally be fixed now. Here's a quick post-mortem of what happened.
After the restart, our Jenkins server has accidentally had a fr_FR locale. This
means some of the logs are now in French. In t
This is all sorted now. I've restarted Jenkins so it's English rather than
French :)
--
nigelb
signature.asc
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel
Hello folks,
This is email is only relevant if your project runs builds on CentOS CI and
clones from the Gluster Gerrit instance.
There's a networking issue that's re-emerged after the migration. I've brought
it up with the Networking folks and the CentOS folks. I'm hoping it will be
fixed later
Hello folks,
I've upgraded Gerrit to 2.12.7. We run 2.12.2 in production. The changes are
mostly bug fixes. The full release notes are in the release notes[1]. Please
test out staging[2] and let me know if you notice anything wrong.
[1]: https://www.gerritcodereview.com/releases/2.12.md#2.12.3
[
Hello folks,
I've been slowly working on moving jobs off our master machine on
build.gluster.org. This will let us upgrade to a new Jenkins server without too
much pain. In this regard, I've moved compare-bug-version-and-git-branch off
master onto bugziller.rht.gluster.org.
This machine has bugzi
This should be fixed now. See
https://bugzilla.redhat.com/show_bug.cgi?id=1442672
On Mon, Apr 17, 2017 at 5:37 AM, Zhengping Zhou
wrote:
> Did anyone encount this problem when excute "git pull", this output
> is :
>
>
> [zzp@42 gluster]$ git pull
> ssh_exchange_identification: Connection cl
This should be fixed now: https://bugzilla.redhat.com/
show_bug.cgi?id=1442672
Vijay, can you link me to your failed Jenkins job? Jenkins should have been
able to clone since it uses the git protocol and not SSH.
On Sun, Apr 16, 2017 at 9:25 PM, Vijay Bellur wrote:
>
>
> On Sun, Apr 16, 2017 at
Hello folks,
We're announcing a Jenkins outage window on 27th Apr 2017 during the following
times:
0300 - 0700 EDT
0700 - 1100 UTC
0800 - 1200 CEST
1230 - 1630 IST
This is purposely in the middle of the working day so we can identify any
issues that might come up post-upgrade and fix them immedi
Hello folks,
As I was testing the Jenkins upgrade, I realized we store quite a lot of old
builds on Jenkins that doesn't seem to be useful. I'm going to start cleaning
them slowly in anticipation of moving Jenkins over to a CentOS 7 server in the
not-so-distant future.
* Old and disabled jobs wil
Hello
A reminder that this is today.
On Tue, Apr 18, 2017 at 04:06:25PM +0530, Nigel Babu wrote:
> Hello folks,
>
> We're announcing a Jenkins outage window on 27th Apr 2017 during the following
> times:
>
> 0300 - 0700 EDT
> 0700 - 1100 UTC
> 0800 - 1200 CEST
Hello folks,
The first part of the Jenkins upgrade has now begun. The Jenkins server is now
on quiet mode. No new builds will be scheduled. I will be shuting down Jenkins
in the next 1h to begin the upgrade.
--
nigelb
signature.asc
Description: PGP signature
Hello,
The upgrade is now complete and we should be good to go. Please let me know if
there are any problems.
--
nigelb
On Thu, Apr 27, 2017 at 11:34:05AM +0530, Nigel Babu wrote:
> Hello folks,
>
> The first part of the Jenkins upgrade has now begun. The Jenkins server is now
> o
Hello folks,
In testing the Jenkins upgrade, I learned that we allow Jenkins read access to
/etc/shadow to allow Unix authentication. In addition to this, our
authentication was open to brute force attacks and hard to keep the user list
updated. To ease these pains, we've switched Jenkins authenti
We use the "cherry-pick" submit type for glusterfs on Gerrit[1]. In the past,
Poornima has pointed this out as well. I believe there was no interest in
changing the submit type[2] because the other submit types do not add metadata
to
the commit itself.
[1]:
https://review.gluster.org/Documentati
Hello folks
I'd like to introduce Smit Thakkar. He's going to work on fstat over the next
few months. I've just deployed his newest feature. This will let you select
date ranges for fstat rather than looking at results back from point in time.
This will let us compare failures in May vs failures i
Hello folks,
I've made a few changes to period regression runs as requested by quite a few
people.
1. The regression-test-burn-in[1] job now runs every 8 hours. At , 0800,
and 1600. This job will take master and run regressions and report failures
to maintain...@gluster.org
2. There is
FYI: There are now emails to gluster-maintainers@ about this. If you'd like
to help diagnose/fix the problems, please see the job and logs here:
https://build.gluster.org/job/regression-test-with-multiplex/
--
nigelb
___
Gluster-devel mailing list
Glust
Hello folks,
We've switched Jenkins to using Github authentication. This means unix accounts
on the Jenkins server are no longer required for access. We will be removing
all the old users to reduce our attack vector. Please back up any scripts/files
you'll be needing from your home directory on th
Hello folks,
We'll be having a short downtime for build.gluster.org on 20th June 2017
(tomorrow).
Date: 20th June 2017
Time: 0230 UTC (2230 EDT / 0430 CEST / 0800 IST)
Duration: 1h
Jenkins will be in a quiet time from 1h before the outage where no new builds
will be allowed to start.
This downt
Other than Gerrit, the rest can be rebooted ruthlessly.
On 19-Jun-2017 23:16, "Michael Scherer" wrote:
> Le lundi 19 juin 2017 à 17:55 +0200, Michael Scherer a écrit :
> > Le lundi 19 juin 2017 à 17:12 +0530, Nigel Babu a écrit :
> > > Hello folks,
> > >
&
Hello folks,
Amar has proposed[1] these changes in the past and I'd like to announce us going
live with them as we've not received any strong feedback against it.
## Centos Regression
* On master, we only run tests/basic as pre-merge testing.
* On release branches, we will run the entire suite of
On Thu, Apr 20, 2017 at 10:57:53AM +0530, Nigel Babu wrote:
> Hello folks,
>
> As I was testing the Jenkins upgrade, I realized we store quite a lot of old
> builds on Jenkins that doesn't seem to be useful. I'm going to start cleaning
> them slowly in anticipation of
On Wed, Jun 21, 2017 at 06:05:32PM +0530, Atin Mukherjee wrote:
> On Tue, Jun 20, 2017 at 9:17 AM, Nigel Babu wrote:
>
> > Hello folks,
> >
> > Amar has proposed[1] these changes in the past and I'd like to announce us
> > going
> > live with them as we&#x
Hello folks,
We'll have a 1-hour long Gerrit outage on Monday for a Gerrit upgrade. We'll be
moving from 2.12.2 to 2.12.7. It's a minor version upgrade and I don't expect
any troubles. You can test the new version on gerrit-stage.rht.gluster.org
Date: 21 June 2017
Time: 0230 UTC (2230 EDT / 0430
On Wed, Jun 21, 2017 at 10:35:05AM +0530, Amar Tumballi wrote:
> Today, any changes to glusterfs code base (other than 'doc/') triggers the
> regression runs when +1 Verified is voted. But we noticed that patches
> which are changes in 'extras/' or just updating README file, need not run
> regressi
Hello folks,
We'll also have a short Jenkins outage on 26 June 2017, for a Jenkins plugin
installation and upgrade.
Date: 26th June 2017
Time: 0230 UTC (2230 EDT / 0430 CEST / 0800 IST)
Duration: 1h
Jenkins will be in a quiet time from 1h before the outage where no new builds
will be allowed to
Hello folks,
We had downtimes today for both Gerrit and Jenkins related upgrades. The Gerrit
upgrade went very smoothly. We will need to figure out a date in the short-term
where we'll upgrade to the next major release.
The Jenkins upgrade caused some issues causing some downtime. The latest
vers
Hi Pranith and Xavi,
We seem to be running into a problem with glusto tests when we try to run
them against dispersed volumes over a CIFS mount[1]. You can find the logs
attached to the job [2].
I've triggered a fresh job[3] to confirm that it only fails in these
particular conditions and certain
On Thu, Jun 29, 2017 at 6:49 PM, Anoop C S wrote:
> Is this a new test case? If not was it running successfully before?
>
This test case is not new, but we weren't hitting this for quite a while
because we were failing because of a GNFS packaging issue. Now that I've
recently fixed it up, we're
Hello,
I've spoken to Atin, Ravi, and Amar and we agreed on a solution that I've just
completed.
1. I've landed a patch directly on master bypassing review. This patch will
disabling the test that is currently failing. Now patches that are waiting
to land in master can be landed safely whil
>
> Maybe we need to upgrade the version of gdb on these machines, because it
> didn't seem able to get the backtrace but the version I'm using (7.12.50)
> did just fine. The first few frames of thread 1 above the signal handler
> look like this.
>
I'd like to move our regression infra to Centos
Hello,
## Highlights
* If you pushed a patch today or did "recheck centos", please do a recheck.
Those jobs were not triggered.
* Please actually verify that the jobs for your patches have started. You
can do that by visiting https://build.gluster.org/job/smoke/ (for smoke) or
https://build.gluste
Note: I've retriggered smoke/regression where appropriate for all patches
posted since the issue started.
On Fri, Jul 14, 2017 at 1:00 PM, Nigel Babu wrote:
> Hello,
>
> ## Highlights
> * If you pushed a patch today or did "recheck centos", please do a
> recheck.
t this out!
>
> Regards,
> Amar
>
>
>>
>>
>> --
>> *From: *"Pranith Kumar Karampuri"
>> *To: *"Anoop C S"
>> *Cc: *"gluster-devel"
>> *Sent: *Thursday, June 29, 2017 7:36:45 PM
>> *
Hi Jeff,
It appears that something changed in https://review.gluster.org/#/c/17771.
The tarball with the logs for that patch was 32G. That doesn't sound right.
Is something writing to log excessively after this patch landed?
--
nigelb
___
Gluster-devel
> On Mon, Jul 17, 2017, at 02:00 PM, Jeff Darcy wrote:
>
> On Mon, Jul 17, 2017, at 09:28 AM, Nigel Babu wrote:
>
> It appears that something changed in https://review.gluster.org/#/c/17771.
> The tarball with the logs for that patch was 32G. That doesn't sound right.
> I
Hello folks,
I've just upgraded Gerrit on staging to 2.13.9. Please help test this version.
We're planning to upgrade review.gluster.org in the next 30 to 60 days.
Staging URL: https://gerrit-stage.rht.gluster.org/
Release Notes: https://www.gerritcodereview.com/releases/2.13.md
--
nigelb
__
Niels, could you look at this failure? It seems to have started post-merge
of this patch: https://review.gluster.org/#/c/17779/
On Mon, Jul 24, 2017 at 1:04 PM, Atin Mukherjee wrote:
> Bump.
>
> Failures are constant. May I request someone from replicate team to take a
> look at it?
>
> On Fri
Hello folks,
I'm going to do an unplanned restart of Gerrit in the next 2 minutes so we
pick up a Java security update. It's blocking a few people from logging
into Gerrit
--
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.
017 at 10:06 AM, Raghavendra Gowdappa
wrote:
> A Gentle reminder.
>
> @everyone,
>
> Do we've a process to be followed in this scenario?
>
> regards,
> Raghavendra
>
> - Original Message -
> > From: "Raghavendra Gowdappa"
> > To: &qu
> >
> > I am not the owner/author of these patches and AFAIK, only a owner can
> > abandon patches.
>
> And the owners of these patches are not currently active in the project.
> So, I cannot discuss with them and arrive at a consensus to abandon them.
>
> > > > >
> > > > > https://review.gluster.o
On Wed, Aug 16, 2017 at 8:19 PM, Niels de Vos wrote:
> On Wed, Aug 16, 2017 at 06:05:20PM +0530, Deepshikha Khandelwal wrote:
> > Hello everyone,
> >
> > We have been testing static analysis for Gluster on the CI system for the
> > last few weeks.
> >
> > We have implemented cppcheck[1] and clang
This change is taking the first step towards implementing those ideas. One
of the major blockers to implementing them was that it was difficult to
grant easy access to change the hook. Granting production access to Gerrit
is next to impossible unless you really know what you're doing.
We'll not in
On Thu, Aug 17, 2017 at 5:36 PM, Mohammed Rafi K C
wrote:
>
>
> On 08/17/2017 05:07 PM, Nigel Babu wrote:
>
> This change is taking the first step towards implementing those ideas. One
> of the major blockers to implementing them was that it was difficult to
> grant easy
Shwetha,
Is this time out configurable? Or is it hard-coded into the glusto-tests
repo?
On Sat, Aug 26, 2017 at 1:59 AM, Shyam Ranganathan
wrote:
> Nigel was kind enough to kick off a glusto run on 3.12 head a couple of
> days back. The status can be seen here [1].
>
> The run failed, but manag
Hello folks,
I spend some time today mucking about trying to figure out how to make our
documentation search a better experience. The short answer is, search kind
of works now.
Long answer: mkdocs creates a client side file which is used for search.
RTD overrides this by referring people to Elast
Hello folks,
We need to fix a networking problem on Jenkins, upgrade, and apply a few
security fixes to Jenkins. We'll be going into quiet mode now and any jobs
still running at 18:30 will be canceled and re-triggered after the restart.
--
nigelb
___
G
The restart and upgrade is complete. Any jobs that were triggered during
the quiet period are starting up now.
On Tue, Aug 29, 2017 at 4:05 PM, Nigel Babu wrote:
> Hello folks,
>
> We need to fix a networking problem on Jenkins, upgrade, and apply a few
> security fixes to Jenki
Hello,
To reduce confusion, we've setup docs.gluster.org pointing to
gluster.readthedocs.org. Both URLs will continue to work for the forseeable
future.
Please update any references that you control to point to docs.gluster.org. At
some point in the distant future, we will switch to hosting docs.
Why are we failing because the first "rebalance status" fails? Isn't it
supposed to check in a loop and wait until it succeeds?
Specifically, I think line 288 and 289 need to be removed
http://git.gluster.org/cgit/glusto-tests.git/tree/glustolibs-gluster/glustolibs/gluster/rebalance_ops.py#n288
I
Hello folks,
A few times, we've merged dependent patches out of order because the Submit
type[1] did not block us from doing so. The last few times we've talked about
this, we didn't actually take a strong decision either way. In yesterday's
maintainers meeting, we agreed to change the Submit type
On Thu, Sep 07, 2017 at 12:17:32PM +0530, Atin Mukherjee wrote:
> One basic question (rather clarification) here. If indeed a rebase is
> necessary for a patch which was posted some time back and a regression was
> passed at that time, with this change will a (centos) regression job
> re-triggered
1 - 100 of 331 matches
Mail list logo
