Disable autotests for beacon_chain crate
#2658
Merged
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.
Issue Addressed
NA
Proposed Changes
Following @michaelsproul's example in #2404, this disables
autotestsfor thebeacon_chaincrate. This means the tests in thetestsdirectory all compile as a single binary, rather than individual binaries. This reduces total compilation time.Benchmarks
With autotests (i.e.,
unstable):Without autotests (this PR):
This is running on my hex-core machine. I suspect the improvement will be much greater on lower-core-count hardware since they can't compile multiple crates in parallel.
Additional Info
@michaelsproul I'm not very well informed on
autotests, I could use your eyes to make sure I'm not missing anything 🙏