-
Notifications
You must be signed in to change notification settings - Fork 37
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 interface_zmq functional test case #116
Fix interface_zmq functional test case #116
Conversation
@madnadyka you were right, I did a fresh sync after merges, clean and rebuild and
|
Use correct keccak256 hash and single sha256 to verify block and transactions.
db873a0
to
307c9ac
Compare
Hi @madnadyka I did a fresh rebase against latest master the I would be grateful if you checked this pull request and the test case again. Please make sure that you have
and when you call
after that with a rebuild you should hopefully see:
|
Now it is passed |
Thank you for merging everything! |
HI @gitcoindev ! |
Dear @wu-emma, thank you a lot, I really appreciate it. This is a great
start into the New Year. I will try submit new PRs by mid/end of January.
sob., 31 gru 2022 o 14:36 wu-emma ***@***.***> napisał(a):
… HI @gitcoindev <https://github.com/gitcoindev> !
thanks for your contributions, good job!
Send you 2k USDT (for now)
https://etherscan.io/tx/0x55c8092a842aa5f8f29f8311a54b24b71be1201ce127d5275883fdb8d3ffccf6
Guys would check the PRs volume just in case.
All the best in New Year!
—
Reply to this email directly, view it on GitHub
<#116 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVFGLNPZV3EJIOAHCYMWV5LWQAZEJANCNFSM6AAAAAATEPQRVI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi @gitcoindev ooops... I occasionally sent it via BSC network. Hope you would be able to retrieve/bridge it, sorry. |
Hi @wu-emma thank you a lot! I really appreciate this. I was able to bridge this one, no worries! |
Description
The goal of this pull request is to fix interface_zmq functional test case.
Notes
The test case needed two separate fixes: first was the bugfix from Bitcoin core bitcoin/bitcoin#17185 , then my bugfix for Bitgesell, to verify against keccak256 and single sha256.
Hi @madnadyka @wu-emma @janus I'd be grateful if you found time for the review
I opened a batch of new pull requests fixing functional tests including this one
#107
#108
#109
#110
#111
#112
#113
#114
#115
#116
After those pull request will be reviewed and merged there are last remaining failing tests (all of them not trivial or requiring a lot of integration, I estimate 5-10 days to fix) that I would like to tackle in January next year:
After those are fixed in the new batch of pull requests we should have all functional tests passing and could integrate all new tests from Bitcoin core if functionality is already available in Bitgesell and you would be interested to integrate them.
PR reward address
0x7e92476D69Ff1377a8b45176b1829C4A5566653a (ETH mainnet or Polygon)