Expose authoritative portable code sets - #79
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.
Summary
PORTABLE_CODE_SETSexport from themexecution_store_failureand harness-onlystructural_validationThe conformance pin advances to merged registry head
5ba78c7. This is the repository-standard minimal pin update needed for the generated closed-code registry vectors; it also contains six merged logical execution-store scope vectors now exercised by the driver.Validation
make check(274 passed, 5 skipped)make conformanceagainst conformance5ba78c7and specificationcc4b0d7(288 passed)scripts/verify_distribution.pyPORTABLE_CODE_SETSand the category enum exportsFixes #78