[ci] Fan formal tasks out in parallel - #4
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
1 participant
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.
Splits the single serial formal job into one runner per SymbiYosys task. A small planning job reads the [tasks] block out of every formal/*.sby and emits the module and task pairs as JSON, and the formal job consumes that with fromJSON as a dynamic matrix.
Wall-clock time becomes the slowest single task plus toolchain setup, rather than the sum of every task. Adding a module or a task needs no change to this file, since the planner globs the directory at run time. fail-fast is off so one failing proof no longer cancels the others, and ci-gate still fails the build if any leg does not succeed, so the required status check keeps its name.