Tie CBMC to 5.95.1 given 6.0.0 alpha is causing PR's to fail #96
Conversation
This file contains 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
Skptak
reviewed
Dec 14, 2023
Co-authored-by: Soren Ptak <ptaksoren@gmail.com>
Skptak
reviewed
Dec 14, 2023
Co-authored-by: Soren Ptak <ptaksoren@gmail.com>
paulbartell
approved these changes
Dec 14, 2023
Skptak
approved these changes
Dec 14, 2023
This was referenced Aug 23, 2024
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.
CBMC proofs in our repositories that default to using the latest version of CBMC are currently failing due to either a bug or breaking change in the pre-production version of cbmc 6.0.0. Tying the CBMC version to 5.95.1 (latest stable, working release on our repos) to resolve this issue in the meantime. Please revert this change once there is a new production release.
Note: There is a message on the latest release of CBMC stating "This release is to test our infrastructure and shouldn't be used in a production setting."