On Fri, Jul 27, 2018 at 7:36 PM, Shyam Ranganathan <srangana@xxxxxxxxxx> wrote:
On 07/26/2018 12:53 AM, Nigel Babu wrote:
> 3) bug-1432542-mpx-restart-crash.t times out consistently: Thanks Nigel.
> 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?
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@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel
Amar Tumballi (amarts)
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
