Repository navigation
ci: parallelize extended validation and reuse one build plan - #65
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.
The representative Release job serializes core integration tests, properties, a second full-library interchange build, and Criterion dependency compilation. Move extended validation into a parallel job, build all three extended components in one Cabal plan, and keep their flags/build directory consistent so the library is compiled once. The interchange helper accepts repeatable Cabal flags to preserve that plan.
All existing core compiler/build-type checks, portability probes, full optional differential checks, fuzzing and benchmark fixture checks remain. Reuse the previous Release cache on the first extended run, then save an extended-validation cache.
Validation: actionlint, Ruff and whitespace checks pass. Build the three components together locally, then run properties, Criterion fixtures and 577 core interchange checks from that build; all pass with no additional module compilation. Local Arrow/HDF5/ONNX dependencies are absent; CI retains
--require-optionalwith all dependencies installed.