Remove integrity_sync
data in stable phase
#2999
Merged
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.
Description
This PR fixes the problem reported at #2814.
The problem occurs because the setup and stable phases are calculated using only the data of the master node (since that is the only node whose performance is seriously affected during setup). However, sometimes workers can display a last Integrity_sync log dated after the end of the setup phase on the master, causing the failure.
Integrity sync data in a worker after the setup phase is now discarded, so the error no longer occurs.
Logs example
Tests
pycodestyle --max-line-length=120 --show-source --show-pep8 file.py
.provision_documentation.sh
generate the docs without errors.