-
Notifications
You must be signed in to change notification settings - Fork 790
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
Run ILVerify #17953
Run ILVerify #17953
Conversation
✅ No release notes required |
Separated baselines, if it succeeds, it's ready. |
The CI step feels wrong - it finished in 1m30s only, I think it did not do the build at all. |
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.
See CI - was too fast and did not error.
Ah, path issue, gonna fix it tomorrow |
Wasn't the path issue, but the issue of me commenting out part of the script to test locally, and forgetting to uncomment. Script will also fail now if the DLL is not on the path. |
@T-Gro this is passing now: Also checked with false positives (invalid baselines) - resulted in the step failure. |
Run ilverify on each PR. Currently it fails on a bunch of "invalid" codegen. Not sure if it makes sense to ignore current one, or create a baseline (which would be much better).
I will see how it runs in CI and create a baseline, so no new codegen changes are introduced.