/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
>>>> upg
gradle 5 pretty fast.
>
> On Thu, Feb 7, 2019 at 8:18 PM Udi Meiri <mailto: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
t;>>> 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 wrote:
>>>>
ems 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 wrote:
>>
>>> If anyone
gt;>>
>>> 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 wrote:
>>>
>>>> If anyone has done any investigation/is working on thi
ch
> 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 wrote:
>
>> If anyone has done any investigation/is working on this please share.
>
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 wrote:
> If anyone has done any investigation/is working on this please share.
>
> I'm investigatin
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
> 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.
>
The only statistics I get to see are the build load statistics:
https://builds.apache.org/computer/beam1/load-statistics
On Fri, Mar 9, 2018 at 10:43 AM, Udi Meiri wrote:
> Is there a way to see OS load statistics?
>
> On Fri, Mar 9, 2018 at 10:24 AM Jason Kuster
Is there a way to see OS load statistics?
On Fri, Mar 9, 2018 at 10:24 AM Jason Kuster wrote:
> Jenkins executors are probably less beefy than your development machine
> and also have two slots, thus are likely running two builds at once,
> causing extra slowness.
>
>
>
Jenkins executors are probably less beefy than your development machine and
also have two slots, thus are likely running two builds at once, causing
extra slowness.
On Fri, Mar 9, 2018 at 10:18 AM Udi Meiri wrote:
> Hi,
>
> Does anybody know why Jenkins hosts take so long to
Hi,
Does anybody know why Jenkins hosts take so long to run? For example, beam1
was running beam_PostCommit_Python_Verify and I saw this time for running
"tox -e py27":
Ran 1535 tests in 403.860s
on my workstation I got:
Ran 1535 tests in 160.242s
Is there any way to troubleshoot this? Each
13 matches
Mail list logo