Google Git
Sign in
chromium / infra / luci / luci-go / 6b39aad695a65a004d6c59e14188da1c4b171671
commit6b39aad695a65a004d6c59e14188da1c4b171671[log] [tgz]
authorAnushruth <anushruth@google.com>Thu Mar 06 19:32:58 2025
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Mar 06 19:32:58 2025
treee5c15f7485a6b4fbe188c2c18d3617735d5d2ce1
parented69c91a7479c3273556d28dbefb46763d377e2c [diff]
[gcep] Fix the inspect swarming task delete VM logic

Bug: b/395973590

This patch adds the fix introduced in crrev/c/6277626 to inspect
swarming task. Both of these tasks operate on all the VMs periodically.
The manage-bot task validates the VMs listed in gcep datastore as
opposed to inspect swarming, which lists bots from swarming and then
performs all the validations. For completion the new flow is

       1. Bot is dead and has a termination_task_id
                Kill the VM
        3. Bot is dead and was last seen more than vm.Timeout ago
                Kill the VM

Change-Id: Idc280ca3323a40101735b50ac7eb78c533452a44
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/6332025
Reviewed-by: Gowri Denduluri <gowriden@google.com>
Commit-Queue: Anushruth Sasivehalli <anushruth@chromium.org>
Reviewed-by: Justin Suen <justinsuen@google.com>
Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
1 file changed
tree: e5c15f7485a6b4fbe188c2c18d3617735d5d2ce1
  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.