Re: [Gluster-devel] Release 5: Master branch health report (Week of 23rd July)

2018-07-27 Thread Amar Tumballi
On Fri, Jul 27, 2018 at 7:36 PM, Shyam Ranganathan 
wrote:

> On 07/26/2018 12:53 AM, Nigel Babu wrote:
> > 3) bug-1432542-mpx-restart-crash.t times out consistently:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1608568
> >
> > @nigel is there a way to on-demand request lcov tests through
> gerrit? I
> > am thinking of pushing a patch that increases the timeout and check
> if
> > it solves the problem for this test as detailed in the bug.
> >
> >
> > You should have access to trigger the job from Jenkins. Does that work
> > for now?
>
> Thanks Nigel.
>
> After fixing up the Jenkins job to run against a pending commit in
> gerrit and tweaking one more timeout value, this test has passed in lcov
> runs (see [1], still running but the first test that has passed was the
> failing test).
>
> @mohit/@sanju, this is a mux test, and increasing timeouts seem to do
> the trick, but I am not quite happy with the situation, can you take a
> look and see where the (extra) time is being spent and why?
>
>
Notice that lcov tests are at least 1.5x slower than normal, as it dumps
most of the codepath etc into the system. If the timeout is very close to
actual completion time, then there is this chance.



> The other test has also passed in the nightly regressions, post the fix
> in sdfs. So with this we should get back to GREEN on line-coverage
> nightly runs.
>
> [1] line-coverage test run: https://build.gluster.org/job/
> line-coverage/401
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-devel
>
>
>


-- 
Amar Tumballi (amarts)
___
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Release 5: Master branch health report (Week of 23rd July)

2018-07-27 Thread Shyam Ranganathan
On 07/26/2018 12:53 AM, Nigel Babu wrote:
> 3) bug-1432542-mpx-restart-crash.t times out consistently:
> https://bugzilla.redhat.com/show_bug.cgi?id=1608568
> 
> @nigel is there a way to on-demand request lcov tests through gerrit? I
> am thinking of pushing a patch that increases the timeout and check if
> it solves the problem for this test as detailed in the bug.
> 
> 
> You should have access to trigger the job from Jenkins. Does that work
> for now?

Thanks Nigel.

After fixing up the Jenkins job to run against a pending commit in
gerrit and tweaking one more timeout value, this test has passed in lcov
runs (see [1], still running but the first test that has passed was the
failing test).

@mohit/@sanju, this is a mux test, and increasing timeouts seem to do
the trick, but I am not quite happy with the situation, can you take a
look and see where the (extra) time is being spent and why?

The other test has also passed in the nightly regressions, post the fix
in sdfs. So with this we should get back to GREEN on line-coverage
nightly runs.

[1] line-coverage test run: https://build.gluster.org/job/line-coverage/401
___
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] [Gluster-infra] [automated-testing] Gerrit downtime on Aug 8, 2016

2018-07-27 Thread Nigel Babu
Ah, apologies.

Staging URL: http://gerrit-stage.rht.gluster.org/

If you want to try out PolyGerrit, the new UI, click on the footer of the
page that says "Switch to new UI".

On Fri, Jul 27, 2018 at 5:46 PM Sankarshan Mukhopadhyay <
> sankarshan.mukhopadh...@gmail.com> wrote:
>
>> The staging URL seems to be missing from the note
>>
>> On Fri, Jul 27, 2018 at 5:28 PM, Nigel Babu  wrote:
>> > Hello,
>> >
>> > It's been a while since we upgraded Gerrit. We plan to do a full
>> upgrade and
>> > move to 2.15.3. Among other changes, this brings in the new PolyGerrit
>> > interface which brings significant frontend changes. You can take a
>> look at
>> > how this would look on the staging site[1].
>> >
>> > ## Outage Window
>> > 0330 EDT to 0730 EDT
>> > 0730 UTC to 1130 UTC
>> > 1300 IST to 1700 IST
>> >
>> > The actual time needed for the upgrade is about than hour, but we want
>> to
>> > keep a larger window open to rollback in the event of any problems
>> during
>> > the upgrade.
>> >
>>
>
-- 
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Coverity covscan for 2018-07-27-405c6e8a (master branch)

2018-07-27 Thread staticanalysis


GlusterFS Coverity covscan results for the master branch are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-07-27-405c6e8a/

Coverity covscan results for other active branches are also available at
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/

___
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel


[Gluster-devel] Gerrit downtime on Aug 8, 2016

2018-07-27 Thread Nigel Babu
Hello,

It's been a while since we upgraded Gerrit. We plan to do a full upgrade
and move to 2.15.3. Among other changes, this brings in the new PolyGerrit
interface which brings significant frontend changes. You can take a look at
how this would look on the staging site[1].

## Outage Window
0330 EDT to 0730 EDT
0730 UTC to 1130 UTC
1300 IST to 1700 IST

The actual time needed for the upgrade is about than hour, but we want to
keep a larger window open to rollback in the event of any problems during
the upgrade.

-- 
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Wireshark dissectors for Gluster 4.0

2018-07-27 Thread Amar Tumballi
Took a look at the patch!

Looks like you have covered every FOP, other than compound? (which is not
used anywhere now). Is there anything specific which you missed, where you
need help to complete it?





On Fri, Jul 27, 2018 at 11:32 AM, Poornima Gurusiddaiah  wrote:

> Hi,
>
> Here is the patch for dissecting Gluster 4.0 protocol in wireshark [1].
> The initial tests for fops seem to be working. Request you all to add
> missing fops, fix/report any issues in decoding.
>
> [1] https://code.wireshark.org/review/#/c/28871
>
> Regards,
> Poornima
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-devel
>



-- 
Amar Tumballi (amarts)
___
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel