Skip to content

GEODE-9050: Backporting the develop version of AbstractPubSubIntegrationTest#7044

Closed
upthewaterspout wants to merge 3 commits intoapache:support/1.14from
upthewaterspout:feature/backport-develop-pubsub-test-GEODE-9050
Closed

GEODE-9050: Backporting the develop version of AbstractPubSubIntegrationTest#7044
upthewaterspout wants to merge 3 commits intoapache:support/1.14from
upthewaterspout:feature/backport-develop-pubsub-test-GEODE-9050

Conversation

@upthewaterspout
Copy link
Contributor

@upthewaterspout upthewaterspout commented Oct 25, 2021

This test is now more lenient about when messages are delivered to the client.
We were previously expecting that if we called publish followed by unsubscribe
we would observe messages from the publish operation, which I don't think was
actually true even before but was failing consistently with the updated netty.

Upgrading our netty dependency to 4.1.68.Final

onichols-pivotal and others added 2 commits October 25, 2021 22:49
Fixing a race condition in ensureOrderingOfPublishedMessages. This test was
expecting the client to receive messages from the server after calling publish,
but the events are processed asynchronously on the client. Changing the test to
wait for the messages to arrive.

Backporting the develop version of this test resulted in new failures, so just
fixing the one race condition we're hitting in support/1.14 for this test.
@upthewaterspout upthewaterspout marked this pull request as draft October 26, 2021 21:49
@upthewaterspout upthewaterspout force-pushed the feature/backport-develop-pubsub-test-GEODE-9050 branch from 9bc577f to 91fa06e Compare October 26, 2021 21:50
This test is not failing for me locally. Adding some debug printouts to try
to see what is going on in CI.
@onichols-pivotal
Copy link
Contributor

this bump was reverted from develop, so won't be backported at this time

@onichols-pivotal
Copy link
Contributor

this bump was re-applied to develop (but with 4.1.70), so backport is back on...although we'll need to decide if 4.1.68 /w netty-all or 4.1.70 /w specific netty jars is the right path, as well as getting path the failing test.

@upthewaterspout
Copy link
Contributor Author

Not using this change for support/1.14, we changed this test a different way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments