Test peering #519
Merged
Test peering #519
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
Otherwise, the on/off messages are logged regularly every 5-10 seconds or so, despite nothing changes in the freeze mode state. However, keep the warning on same-priority conflicting operators always logged, so that the newly appearing operators are noticed in the logs in every moment in time, not only when the freeze mode is toggled on.
19 tasks
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.
What do these changes do?
Add unit- and functional tests for peering (cross-operator basic synchronization tool to avoid double-processing).
Description
This is the last of the testing topics needed to close #13.
Now, the peering behavior is also tested — same as all other aspects of the framework, and more or less the same way.
In addition, the logging of peering freezes is slightly improved to avoid flooding the freeze-on messages when the state is actually not changed. But keep logging the messages that explain "why" the state is kept "on", even if the reasons change over time.
Issues/PRs
Type of changes
Checklist
CONTRIBUTORS.txt