Repository navigation
Align post-build glibc validation with qualified runtime - #371
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The post-build package check still expected Canonical's
2.43-2ubuntu2.4after the runtime installed the qualified2.43-2ubuntu2.4+pasturestack.1backport. This stopped publisher run 40148828576 after the image exported successfully.Align that one runtime comparison with the final package version. Extend the existing source contract to compare both post-build libc package oracles against the Dockerfile runtime pin, with a regression for each oracle. The official download pin and all other runtime guards stay unchanged.
Validation: the new contract reproduced the original source failure before the fix; all 6 focused tests, Bash syntax validation and
git diff --checkpass after it. Original failed run/API/build log/artifact are retained. No image rebuild, native suite, publication or QA deployment was run for this patch.