Repository navigation
[To dev/1.3] [Test] Fix asynchronous assertions in pipe integration tests (#18941) - #18973
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Backport of
c535723a17a9492dc4479de5af7ab0c02864b509(#18941) todev/1.3.This applies the Tree Model fixes to the legacy auto-create pipe integration tests:
assertDataAlwaysOnEnvwhen verifying that stopped pipes do not change receiver data;The source commit's Table Model test changes are omitted because
dev/1.3has no corresponding test paths.Validation:
mvn spotless:apply -pl integration-test -P with-integration-testsmvn test-compile -DskipTests -pl integration-test -P with-integration-testsMultiClusterIT2AutoCreateSchemaprofile, but the local ConfigNode at127.0.0.1:14213refused connections, so the run could not complete.