-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Closed
Labels
Buildersx/build issues (builders, bots, dashboards)x/build issues (builders, bots, dashboards)FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.
Milestone
Description
On several CLs lately, I've seen nearly all of the builders complete within 10 minutes or so, but the linux-arm-aws
and linux-arm64-aws
TryBots always seem to take 15 minutes or more.
It appears that these builders aren't currently sharded at all:
https://cs.opensource.google/go/x/build/+/master:dashboard/builders.go;l=2417;drc=9ca9dc28e477c63197a65122b31a98146c49d07d
https://cs.opensource.google/go/x/build/+/master:dashboard/builders.go;l=2434;drc=9ca9dc28e477c63197a65122b31a98146c49d07d
Is there something we can do to bring the latency for these builders up to par with the other TryBots? (Perhaps enable sharding?)
(CC @prattmic, who I think has done some recent latency measurements)
Metadata
Metadata
Assignees
Labels
Buildersx/build issues (builders, bots, dashboards)x/build issues (builders, bots, dashboards)FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.
Type
Projects
Status
Done