Google Git
Sign in
chromium / infra / luci / luci-go / 1bf944acb488dd3138da4b72837b50ea5e72efba
commit1bf944acb488dd3138da4b72837b50ea5e72efba[log] [tgz]
authorPatrick Meiring <meiring@google.com>Mon May 19 01:13:43 2025
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon May 19 01:13:43 2025
tree653b02ff6e75140d688e7a516e8a45acada38ae1
parentd41d8e8fbb0b13f98011ed4cbf60d68156ead159 [diff]
[ResultDB] Add order_by support to QueryTestVariants.

Allow the UI to sort by (effective) verdict status v2 instead
of the verdict status v1.

This implementation does come with a caveat, which is that the
status which we do not sort by may not always be correct (e.g.
verdict status v1 may not be correct if we sort by v2 status and
where the number of results in the verdict is more than the
ResultLimit). Also, PASSED and SKIPPED results have the same
sort priority for performance reasons.

BUG=b:415878114
TEST=Integration tests

Change-Id: I5eb923e78c95e120c80541a3a4a771b5b1e732ec
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/6545445
Reviewed-by: Beining Chen <beining@google.com>
Commit-Queue: Patrick Meiring <meiring@google.com>
8 files changed
tree: 653b02ff6e75140d688e7a516e8a45acada38ae1
  1. analysis/
  2. appengine/
  3. auth/
  4. auth_service/
  5. bisection/
  6. build/
  7. buildbucket/
  8. casviewer/
  9. cipd/
  10. cipkg/
  11. client/
  12. common/
  13. config/
  14. config_service/
  15. cv/
  16. deploy/
  17. examples/
  18. gae/
  19. gce/
  20. grpc/
  21. hardcoded/
  22. led/
  23. logdog/
  24. luci_notify/
  25. lucicfg/
  26. lucictx/
  27. luciexe/
  28. mailer/
  29. milo/
  30. mmutex/
  31. provenance/
  32. recipes_py/
  33. resultdb/
  34. scheduler/
  35. scripts/
  36. server/
  37. source_index/
  38. standalone/
  39. starlark/
  40. swarming/
  41. teams/
  42. third_party/
  43. tokenserver/
  44. tools/
  45. tree_status/
  46. vpython/
  47. web/
  48. .gitallowed
  49. .gitignore
  50. .go-lintable
  51. AUTHORS
  52. codereview.settings
  53. CONTRIBUTING.md
  54. CONTRIBUTORS
  55. go.mod
  56. go.sum
  57. LICENSE
  58. OWNERS
  59. PRESUBMIT.py
  60. README.md
  61. staticcheck.conf
  62. tools.go
  63. WATCHLISTS
README.md

luci-go: LUCI services and tools in Go

GoReference

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

It is now possible to directly install tools with go install:

go install go.chromium.org/luci/auth/client/cmd/...@latest
go install go.chromium.org/luci/buildbucket/cmd/...@latest
go install go.chromium.org/luci/cipd/client/cmd/...@latest
go install go.chromium.org/luci/client/cmd/...@latest
go install go.chromium.org/luci/cv/cmd/...@latest
go install go.chromium.org/luci/gce/cmd/...@latest
go install go.chromium.org/luci/grpc/cmd/...@latest
go install go.chromium.org/luci/logdog/client/cmd/...@latest
go install go.chromium.org/luci/luci_notify/cmd/...@latest
go install go.chromium.org/luci/lucicfg/cmd/...@latest
go install go.chromium.org/luci/luciexe/legacy/cmd/...@latest
go install go.chromium.org/luci/mailer/cmd/...@latest
go install go.chromium.org/luci/mmutex/cmd/...@latest
go install go.chromium.org/luci/resultdb/cmd/...@latest
go install go.chromium.org/luci/server/cmd/...@latest
go install go.chromium.org/luci/swarming/cmd/...@latest
go install go.chromium.org/luci/tokenserver/cmd/...@latest
go install go.chromium.org/luci/tools/cmd/...@latest

Contributing

Contributing uses the same flow as Chromium contributions.