AWS2 ddb-streams integration tests failures #2860 #2951
Merged
Conversation
This file contains 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
JiriOndrusek
force-pushed
the
aws2-ddb-test
branch
from
4555194
to
979b566
Compare
oscerd
approved these changes
Jul 27, 2021
aldettinger
approved these changes
Jul 27, 2021
|
@aldettinger Issue can not be replicated manually or at least I wasn't able to (without tweaking some component code). I was testing it on a machine provided by the reporter. The same behavior could reproduced with the use of |
|
Build error doesn't seem to be related to the code change: |
|
I agree, the build issue must be related to post release steps. So let's merge. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #2860
Problem was caused by the fact that on slower machines, route containing consumer is started, but consumer isn't receiving (not started). Then it could easily happen, that some events are ignored because of that.
I added a periodical check, that some random (init event) are received. These init events have to be created periodically to be sure that consumer is running in the moment of event's creation.