fix(release): stop Windows server build from timing out and cancelling releases#5519
Merged
Merged
Conversation
…g releases The build-server Windows leg ran ~33-34 min warm against a 35-min CI timeout; any cache miss tripped it, and a timed-out job reports as 'cancelled', which fails the release job's build-server==success gate and silently skips the GitHub Release + production deploy. This happened on most daily releases, requiring manual re-runs. Root cause: server-release inherited release's fat LTO + codegen-units=1 (those exist for WASM binary size, not native servers). Switch to thin LTO + 16 codegen units to cut compile time well under the ceiling, and raise the timeout to 55 min for headroom against a cold cache.
matthewevans
enabled auto-merge
July 10, 2026 18:36
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the server-release profile in Cargo.toml to use thin LTO (lto = "thin") and 16 codegen units (codegen-units = 16) to optimize compile times and prevent CI timeouts on Windows. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The build-server Windows leg ran ~33-34 min warm against a 35-min CI
timeout; any cache miss tripped it, and a timed-out job reports as
'cancelled', which fails the release job's build-server==success gate and
silently skips the GitHub Release + production deploy. This happened on
most daily releases, requiring manual re-runs.
Root cause: server-release inherited release's fat LTO + codegen-units=1
(those exist for WASM binary size, not native servers). Switch to thin
LTO + 16 codegen units to cut compile time well under the ceiling, and
raise the timeout to 55 min for headroom against a cold cache.