Failed to fetch step information from LogDog |
|
Issue descriptionLoading these three tryjob builds recently: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux-chromeos-compile-dbg/7714 https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux-chromeos-dbg/558 https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux_chromium_chromeos_msan_rel_ng/1067 First of all they took forever to load, like 30 s or more, and then they just show: --- Failed to fetch step information from LogDog context deadline exceeded - no logs - --- Screenshot: https://screenshot.googleplex.com/bex798a1zTV.png When reloading, it loads successfully.
,
Dec 6
The following revision refers to this bug: https://chromium.googlesource.com/infra/luci/luci-go.git/+/9d3688949727026d533af2086ceb91a558f3789f commit 9d3688949727026d533af2086ceb91a558f3789f Author: Ryan Tseng <hinoka@google.com> Date: Thu Dec 06 18:07:46 2018 [logdog] Increase logs module min instances to 4 (from 2) A bug described symptoms of not enough instances to serve log endpoints. Because flex takes a longer time to spin up instances than classic, it's more important to have idle instances ready to serve. Bug: 910095 Change-Id: I2452fbfd73866321f63d10d57f74aaae9ce83fcb Reviewed-on: https://chromium-review.googlesource.com/c/1355799 Commit-Queue: Ryan Tseng <hinoka@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> [modify] https://crrev.com/9d3688949727026d533af2086ceb91a558f3789f/logdog/appengine/cmd/coordinator/logs/module-logs.yaml |
|
►
Sign in to add a comment |
|
Comment 1 by hinoka@chromium.org
, Nov 29Components: Infra>Platform>LogDog
Status: Available (was: Untriaged)