From 8719580283753668da6392ebc1881f282e974bca Mon Sep 17 00:00:00 2001 From: Ilona Tomkowicz Date: Mon, 9 Mar 2026 14:30:55 +0100 Subject: [PATCH] Set agent-side buildTimeout for Blazor Wasm to fix build timeout 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: https://github.com/aspnet/Benchmarks/pull/2158 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- build/blazor-scenarios.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build/blazor-scenarios.yml b/build/blazor-scenarios.yml index c6739b53b..3346a8677 100644 --- a/build/blazor-scenarios.yml +++ b/build/blazor-scenarios.yml @@ -55,7 +55,7 @@ steps: "name": "crank", "condition": "(${{ parameters.condition }})", "timeout": "00:20:00", - "args": [ "${{ parameters.arguments }} --session $(session) ${{ s.arguments }} --application.framework net11.0 --command-line-property --table BlazorWasm --sql SQL_CONNECTION_STRING --cert-tenant-id SQL_SERVER_TENANTID --cert-client-id SQL_SERVER_CLIENTID --cert-path SQL_SERVER_CERT_PATH --cert-sni --chart" ] + "args": [ "${{ parameters.arguments }} --session $(session) ${{ s.arguments }} --application.buildTimeout 00:20:00 --application.framework net11.0 --command-line-property --table BlazorWasm --sql SQL_CONNECTION_STRING --cert-tenant-id SQL_SERVER_TENANTID --cert-client-id SQL_SERVER_CLIENTID --cert-path SQL_SERVER_CERT_PATH --cert-sni --chart" ] } - ${{ each s in parameters.lighthouseScenarios }}: