Skip to content

Conversation

@vzarytovskii
Copy link
Member

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.

@vzarytovskii vzarytovskii requested a review from a team as a code owner November 4, 2024 13:53
@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2024

✅ No release notes required

@dotnet dotnet deleted a comment from psfinaki Nov 4, 2024
@dotnet dotnet deleted a comment from azure-pipelines bot Nov 4, 2024
@vzarytovskii
Copy link
Member Author

Separated baselines, if it succeeds, it's ready.

@T-Gro
Copy link
Member

T-Gro commented Nov 5, 2024

The CI step feels wrong - it finished in 1m30s only, I think it did not do the build at all.
And has some warnings but still has to failed CI.

Copy link
Member

@T-Gro T-Gro left a 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.

@vzarytovskii
Copy link
Member Author

See CI - was too fast and did not error.

Ah, path issue, gonna fix it tomorrow

@vzarytovskii
Copy link
Member Author

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.

@vzarytovskii
Copy link
Member Author

@T-Gro this is passing now:
image

Also checked with false positives (invalid baselines) - resulted in the step failure.

@T-Gro T-Gro merged commit 545efca into dotnet:main Nov 7, 2024
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants