test: fix op e2e tests for the updates of finality gadget #41
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,
bournezjc,
parketh,
gusin13 and
bap2pecs
parketh
approved these changes
Aug 21, 2024
SebastianElvis
approved these changes
Aug 21, 2024
|
lgtm 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 op e2e tests. This fix sets the
BitcoinRPCHostwith a special string "mock-btc-client", and then, in finality gadget, we checkBitcoinRPCHostand use the mock btc client for "mock-btc-client".Context: the finality gadget's 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 abitcoindrather than the mock btc client.Test Plan