fix: parity timeout 5h -> 12h - #144
Merged
Merged
Conversation
…480 pairs Two consecutive 18,000s timeouts each completed ~2,000 of 2,480 reference pairs; the resumable file proves steady ~2,000/5h progress. A 12h window lets one run finish (resume carries the 1,984 done).
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
1 participant
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.
The 2.1 parity has timed out twice at 18,000s with steady measured progress (~2,000 of 2,480 reference pairs per 5h window). 12h lets a single run complete; the resumable file carries the 1,984 already decoded.