On 8 August 2018 at 06:11, Shyam Ranganathan wrote:
> 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
On Wed, Aug 8, 2018 at 5:08 AM 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
> how to find failures.
>
> 1) We are running the tests using the patch [2].
>
> 2) Run d
I have posted a patch https://review.gluster.org/#/c/20657/ and start
brick-mux regression to validate the patch.
Thanks
Mohit Agrawal
On Wed, Aug 8, 2018 at 7:22 AM, Atin Mukherjee wrote:
> +Mohit
>
> Requesting Mohit for help.
>
> On Wed, 8 Aug 2018 at 06:53, Shyam Ranganathan
> wrote:
>
>>
+Mohit
Requesting Mohit for help.
On Wed, 8 Aug 2018 at 06:53, Shyam Ranganathan wrote:
> 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
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 failed in run:
https://b
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.gluster.org/job/
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
how to find failures.
1) We are running the tests using the patch [2].
2) Run details are extracted into a separate sheet in [3] named "Run
Failures"
On Tue, Aug 7, 2018, 10:46 PM Shyam Ranganathan wrote:
> On 08/07/2018 02:58 PM, Yaniv Kaul wrote:
> > The intention is to stabilize master and not add more patches that my
> > destabilize it.
> >
> >
> > https://review.gluster.org/#/c/20603/ has been merged.
> > As far as I can see, it h
On 08/07/2018 02:58 PM, Yaniv Kaul wrote:
> The intention is to stabilize master and not add more patches that my
> destabilize it.
>
>
> https://review.gluster.org/#/c/20603/ has been merged.
> As far as I can see, it has nothing to do with stabilization and should
> be reverted.
Posted
On Mon, Aug 6, 2018 at 1:24 AM, Shyam Ranganathan
wrote:
> 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 eve
GlusterFS Coverity covscan results for the master branch are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-08-07-9e03c5fc/
Coverity covscan results for other active branches are also available at
http://download.gluster.org/pub/gl
Hello folks,
We are planning to reduce coverity errors to improve upstream stability.
To avoid duplicate efforts and concerns like patch review, we suggest
following rules :-
1. Visit https://scan.coverity.com/projects/gluster-glusterfs and
request to "Add me to project" to see all reported cove
12 matches
Mail list logo
