Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wasm.Build.Tests.WasmTemplateTests failing with System.TimeoutException : Timeout 30000ms exceeded. #108102

Closed
jkotas opened this issue Sep 21, 2024 · 3 comments
Assignees
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab
Milestone

Comments

@jkotas
Copy link
Member

jkotas commented Sep 21, 2024

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=814594
Build error leg or test failing: Wasm.Build.Tests.WasmTemplateTests.RunWithDifferentAppBundleLocations
Pull request: #108094

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": [ "Browser has been disconnected", "Wasm.Build.Tests.WasmTemplateTests", "System.TimeoutException : Timeout 30000ms exceeded." ],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=814594
Error message validated: [Browser has been disconnected Wasm.Build.Tests.WasmTemplateTests System.TimeoutException : Timeout 30000ms exceeded.]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 9/22/2024 3:45:44 AM UTC

@jkotas jkotas added blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab labels Sep 21, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Sep 21, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Sep 21, 2024
@jkotas jkotas added the arch-wasm WebAssembly architecture label Sep 21, 2024
Copy link
Contributor

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

@jkotas jkotas added area-VM-meta-mono and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Sep 21, 2024
@lewing lewing removed the untriaged New issue has not been triaged by the area owner label Sep 21, 2024
@lewing lewing added this to the 10.0.0 milestone Sep 21, 2024
@lewing
Copy link
Member

lewing commented Sep 22, 2024

I'm not sure why #108074 wasn't matching either

@lewing
Copy link
Member

lewing commented Sep 22, 2024

this was missing the array brackets, closing in favor of #108107

@lewing lewing closed this as completed Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab
Projects
None yet
Development

No branches or pull requests

3 participants