commit | d9019d4804902761f3256f2a23225340069e015f | [log] [tgz] |
---|---|---|
author | Vadim Shtayura <vadimsh@chromium.org> | Fri Feb 01 18:47:02 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Feb 01 18:47:02 2019 |
tree | f61bf1589e16894d000bacb8a42b56322772b269 | |
parent | 19758d5c8f157c17e32cbf15a9dd874a29baa645 [diff] |
[starlark] Print full stack trace when some deep load(...) fails. This is similar to https://chromium-review.googlesource.com/c/1444569 but for load(...). It was harder to spot load(...) had the same problem because there's usually not many errors in the top level of a loaded script (it is just a bunch of function definitions). R=tandrii@chromium.org BUG=833946 Change-Id: I15996fc8da5da71954ec7426a0bf6ddec336ea68 Reviewed-on: https://chromium-review.googlesource.com/c/1449309 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:
fetch infra cd infra/go eval `./env.py` cd src/go.chromium.org/luci
Contributing uses the same flow as Chromium contributions.