Fix lints in integration testing API #340
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.
Problem description
When I introduced the
api
module and turned on optional lints about the (non-)pub
types, I forgot to exposepub
functions from theintegration_testing
module. This was not spotted by the CI, because the checks were run without--cfg cpp_integration_testing
inRUSTFLAGS
.What's done
integration_testing
module is made pass the optional lints.cargo check
is now run with the--all-targets
flag, so that it checks tests, too (not only the lib crate).cargo clippy
is now run with thecpp_integration_testing
option inRUSTFLAGS
to make the integration testing code covered by the linter.Pre-review checklist
[ ] I have implemented Rust unit tests for the features/changes introduced.[ ] I have enabled appropriate tests inMakefile
in{SCYLLA,CASSANDRA}_(NO_VALGRIND_)TEST_FILTER
.[ ] I added appropriateFixes:
annotations to PR description.