Google Git
Sign in
chromium / infra / luci / luci-go / c88f62b7a178
commitc88f62b7a17832a4f48ce4b6737cf0d3a1d337dc[log] [tgz]
authorBeining Chen <beining@google.com>Wed Feb 01 06:48:27 2023
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Feb 01 06:48:27 2023
tree65c30ccdf9dc10715cd05d8ee18580fa74f8d04f
parent4b28252fe20ed61e3f6c2379107e90cfd615a768 [diff]
[Analysis] Derive verdicts from test results in resultCollector and ignore all skipped test runs.

The EngProd team would like to know whether an exonerated test run has flaky or unexpected result in the `chrome-flakiness.weetbix.ci_flaky_test_variants` table. And they want to ignore all skipped test runs.

This change use test results to derive verdict and save to the `verdicts` table. Also, we ignore all skipped test result and if a tv has all test results skipped, it won't be saved to the `verdicts` table.

Test: TEST=INTEGRATION_TESTS=1 go test go.chromium.org/luci/analysis/...

Bug: b:261876756

Change-Id: I53abdaa2f2f34a595559748030b959955742333e
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/4211095
Commit-Queue: Beining Chen <beining@google.com>
Reviewed-by: Patrick Meiring <meiring@google.com>
2 files changed
tree: 65c30ccdf9dc10715cd05d8ee18580fa74f8d04f
  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.