Skip to content

Multiple release builds deadlocks on Windows flutter_release_builder #168934

@matanlurey

Description

@matanlurey

We have 5 32x CPU builders allocated to the release-pool.

As defined in engine/src/flutter/.ci.yaml we have 2 orchestrator builds for Windows:

- name: Windows windows_android_aot_engine
recipe: engine_v2/engine_v2
timeout: 120
properties:
add_recipes_cq: "true"
release_build: "true"
config_name: windows_android_aot_engine
# Do not remove(https://github.com/flutter/flutter/issues/144644)
# Scheduler will fail to get the platform
drone_dimensions:
- os=Windows
- name: Windows windows_host_engine
recipe: engine_v2/engine_v2
timeout: 120
properties:
add_recipes_cq: "true"
release_build: "true"
config_name: windows_host_engine
# Do not remove(https://github.com/flutter/flutter/issues/144644)
# Scheduler will fail to get the platform
drone_dimensions:
- os=Windows

For the release process, each of these uses one of our (very limited) 5 32x CPU builders just to spawn other (actual) builders:

When multiple builds are running, (i.e. 2), 4 of the 5 builders are used for orchestration!

We should try to move these to Linux-based orchestrators - there is no reason to use a Windows build at the moment.

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listinfra: chromiuminfra: recipesIssues with flutter/recipesinfra: releaseRelease-related requests and toolingteam-infraOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure team

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions