Google Git
Sign in
chromium / infra / luci / luci-go / 13d8a2b3726e27f3c15a51c7d144798fcc04f859
commit13d8a2b3726e27f3c15a51c7d144798fcc04f859[log] [tgz]
authorQuang Minh Tuan Nguyen <nqmtuan@google.com>Thu Jan 12 07:21:58 2023
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jan 12 07:21:58 2023
tree7f8a09a2b22efe977c504f52c581aa8bc7ed2489
parentd0a2875cbaed5d64474e66898490ad8c5e7b0d3c [diff]
[Bisection] Only cancel build if the succeeded build is more recent

Current behavior: If we receive buildbucket pubsub that a new build has succeeded, we cancel analysis for the same builder

Problem: There may be cases that a build start earlier may finish later.  In case that the succeeded build was based on an older revision, we don't want to cancel the current analysis.


Bug:1295566
Change-Id: I006b2f6c3a4719736470b233bf0593d43d13b44a
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4159759
Auto-Submit: Tuan Nguyen <nqmtuan@google.com>
Commit-Queue: Anne Redulla <aredulla@google.com>
Reviewed-by: Anne Redulla <aredulla@google.com>
4 files changed
tree: 7f8a09a2b22efe977c504f52c581aa8bc7ed2489
  1. analysis/
  2. appengine/
  3. auth/
  4. auth_service/
  5. bisection/
  6. build/
  7. buildbucket/
  8. casviewer/
  9. cipd/
  10. client/
  11. cmdrunner/
  12. common/
  13. config/
  14. cv/
  15. deploy/
  16. examples/
  17. gae/
  18. gce/
  19. grpc/
  20. hardcoded/
  21. led/
  22. logdog/
  23. luci_notify/
  24. lucicfg/
  25. lucictx/
  26. luciexe/
  27. mailer/
  28. milo/
  29. mmutex/
  30. provenance/
  31. resultdb/
  32. scheduler/
  33. scripts/
  34. server/
  35. standalone/
  36. starlark/
  37. swarming/
  38. third_party/
  39. tokenserver/
  40. tools/
  41. vpython/
  42. web/
  43. .gitallowed
  44. .gitattributes
  45. .golangci.yml
  46. AUTHORS
  47. codereview.settings
  48. CONTRIBUTING.md
  49. CONTRIBUTORS
  50. go.mod
  51. go.sum
  52. LICENSE
  53. OWNERS
  54. PRESUBMIT.py
  55. README.md
  56. tools.go
  57. 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.