[resultui] use computed invocation ID to query resultdb

1. Use computed invocation ID to query resultdb.
2. Change how uninitialised invocation ID is represented to make it
easier to update.
3. Add test cases.

After this CL:
1. old builds that don't support the new invocation ID format will not
work correctly. This will be fixed in the next CL.
2. result tab's rendering time will be reduced by 200-1000ms when
accessed directly.

R=nodir@chromium.org, nqmtuan@google.com

Bug: 1114935
Change-Id: Ie82d61895b87ddb9220dbbc22c4c462a38b22239
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/2712050
Reviewed-by: Nodir Turakulov <nodir@chromium.org>
Commit-Queue: Weiwei Lin <weiweilin@google.com>
7 files changed
tree: cb0bb153dae161b8484ef1795bbbd056731d67c4
  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. scheduler/
  42. server/
  43. starlark/
  44. swarming/
  45. tokenserver/
  46. tools/
  47. tumble/
  48. vpython/
  49. 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.