Seems like there was a spike for all build times yesterday probably added
up to give slow Jenkins scheduling times for triggers. Also, seems like we
had three spikes that are about a week apart recently.


On Thu, Feb 7, 2019 at 11:46 AM Michael Luckey <adude3...@gmail.com> wrote:

> What might have some influence is the implicit disabling of the build
> cache by activating Jacoco report. There seems to be a increase of
> beam_PreCommit_Java_Cron with
> https://builds.apache.org/job/beam_PreCommit_Java_Cron/914/ and looking
> into cacheable task there seems to be lots of work done now which
> previously was cacheable.
>
> Not sure, whether this is the culprit- or part of it -, but I d suggest to
> upgrade to gradle 5 pretty fast.
>
> On Thu, Feb 7, 2019 at 8:18 PM Udi Meiri <eh...@google.com> wrote:
>
>> If anyone has done any investigation/is working on this please share.
>>
>> I'm investigating Jenkins slowness. I've noticed it happening since
>> yesterday: precommits taking 3 hours to start, phrase commands similarly
>> taking as much time to register.
>>
>> My current theory is that we have a job that's are taking much longer
>> than usual to run.
>>
>

Reply via email to