[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>
1 file changed
tree: 90d93564f541c3861cb8b323e7718d43aacb2d1d
  1. .gitallowed
  2. .gitattributes
  3. .gitignore
  4. AUTHORS
  5. CONTRIBUTING.md
  6. CONTRIBUTORS
  7. LICENSE
  8. OWNERS
  9. PRESUBMIT.py
  10. README.md
  11. WATCHLISTS
  12. appengine/
  13. auth/
  14. buildbucket/
  15. casviewer/
  16. cipd/
  17. client/
  18. cmdrunner/
  19. codereview.settings
  20. common/
  21. config/
  22. cq/
  23. cv/
  24. dm/
  25. examples/
  26. gae/
  27. gce/
  28. grpc/
  29. hardcoded/
  30. led/
  31. logdog/
  32. luci_notify/
  33. lucicfg/
  34. lucictx/
  35. luciexe/
  36. machine-db/
  37. milo/
  38. mmutex/
  39. mp/
  40. resultdb/
  41. rts/
  42. scheduler/
  43. server/
  44. starlark/
  45. swarming/
  46. tokenserver/
  47. tools/
  48. tumble/
  49. vpython/
  50. web/
README.md

luci-go: LUCI services and tools in Go

GoDoc

Installing

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

Contributing uses the same flow as Chromium contributions.