-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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][aot] Almost all library tests failing on Windows with RuntimeError: null function or function signature mismatch
#61721
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsPR failing on windows:
|
Similar failure with
|
System.Runtime.Tests
failing with RuntimeError: null function or function signature mismatch
System.Runtime.Tests
failing on Windows with RuntimeError: null function or function signature mismatch
Does this only fail on windows ? |
I've only seen this on windows. |
It's hitting here
cc @BrzVlad |
System.Runtime.Tests
failing on Windows with RuntimeError: null function or function signature mismatch
RuntimeError: null function or function signature mismatch
- Update chrome+chromedriver for helix tests to latest stable (`96.0.4664.45`) - Enable library tests to run on Windows, for manual runs - Disable windows/AOT builds completely due to #61721 - Disable failing WBT tests on windows due to #61725 - Disable JS interop tests failing with new chrome - #61945 Co-authored-by: Radek Doulik <radek.doulik@gmail.com>
I am able to reproduce it with browser-bench sample on windows. It fails in Here is the function from bench sample build on windows. The error happens in The diff between windows sample and imac sample. I have also tried to bisect the problem on windows. The bench sample AOT version started to fail with 62eafc1. It doesn't crash the same way though, as the bench sample changed too and I am not able to build the current version with 62eafc1 build. @vargaz do you know what might be wrong here? |
Edit: nm. I re-checked the |
They had been disabled earlier because of dotnet#61721
They had been disabled earlier because of #61721
PR failing on windows:
Build
Log
The text was updated successfully, but these errors were encountered: