-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[8.0] File used by another process in Wasm.Build.Tests.Blazor.SimpleRunTests.BlazorBuildAndRunForDifferentOutputPaths #92805
Labels
arch-wasm
WebAssembly architecture
area-VM-meta-mono
Known Build Error
Use this to report build issues in the .NET Helix tab
Milestone
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsError Blob{
"ErrorMessage": "Wasm.Build.Tests.Blazor.SimpleRunTests.BlazorBuildAndRunForDifferentOutputPaths(config: "Debug", appendRID: False, useArtifacts: True) [FAIL]",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": true
} Reproduction Steps
|
@radical - please triage, and set milestone accordingly. |
removing blocking-clean-ci as it has not been hit in 30 days
|
cc @maraf |
This looks like a failure after test during clean up |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
arch-wasm
WebAssembly architecture
area-VM-meta-mono
Known Build Error
Use this to report build issues in the .NET Helix tab
Error Blob
Reproduction Steps
browser-wasm windows Release WasmBuildTests
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=421749
Error message validated:
Wasm.Build.Tests.Blazor.SimpleRunTests.BlazorBuildAndRunForDifferentOutputPaths(config: "Debug", appendRID: False, useArtifacts: True) [FAIL]
Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 9/29/2023 1:15:06 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: