-
Notifications
You must be signed in to change notification settings - Fork 127
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] ILLinker crash System.NotImplementedException: Var
in System.Reflection.Metadata
tests
#2963
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsRolling build with
Changes since the last rolling build: 063f7b7...4211dc4 .
cc @eerhardt @buyaa-n @vitek-karas
|
Tagging subscribers to 'linkable-framework': @eerhardt, @vitek-karas, @LakshanF, @sbomer, @joperezr Issue DetailsRolling build with
Changes since the last rolling build: 063f7b7...4211dc4 .
cc @eerhardt @buyaa-n @vitek-karas
|
I guess its better to revert my PR to unblock dotnet/runtime#73410 |
I'm not sure about dotnet/runtime#73410 having this, but this is breaking scheduled rolling builds on |
This is a Cecil bug. Apparently, it also doesn't support generic attributes that Roslyn is introducing support for. It will probably take a while to fix that because it's in Cecil, and that needs to propagate to the linker repo and that needs to propagate to the runtime repo. The System.Reflection.Metadata support for generic attributes is critical for 7.0 (both for our customers and for our own tools that depend on S.R.Metadata, such as the NativeAOT compiler). @buyaa-n Once the revert is done, would it be possible to re-submit just the product change of dotnet/runtime#72561 without the test changes so that we have it in main again soon? |
Yes we can as tests are passed previously, also maybe create an issue and add active issue to the new tests instead of removing them
@radical I am not familiar with what rolling builds does, is there a way to conditionally disable/ifdef the new tests from that build? I removing or commenting those tests is only option? |
Rolling builds are scheduled builds that run twice a day. In this case they are running against 'main' with no other changes. The revert should be enough for them. |
The problem is while building the tests, so ActiveIssue won't cut it. We could alternatively disable building the tests on WASM (with a link to this issue) by adding S.R.Metadata tests somewhere around here: Basically, I want to make sure the S.R.Metadata change ships in 7.0 irrespective of whether the illinker fix makes it. The Roslyn feature is shipping. |
I don't know the details, but can we disable only the specific individual tests for wasm, so they are not included in the test suite at all, instead of disabling tests for the entire library? |
Right, looked into the build log, I see that now. I will try to ifdef the generic attributes part (will run wasm build on my new PR) @MichalStrehovsky please take a look at this log: https://dev.azure.com/dnceng/public/_build/results?buildId=1932703&view=logs&j=d9366717-4230-52c6-0a51-0b43431c29c7&t=c627612c-ea4b-5282-5e42-8a39063fd2d8. It throw |
illinker chokes as soon as it sees this: We would need to ifdef it out (and the corresponding test) on browser. I don't know if we can per-platform ifdef things for libraries that don't have a WASM-specific version (this all targets net7.0, not net7.0-windows/net7.0-browser, etc.). Probably not. |
Right, it needs follow up work now that NativeAOT can parse these attributes. That's why it's critical for this change to get in :). I cannot do the follow up work without the S.R.Metadata change. |
This is just a test though. We can ifdef tests. |
The change was reverted, and we no longer have the crash. Closing this. |
Is there an issue tracking the Cecil bug? |
Not that I know of. |
Reopening then and throwing it over the fence to the linker repo. |
Rolling build with
/p:EnableAggressiveTrimming=true
:Changes since the last rolling build: 063f7b7...4211dc4 .
The only commit with changes to SRM that I can see - b947dd6 .
cc @eerhardt @buyaa-n @vitek-karas
The text was updated successfully, but these errors were encountered: