We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As part of IntersectMBO/ouroboros-network#759 (PR IntersectMBO/ouroboros-network#1554) we introduced tests for the BlockchainTime in the presence of an unstable clock. However, it would be good to extend also the consensus tests to apply clock changes, to catch stuff like IntersectMBO/ouroboros-network#1570 and IntersectMBO/ouroboros-network#1544 (comment) .
BlockchainTime
The text was updated successfully, but these errors were encountered:
Thomas and I think that Issue #753 is essentially blocking this: letting the nodes' clocks jump independently will effectively introduce clock skew.
Letting the nodes' clocks all jump together, remaining in sync, seems less interesting, but it would almost certainly be easier to test.
Sorry, something went wrong.
Unless UTCTime is reset, that doesn't seem particularly useful to test 😁
nfrisby
No branches or pull requests
As part of IntersectMBO/ouroboros-network#759 (PR IntersectMBO/ouroboros-network#1554) we introduced tests for the
BlockchainTime
in the presence of an unstable clock. However, it would be good to extend also the consensus tests to apply clock changes, to catch stuff like IntersectMBO/ouroboros-network#1570 and IntersectMBO/ouroboros-network#1544 (comment) .The text was updated successfully, but these errors were encountered: