Fix flaky test in LogUtilTest.groovy #92
Open
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.
I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
Problem
This PR aims to fix the flaky test: com.yahoo.parsec.logging.LogUtilTest."test generateLog with custom data object should return info contain custom json data"
parsec-libraries/parsec-logging/src/test/groovy/com/yahoo/parsec/logging/LogUtilTest.groovy
Lines 39 to 45 in 142bc4c
The above check fails as the order of the items in
log_data
varies upon non-determintic shuffling.I found and confirmed the flaky behaviour of the test using an open-source research tool NonDex, which shuffles implementations of nondeterminism operations.
Solution
This PR fixes the test by checking for both possibilities of
log_data
.parsec-libraries/parsec-logging/src/test/groovy/com/yahoo/parsec/logging/LogUtilTest.groovy
Line 44 in bec72f0
Steps to reproduce
The following command can be used to reproduce the assertion errors and verify the fix.
Integrate NonDex:
Add the following snippet to the top of the build.gradle in $PROJ_DIR:
Append to build.gradle in $PROJ_DIR:
Execute Test with Gradle:
Run NonDex:
Test Environment:
Please let me know if you have any concerns or questions.