-
Notifications
You must be signed in to change notification settings - Fork 5k
[browser][MT] System.Net.Http.Functional.Tests failure ("Why are we setting the target on an unoccupied slot?") #104524
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
Labels
arch-wasm
WebAssembly architecture
area-GC-mono
area-VM-threading-mono
Known Build Error
Use this to report build issues in the .NET Helix tab
os-browser
Browser variant of arch-wasm
Milestone
Comments
Tagging subscribers to this area: @BrzVlad |
Not only |
Now I'm thinking this could be a root cause #107974 |
|
removing blocking-clean-ci as it has not failed in 30 days
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
arch-wasm
WebAssembly architecture
area-GC-mono
area-VM-threading-mono
Known Build Error
Use this to report build issues in the .NET Helix tab
os-browser
Browser variant of arch-wasm
Log
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=760113
Build error leg or test failing: WasmTestOnFirefox-MT-System.Net.Http.Functional.Tests.WorkItemExecution
Pull request: #104103
Error Message
Fill the error message using step by step known issues guidance.
Report
Summary
Report
Summary
The text was updated successfully, but these errors were encountered: