Another run on Jenkins was faster: Ran 1535 tests in 267.273s On Fri, Mar 9, 2018 at 10:52 AM Lukasz Cwik <lc...@google.com> wrote:
> 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 <eh...@google.com> wrote: > >> Is there a way to see OS load statistics? >> >> On Fri, Mar 9, 2018 at 10:24 AM Jason Kuster <jasonkus...@google.com> >> 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. >>> >>> >>> On Fri, Mar 9, 2018 at 10:18 AM Udi Meiri <eh...@google.com> 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 >>> <https://goto.google.com/jasonkuster-feedback> >>> >> >
smime.p7s
Description: S/MIME Cryptographic Signature
