From e05d0fa1a088c76b4ac481f4bd861cffe93a388c Mon Sep 17 00:00:00 2001
From: Parker Bibus <parkerbibus@microsoft.com>
Date: Thu, 5 Mar 2026 15:05:02 -0800
Subject: [PATCH] Increase Blazor Wasm crank timeout to 20 minutes

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>
---
 build/blazor-scenarios.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/build/blazor-scenarios.yml b/build/blazor-scenarios.yml
index e09fc342f..c6739b53b 100644
--- a/build/blazor-scenarios.yml
+++ b/build/blazor-scenarios.yml
@@ -54,6 +54,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" ]
         }