Timeout when opening new logdog-powered build |
||||
Issue descriptionI'm not sure what so special about this build, but I consistently get """ Error: 500 failed to load LogDog annotation stream: encountered error 500, Failed to load stream Request ID: 58ad31cb00ff0835067edd0bf70001737e6c7563692d6d696c6f2d6465760001313532362d3937626637323200010106 """ when opening https://luci-milo-dev.appspot.com/swarming/task/347d53317653dc10?server=chromium-swarm-dev.appspot.com after ~30 sec of waiting. This build was created here: https://luci-scheduler-dev.appspot.com/jobs/infra/infra-continuous-trusty-64/9152410177100076960 (adding this to preserve timestamps and stuff). --- aaand while filing the bug it stopped reproducing, but the most recent build here https://luci-scheduler-dev.appspot.com/jobs/infra/infra-continuous-trusty-64 hangs in similar way (https://luci-milo-dev.appspot.com/swarming/task/347d5efd30157410?server=chromium-swarm-dev.appspot.com) Seems like new builds has a tendency to hang.
,
Feb 23 2017
Oh nice debugging. I see two schools of thought: 1) is that -dev should only talk/impersonate/etc. other -dev instances. 2) is that -dev is development, but can do anything that prod can do. Any opinions on which one should be employed with Milo?
,
Feb 23 2017
1 Delegation tokens from chrome-infra-auth-dev will not work on services connected to chrome-infra-auth. By design.
,
Feb 23 2017
Perfect, OK.
,
Feb 23 2017
https://chrome-internal-review.googlesource.com/c/331163/
,
Feb 23 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/infradata/config/+/ded1c55e4835e131f0bab99cb6fdd6c34a064e08 commit ded1c55e4835e131f0bab99cb6fdd6c34a064e08 Author: Nodir Turakulov <nodir@google.com> Date: Thu Feb 23 22:53:44 2017
,
Feb 27 2017
This is fixed now, right?
,
Feb 27 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by vadimsh@chromium.org
, Feb 23 2017