Flaky test fix, add NPE protection in TestCloudEventCallbackProperty #2704
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.
Issues
#2700 [Failed CI Test] testUserDefinedCallback
Description
afterTest cleanup method assumes that callbackProperty has already been instantiated and is not null. Tests are run sequentially but the order is not guaranteed unless specifically set, so we can't assume the property is not null.
Added null check and also renamed the method for clarity
Tests
N/A
You can reproduce this issue by running the test method on its own using the master branch:
$ mvn test -Dtest=TestCloudEventCallbackProperty#testUserDefinedCallback -pl=helix-core
After the change:
$ mvn test -Dtest=TestCloudEventCallbackProperty#testUserDefinedCallback -pl=helix-core