-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
System.Runtime.InteropServices.JavaScript.Tests.MarshalTests.TestFunctionApply failed on CI (wasm mono subset) #40112
Comments
It seems to be flaky - I got the failure 4 times out of 10 locally. |
Besides that, there can be something like:
|
The failing tests will be disabled in #40139 |
This failure seems to go away if you pass |
cc @vargaz |
We're disabling on demand GC in the release, and I've been working on binding fixes that should fix this for .NET 6. I don't know if the current set of fixes is sufficient yet |
@kg is this still failing for net5.0? |
I never successfully reproduced this bug locally to begin with, so I don't know. |
Ok, I'll take a look. I was able to reproduce it in the past. |
|
@kg was able to reproduce locally |
Some wasm test failures on the PR #39825:
https://dev.azure.com/dnceng/public/_build/results?buildId=749999&view=ms.vss-test-web.build-test-results-tab
e.g.:
System.Runtime.InteropServices.JavaScript.Tests.MarshalTests.TestFunctionApply
The text was updated successfully, but these errors were encountered: