Repository navigation
Route TLA+ verification through the shared Oracle queue - #44
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.
Route the existing
formal/run_tlc.shentry point through the shared Oracle queue for local development and the maintained-branch CI workflow. The queued worker preserves the existing TLC jar pin, explicit tool overrides, Java flags, 3 case configurations and native verdict rules, and returns exact case logs, exits and measured tool identity. Backend failure never falls back to local execution.Validation: the ordinary local entry point passed all 3 cases through the deployed Oracle queue. Independent review verified the exact candidate against its original native implementation and unchanged models/workflows; all 23 adapter controls passed, including malformed worker markers, capture failures and explicit tool overrides. Bash syntax and whitespace checks passed. Dedicated repository CI accounts are being activated before the workflow is re-enabled; final maintained-branch CI evidence follows integration.