Almost all Perf bots are purple because of bot_update exception. |
||||
Issue description
Traceback (most recent call last):
File "/b/rr/tmp6AImve/rw/checkout/infra/.recipe_deps/recipe_engine/recipe_engine/run.py", line 424, in run
recipe_result = recipe_script.run(api, api._engine.properties)
File "/b/rr/tmp6AImve/rw/checkout/infra/.recipe_deps/recipe_engine/recipe_engine/loader.py", line 59, in run
self.RunSteps, properties, self.PROPERTIES, api=api)
File "/b/rr/tmp6AImve/rw/checkout/infra/.recipe_deps/recipe_engine/recipe_engine/loader.py", line 514, in invoke_with_properties
**additional_args)
File "/b/rr/tmp6AImve/rw/checkout/infra/.recipe_deps/recipe_engine/recipe_engine/loader.py", line 475, in _invoke_with_properties
return callable_obj(*props, **additional_args)
File "/b/rr/tmp6AImve/rw/checkout/infra/recipes/android/perf.py", line 141, in RunSteps
bot_update_step = api.bot_update.ensure_checkout()
File "/b/rr/tmp6AImve/rw/checkout/infra/.recipe_deps/recipe_engine/recipe_engine/recipe_api.py", line 382, in _inner
return func(*a, **kw)
File "/b/rr/tmp6AImve/rw/checkout/infra/.recipe_deps/depot_tools/recipe_modules/bot_update/api.py", line 296, in ensure_checkout
co_root = step_result.json.output['root']
KeyError: 'root'
,
Sep 23 2016
,
Sep 23 2016
hinoka@'s on an airplane right now. Can you please post a link to some of the offending builds so we don't have to dig through them and guess?
,
Sep 23 2016
Maybe crbug/649703 ?
,
Sep 23 2016
The b-lab slaves are hitting some gob rate limiting issue. I think this is a side effect of https://bugs.chromium.org/p/chromium/issues/detail?id=649603 and https://bugs.chromium.org/p/chromium/issues/detail?id=649661
,
Sep 23 2016
I see a lot of: [0:00:34] fatal: remote error: Daily ls-remote rate limit exceeded for IP 70.32.137.216 [0:00:34] fatal: remote error: Daily ls-remote rate limit exceeded for IP 70.32.137.216 [0:00:36] fatal: remote error: Daily ls-remote rate limit exceeded for IP 70.32.137.216 [0:00:38] fatal: remote error: Daily ls-remote rate limit exceeded for IP 70.32.137.216 Yeah, looks like the same thing as that bug in #5. |
||||
►
Sign in to add a comment |
||||
Comment 1 by sullivan@chromium.org
, Sep 23 2016