ci: temporarily disable CBMC checks (known-broken) - #1461
Merged
Conversation
The CBMC CI checks are currently known-broken. Because "cbmc / Run CBMC tests" is a required status check in the repo ruleset, skipping the job (if: false) would leave the check permanently pending and block all PR merges. Instead, replace the job's steps with a single no-op step that prints a disabled/known-broken note and exits 0, so the required check still reports success and PRs stay mergeable. The original steps are preserved as comments so re-enabling is just uncommenting them once CBMC is fixed.
joehendrix
approved these changes
Aug 6, 2026
tautschnig
approved these changes
Aug 6, 2026
shigoel
enabled auto-merge
August 6, 2026 22:23
github-actions
Bot
added
the
github_actions
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
5 participants
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.
What
Temporarily disables the CBMC CI checks, which are currently known-broken. They will be re-enabled once fixed.
Approach
The
cbmc_testjob keeps its identity (nameRun CBMC tests) but its steps are replaced with a single no-op step that prints a "temporarily disabled / known-broken, will be re-enabled" note (plus a::warning::annotation for visibility) and exits 0. The required check therefore still reports success and PRs stay mergeable — no ruleset edits required.The original steps are preserved verbatim as comments in
cbmc.yml, so re-enabling CBMC is just deleting the no-op step and uncommenting them.