-
Notifications
You must be signed in to change notification settings - Fork 706
Chore/extract chainstate from peer #6536
New issue
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
Chore/extract chainstate from peer #6536
Conversation
ece960e
to
8531746
Compare
…N string Signed-off-by: Jacinta Ferrant <[email protected]>
…tacks-core into chore/extract-chainstate-from-peer
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## aac-client-breaking #6536 +/- ##
=======================================================
+ Coverage 75.06% 79.94% +4.88%
=======================================================
Files 566 568 +2
Lines 345526 346578 +1052
=======================================================
+ Hits 259370 277084 +17714
+ Misses 86156 69494 -16662
... and 224 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
…_replay Renaming block-replay script to block-validation
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
…only-for-miner bugfix: enforce bitcoin rpc only for miner
…fallible-to-compile-phase-6467 refactor: aac convert infallible error to compile time
Signed-off-by: Jacinta Ferrant <[email protected]>
Signed-off-by: Jacinta Ferrant <[email protected]>
…tacks-core into chore/extract-chainstate-from-peer
…-boiler-plate Feat/aac testing boiler plate
… into chore/extract-chainstate-from-peer
Signed-off-by: Jacinta Ferrant <[email protected]>
Replaced by #6557 |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This builds upon #6531 which should get merged first. It might be a worthwhile effort to simplify a lot of our tests that utilize TestPeer to use TestChainstate directly (i.e. a lot of them don't even rely on the mempool/Relayer threads etc.) but I would only do this as a follow on and more piece meal.