chore: optimize build and test cycle times#2
Merged
Conversation
5 tasks
4 tasks
3 tasks
strawgate
added a commit
that referenced
this pull request
Apr 14, 2026
- Fix pending_acks count in stalled batch scenario: after ACKing #3, only #1 and #3 are in pending_acks (2, not 3) since #2 hasn't been ACKed yet at that step. - Remove 'queued' from checkpoint-blocking states. Per the TLA+ spec, only sent batches (via begin_send) participate in ordered-ack. Queued batches that were never sent are invisible to the checkpoint machine and should not block advancement. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This was referenced Apr 20, 2026
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.
The tests were extremely slow to compile because
codegen-units = 1andlto = "thin"were applied under the[profile.release]block inCargo.toml(which Cargo uses internally when runningcargo test --release).This PR untangles testing and release processes, extracting these heavy performance optimisations into a dedicated
[profile.production]block that inherits fromrelease.After this change:
cargo test --releasewill run optimally fast (parallelized codegen, 0 LTO), slashing cycle time drastically.cargo build --profile productionwhen ultimate runtime performance is needed.