Make expensive validation manual - #9
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.
Routine pushes and pull requests currently spend up to an hour on two fuzz targets and also rerun sanitizers, Shuttle models and benchmarks. That duplicates deliberate validation and delayed the already-reviewed 0.4.6 publication.
Normal CI now keeps the fast check, formatting and native plus Windows no_std gates. The expensive jobs run only when a manual workflow dispatch selects
deep_checks. Publication depends on the fast gates, so a reviewed version can reach crates.io without starting the deep suite again.This changes workflow scheduling only. It does not change code, dependency versions, or the deep checks themselves, and it introduces no lockfile.