Increase Blazor Wasm crank timeout to 20 minutes#2158
Merged
LoopedBard3 merged 1 commit intoaspnet:mainfrom Mar 6, 2026
Merged
Increase Blazor Wasm crank timeout to 20 minutes#2158LoopedBard3 merged 1 commit intoaspnet:mainfrom
LoopedBard3 merged 1 commit intoaspnet:mainfrom
Conversation
The Blazor Wasm benchmark was timing out at the default 10-minute crank timeout. Add explicit timeout of 20 minutes to the crank job message body. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Adds an explicit 20-minute timeout to the Blazor WASM crank job configuration to prevent benchmark runs from timing out under slower test environments.
Changes:
- Set the crank job message body
timeoutto 20 minutes (00:20:00) in the Blazor scenarios pipeline config.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
DrewScoggins
approved these changes
Mar 5, 2026
ilonatommy
added a commit
that referenced
this pull request
Mar 9, 2026
PR #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: #2158 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
LoopedBard3
pushed a commit
that referenced
this pull request
Mar 9, 2026
PR #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: #2158 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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 Blazor Wasm benchmark was timing out at the default 10-minute crank timeout. Add explicit timeout of 20 minutes to the crank job message body.
This was timing out in the Gold tests while taking 9m 40s in the Intel Perf Lin tests for Blazor Wasm, so I expect slightly upping the timeout time to help with the Gold tests not finishing. Pipeline run hitting this error: https://dev.azure.com/dnceng/internal/_build/results?buildId=2919052&view=results.