Fix Blazor Wasm build timeout by setting agent-side buildTimeout#2162
Merged
LoopedBard3 merged 1 commit intoaspnet:mainfrom Mar 9, 2026
Merged
Conversation
PR aspnet#2158 increased the controller-level session timeout to 20 minutes, but the crank agent's build step still used the default 10-minute DefaultBuildTimeout from dotnet/crank. The 'Build is taking too long' error on asp-citrine-lin (build 2921804) was the agent killing the build, not the controller timing out. Add --application.buildTimeout 00:20:00 to the crank args so the agent allows 20 minutes for the Blazor WASM application to build. Ref: aspnet#2158 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
LoopedBard3
approved these changes
Mar 9, 2026
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
2 participants
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.
PR #2158 increased the controller-level session
timeoutin the Service Bus message body to 20 minutes, but the crank agent's build step still used the default 10-minuteDefaultBuildTimeoutfrom dotnet/crank. TheBuild is taking too long. Halting build.error (e.g. build 2921804) was the agent killing the build, not the controller timing out.This adds
--application.buildTimeout 00:20:00to the crank args so the agent allows 20 minutes for the Blazor WASM application to build, matching the pattern used inmono-scenarios.ymlfor long-building scenarios.Ref: #2158
Testing