-
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
[wasm] Wasm.Build.Tests
failing with Generator 'JSExportGenerator' failed to initialize
.. FileNotFoundException
.. Microsoft.Interop.SourceGeneration
#74944
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue Details
Also seen on #74705 .
|
Wasm.Build.Tests failing with
Generator 'JSExportGenerator' failed to initialize..
FileNotFoundException..
Microsoft.Interop.SourceGeneration`Wasm.Build.Tests
failing with Generator 'JSExportGenerator' failed to initialize
.. FileNotFoundException
.. Microsoft.Interop.SourceGeneration
@ericstj could this be related to #74897 ? This is a wasm template project being built with a rc2 sdk, and This is effectively what's being run:
|
Yes, you need #74943 |
It is a bit disheartening that #74897 landed without running a test of the JSImport generator, the wasm built tests would have indicated there was a problem. |
|
I'm pretty surprised that nothing in the PR validation caught this problem. I tried to go back and inspect the build for that PR but I cannot find it. cc @ViktorHofer |
The PR didn't run any pipelines at all - https://github.com/dotnet/runtime/pull/74897/checks . Probably because of the recent CI issues. |
Yeah, that's my working theory. I hope we have some coverage in place that we produce a ref-pack that can be compiled against. I could imagine a gap here though, and it's something that ought to be filled. |
Wasm.Build.Tests.WasmTemplateTests
failing on multiple PRs. On #74704 it failed with:Also seen on #74705 .
cc @maraf @pavelsavara
Report
Summary
The text was updated successfully, but these errors were encountered: