-
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
ILASM - Disable fileversionpreservation
test
#71972
ILASM - Disable fileversionpreservation
test
#71972
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsShould stop this from failing for now: #71919 ILASM does not support embedding or generating resource data; we would need to add that functionality. It used to exist, but it depended on
|
@dotnet/jit-contrib ready for review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're disabling it for all configurations. You only need to disable it for ilasm round-trip testing.
Use IlasmRoundTripIncompatible
. See https://github.com/dotnet/runtime/blob/main/docs/workflow/ci/disabling-tests.md and other test examples that use this.
Is this test failure happening now because the recent changes mean we're actually (finally) running the round-tripped dll?
Yes. I'll correctly disable the test. |
…o disable roundtrip test for fileversionpreservation
bbc901e
to
70ccd4f
Compare
@dotnet/jit-contrib ready for review again. I used |
Should stop this from failing for now: #71919
ILASM does not support embedding or generating resource data; we would need to add that functionality. It used to exist, but it depended on
CvtRes.exe
which the dotnet team does not own; which is the reason the resource embedding support was removed. See dotnet/coreclr#20818 and #11412