commit | 99e7f18e8172a3bfc53d3374f5dbc8905c5e0223 | [log] [tgz] |
---|---|---|
author | Scott Lee <ddoman@chromium.org> | Tue Oct 27 01:50:40 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 27 01:50:40 2020 |
tree | 90d93564f541c3861cb8b323e7718d43aacb2d1d | |
parent | 7719ce32ec590df59570ad087a4b48956f08ecfb [diff] |
[resultdb] remove the custom log format rdb-stream is mostly run on Swarming tasks, and having the timestamps shown on each log line can be helpful for diagnosing performance regressions. Additional CLs will be sent to print the performance stats at the end of a sink run. However, timestamps on each log are still useful. R=nodir@chromium.org CC=vadimsh@chromium.org Bug: 1141568 Change-Id: I6ff4e92bd842547f109722525d3dc747c3b966e3 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/2500769 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Scott Lee <ddoman@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.