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.
no space left
for test coverage in red-bank repo.Problem:
Tests are structured:
Every
test_
file gets treated as a separate crate.Generating coverage requires to enable
-Cinstrument-coverage
flag which is used for report generation. It generates instrumented binary files for each test module (crate). These files can be quite large. It consumes almost 2x more space than normalcargo make test
.Solutions:
before my PR
target/coverage
~ 6,5 GB:after my PR
target/coverage
~ 4,3 GB (2,2 GB reduction):We chose solution nr 3. End goal is to simplify these tests and move some of them (unit tests) close to original function (
src
) and intests
keeps only integration tests (multitest).