You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
browser-wasm linux Release LibraryTests queues timing out #117974
{
"ErrorMessage": ["Done building Helix work items for scenario WasmTestOn", "The Operation will be canceled. The next steps may not contain expected logs"],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
Known issue validation
Build: 🔎https://dev.azure.com/dnceng-public/public/_build/results?buildId=1102465 Error message validated:[Done building Helix work items for scenario WasmTestOn The Operation will be canceled. The next steps may not contain expected logs] Result validation: ✅ Known issue matched with the provided build. Validation performed at: 7/23/2025 9:52:36 AM UTC
I checked a couple of the logs and it seems the workitems just finished a tiny bit too late, e.g. 5-30mins after AzDO already hit the timeout. So this looks like classic queue capacity issue.
Activity
dotnet-policy-service commentedon Jul 23, 2025
Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.
dotnet-policy-service commentedon Jul 28, 2025
Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.
akoeplinger commentedon Jul 31, 2025
I checked a couple of the logs and it seems the workitems just finished a tiny bit too late, e.g. 5-30mins after AzDO already hit the timeout. So this looks like classic queue capacity issue.