-
Notifications
You must be signed in to change notification settings - Fork 84
Fix: Functional Tests #90
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
Fix: Functional Tests #90
Conversation
This will be needed to postpone difficulty adjustment modifications to a block in the future throughout the functional tests
…sqlite warning message in DigiByte Core
…, CORE: increased peer timeouts
…ady being tracked' error
…get support for BIP68
… functional test)
…empool, even if they were not supposed to
…tocol consensus from 70016 to 70018
… to bumped protocol version to 70018
…tial getaddr broadcast
…to DigiByte's small maturity param
…hain tx required due to small maturity of DigiByte coins
… that only one output is created
…-date with test_framework. 2/3 subtests are failing. Core code needs to be adjusted.
JaredTate
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK. Once again amazing work @SmartArray. Having these tests working is a fundamental step towards a very stable 8.22. The client compiles, runs, and works great.
gto90
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK
|
❤️ |
ycagel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cACK
Fix: Functional Tests
160 commits later, this PR finally fixes all 158 failing functional test by adapting them to the DigiByte network and chainparams.
Before this PR can be tested and merged, #89 needs to be accepted and merged because the functional tests will only run through if the core-related issues are fixed.
In order to fix the tests, it was required to
COIN_MATURITYparameterscryptas a python library that will be called during the tests-easypowthat turns off MultiAlgo during tests that are executed in regtest environment