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.org/job/regression-test
Hi,
With the introduction of default python 3 shebangs and the change in
configure.ac to correct these to py2 if the build is being attempted on
a machine that does not have py3, there are a couple of issues
uncovered. Here is the plan to fix the same, suggestions welcome.
Issues:
- A configure j
Hi,
Updates on the release and shout out for help is as follows,
RC0 Release packages for testing are available see the thread at [1]
These are the following activities that we need to complete for calling
the release as GA (with no major regressions i.e):
1. Release notes (Owner: release owner
On Tue, Sep 25, 2018 at 3:38 PM ABHISHEK PALIWAL
wrote:
> Hi Pranith,
>
> I have some questions if you can answer them:
>
>
> What in LIBC exit() routine has resulted in SIGSEGV in this case ?
>
As per the stack trace you provided it is _IO_unbuffer_all():
(gdb) bt
#0 0x3fffad4463b0 in _IO_u
