Skip to content
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

Validate baseline for lib files #2132

Merged
merged 15 commits into from
Nov 2, 2022
Merged

Validate baseline for lib files #2132

merged 15 commits into from
Nov 2, 2022

Conversation

kennykerr
Copy link
Collaborator

@kennykerr kennykerr commented Nov 2, 2022

As the target libs are binary files and cannot be easily compared, this update stores a text baseline so that we can easily tell if any lib changes have snuck in unawares. The CI build should also validate that no such changes have occurred and fail the build if that's the case.

This just validates the function signatures and associated library names. Ideally, the build can also rebuild all the libs and validate that the lib binaries are identical but that will require more yml trickery.

@kennykerr kennykerr requested a review from riverar November 2, 2022 12:29
@kennykerr
Copy link
Collaborator Author

kennykerr commented Nov 2, 2022

Hmm for some reason, my intentional break of the baseline (479946e) isn't breaking the build.

Oh... 😜

https://github.com/microsoft/windows-rs/actions/runs/3377764644/jobs/5607099985#step:3:23

@kennykerr
Copy link
Collaborator Author

Yay, build now fails if target lib baseline has changed.

@kennykerr kennykerr changed the title Capture and validate baseline for lib files Validate baseline for lib files Nov 2, 2022
@kennykerr kennykerr merged commit c6dfdde into master Nov 2, 2022
@kennykerr kennykerr deleted the baseline branch November 2, 2022 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant