Re: [Gluster-devel] [Gluster-Maintainers] 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-devel] Announcing Softserve- serve yourself a VM

On 02/28/2018 06: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 automatically afterwards. Now

[Gluster-devel] Out of regression builders

As both Shyam & I are running multiple flavours of manually triggered regression jobs (lcov, centos-7, brick-mux) on top of https://review.gluster.org/#/c/glusterfs/+/20637/ , we'd need to occupy most the builders. I have currently run out of builders to trigger some of the runs and have observed

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

On 08/11/2018 02:09 AM, Atin Mukherjee wrote: > 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 >

Re: [Gluster-devel] Master branch lock down status (Wed, August 08th)

On 08/09/2018 10:58 PM, Raghavendra Gowdappa wrote: > > > On Fri, Aug 10, 2018 at 1:38 AM, Shyam Ranganathan > wrote: > > On 08/08/2018 09:04 PM, Shyam Ranganathan wrote: > > Today's patch set 7 [1], included fixes provided till last evening IST, > > and

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

On 08/10/2018 09:59 PM, Shyam Ranganathan wrote: > Today's patch set is 9 [1]. > > Total of 7 runs for line-coverage, mux regressions, centos7 regressions > are running (some are yet to complete). > > Test failure summary is as follows, Updating this section 1.

Re: [Gluster-devel] tests/bugs/core/multiplex-limit-issue-151.t timed out

On 08/11/2018 12:43 AM, Mohit Agrawal wrote: > File a bug https://bugzilla.redhat.com/show_bug.cgi?id=1615003, I am not > able to extract logs > specific to this test case from the log dump. This is because the test is calling cleanup twice in its exit bash traps. - First, the test itself sets a

Re: [Gluster-devel] Master branch lock down status (Sat. Aug 10th)

Patch set 10: Run status Line-coverage 4/7 PASS, 7/7 PASS-With-RETRY Mux-regressions 4/55 PASS, 1 core CentOS7 Regression 3/7 PASS, 7/7 PASS-With-RETRY ./tests/bugs/replicate/bug-1408712.t (2 fail/retry) ./tests/bugs/glusterd/quorum-validation.t (1 fail/retry)

Re: [Gluster-devel] Master branch lock down status (Wed, August 08th)

On Sat, Aug 11, 2018 at 10:33 PM, Shyam Ranganathan wrote: > On 08/09/2018 10:58 PM, Raghavendra Gowdappa wrote: > > > > > > On Fri, Aug 10, 2018 at 1:38 AM, Shyam Ranganathan > > wrote: > > > > On 08/08/2018 09:04 PM, Shyam Ranganathan wrote: > > > Today's