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 <[email protected]> wrote:

> 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 run takes about an hour to
> run, not including time waiting in the queue.
>


-- 
-------
Jason Kuster
Apache Beam / Google Cloud Dataflow

See something? Say something. go/jasonkuster-feedback

Reply via email to