Repository navigation
Conversation
This branch has not been deployed
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
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.
Since enforcer v1.0.1, the integration test of every PR fails with
unsupported_bitcoin_core_version, because CI downloads the movingbip300301-enforcer-latestbuild (Core 30 to 32) andL1-bitcoin-patched-latest(Core 29.2). CI now downloads the enforcer release at the submodule tag, and gets the ecash-com/bitcoin node throughfetch_ecash_bitcoin.sh, as the enforcer CI does. The submodule moves to v1.0.1, because the v1.0.0 script cannot read the current releases.ecash.com layout and v1.0.0 does not accept Core 32.