chromium/src
0
Fork 0
Code Activity

docs: Clarify infra resource usage needed for hardware-requests

Browse Source 
Since it's not 100% clear.

Bug: None
Change-Id: I147db67fbe737997aa77a0b18747010bbc23bf5b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4355717
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Reviewed-by: Gary Tong <gatong@chromium.org>
Auto-Submit: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1120735}
This commit is contained in:
Ben Pastene
2023-03-22 19:54:46 +00:00
committed by Chromium LUCI CQ
parent 7765fa7f51
commit feded0eb91
2 changed files with 5 additions and 4 deletions
docs/infra
new_builder.md
testing/buildbot
README.md

3
docs/infra/new_builder.md

@@ -101,7 +101,8 @@ describe the amount needed, along with any specialized hardware that's required
(e.g. mac hardware, attached mobile devices, a specific GPU, etc.). Note that (e.g. mac hardware, attached mobile devices, a specific GPU, etc.). Note that
even if there's hardware currently available for the new builder, a resource even if there's hardware currently available for the new builder, a resource
request will still be needed if the footprint of the new builder equates to request will still be needed if the footprint of the new builder equates to
at least 5 VMs or 50 CPU cores. See [go/estimating-bot-capacity](https://goto.google.com/estimating-bot-capacity) at least 5 VMs or 50 CPU cores per hour. See
[go/estimating-bot-capacity](https://goto.google.com/estimating-bot-capacity)
for guidance on how many hosts to request. for guidance on how many hosts to request.
See [infradata docs][4] (internal) for information on how to register See [infradata docs][4] (internal) for information on how to register

6
testing/buildbot/README.md

@@ -115,7 +115,7 @@ test suites to the CQ builders is to:
resource request. Depending on resources, the resource owners may not approve resource request. Depending on resources, the resource owners may not approve
of the request. In which case, see step #5. of the request. In which case, see step #5.
1. Calculate the amount of machine resources needed for the tests. Googlers 1. Calculate the amount of machine resources needed for the tests. Googlers
can use [this dashboard](http://shortn/_nyyTPgDJtF) to determine the can use [this dashboard](http://shortn/_X75IFjffFk) to determine the
amount of bots required by comparing it to a similar suite on the same amount of bots required by comparing it to a similar suite on the same
builder. Do this for each CQ builder and each suite that's being added. builder. Do this for each CQ builder and each suite that's being added.
2. File a [resource request](http://go/file-chrome-resource-bug) for the 2. File a [resource request](http://go/file-chrome-resource-bug) for the
@@ -130,8 +130,8 @@ test suites to the CQ builders is to:
explaining why. This can be revisited if things change. explaining why. This can be revisited if things change.
If your change doesn't affect the CQ but is expected to increase utilization in If your change doesn't affect the CQ but is expected to increase utilization in
the testing pools by any more than 5 VMs or 50 CPU cores, it will still need to the testing pools by any more than 5 VMs or 50 CPU cores per hour, it will still
be approved via a resource request. Consult the need to be approved via a resource request. Consult the
[dashboard](http://shortn/_nyyTPgDJtF) linked above to calculate the resource [dashboard](http://shortn/_nyyTPgDJtF) linked above to calculate the resource
usage of a test change. See http://go/i-need-hw for the steps involved in usage of a test change. See http://go/i-need-hw for the steps involved in
getting the approval. getting the approval.