FYI, the crash that Kaleb mentioned looks like this, so I think Nithya
was right that it's a bug in shutdown. Better than memory corruption,
which is what I tend to think of when I hear about random crashes.
https://build.gluster.org/job/centos6-regression/8304/consoleFull
#0 0x7ff603ce1495
There's nothing like starting the day with a good rant.
As I'm sure many of you know, I'm the project's most active committer.
I'm certainly not the most active *reviewer*. There are several other
candidates for that; my money's on Niels. I'm even further from being
the most active *author*.
On Tue, Oct 31, 2017, at 01:01 AM, Amar Tumballi wrote:
> In this case, I suggest maintainers can send a message to author, and
> send an updated patch with their suggestion (with making sure '--
> author' is set to original author). This can save both the effort of
> review, and also heart
I think we're almost done with the new coding standard. The only
objections on the last round were formatting issues, and the couple of
rounds before that weren't very controversial either. I'm sure there
are many other things we could add to help our fellow developers. I've
seen many of you
On Tue, Oct 3, 2017, at 08:33 AM, Amar Tumballi wrote:
> Meeting date: 10/04/2017 (Oct 4th)
> BJ Link
> * Bridge: https://bluejeans.com/205933580
11:00 UTC?
___
maintainers mailing list
maintainers@gluster.org
I've seen a few patches lately that were merged before affected parties
in other timezones had a chance to see them (or see them in their
current form). In at least one case, a patch wasn't even reviewed by
*anyone* other than its author before being merged. I'd like to
discourage this. Yes,
On Mon, Jul 31, 2017, at 03:06 AM, Amar Tumballi wrote:
> Tuesday (1st Aug) - 8:30pm-9:30pm IST (11am - 12pm EDT).
> Wednesday (2nd Aug) - 5pm - 6pm IST (7:30am - 8:30am EDT)
> Wednesday (2nd Aug) - 7:30pm - 8:30pm IST (10am - 11am EDT)
> Friday (4th Aug) - 5pm - 7pm IST (7:30am - 9:30am EDT)
I just pushed a patch that should ease the process of analyzing recent
regression-test failures.
http://review.gluster.org/#/c/12510/
From the commit message:
> Often a test will fail quite frequently, but not so frequently that it
> will fail twice in a row for the same patch. This
