Fix: fp op e2e tests #21
Merged
Conversation
This file contains 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
lesterli
requested review from
gitferry,
SebastianElvis,
parketh,
gusin13 and
bap2pecs
bap2pecs
approved these changes
Aug 21, 2024
|
cc @SebastianElvis as well |
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.
Summary
This PR fixed the fp op e2e tests. The original codes checked the
BBNChainID, but when the value is "chain-test", it would have the issue b/c for the integration deployment scripts, we spin up a bitcoind rather than the mock btc client.Test Plan
All op e2e tests PASSED in this FP PR: babylonlabs-io/finality-provider#41