Gradle cache friendly Junit test fix. #4044
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.
Gradle caches artefacts by task execution signature.
A test module of
core-deterministic
depends on the generated artefacts of an associated data module. Once the data module task is cached its generated outputs are no longer available to the test module (and hence 2 unit tests fail).This fix forces re-execution of the data module prior to running the previously failing test module
VerifyTransactionTest