-
Notifications
You must be signed in to change notification settings - Fork 1
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
chore(e2e): removing btcd #9
Conversation
-cleanup of test manager
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.
few small comments, but in general looks good
Few additional things:
- in our makefile we can now delete
btcd
andbtcwallet
fromtest-e2e
command: https://github.com/babylonlabs-io/vigilante/blob/dev/Makefile#L55 - in tools.go we can delete the btcd and btcwallet import - https://github.com/babylonlabs-io/vigilante/blob/dev/tools/tools.go#L8
- in our second go.mod we can also delete those - https://github.com/babylonlabs-io/vigilante/blob/dev/tools/go.mod#L9
// Config setting necessary to connect btcwallet daemon | ||
defaultConfig.BTC.BtcBackend = "btcd" | ||
defaultConfig.BTC.BtcBackend = types.Bitcoind | ||
defaultConfig.BTC.WalletEndpoint = "127.0.0.1:18554" |
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.
One follow up task we can have is to remove any references to btcd backend, for example:
.WalletEndpoint
config option makes sense only in case of btcd/btcdwallet combo, in case of bitcoind there will be always one endpoint for bitcoind note/wallet.BTC.BtcBackend
options now makes little sense as we intend to support one backed ie bitcoind
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.
Makes sense to be a separate PR, as the config is used in other places also
e2etest/slasher_e2e_test.go
Outdated
|
||
bsTracker := bst.NewBTCSTakingTracker( | ||
tm.BTCClient, | ||
backend, | ||
tm.BabylonClient, | ||
&bstCfg, | ||
&commonCfg, | ||
logger, | ||
metrics, | ||
rootLogger, |
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.
maybe we don't need logs for tests
rootLogger, | |
zap.NewNop(), |
// mine a block that includes slashing tx | ||
tm.MineBlockWithTxs(t, tm.RetrieveTransactionFromMempool(t, []*chainhash.Hash{unbondingSlashingMsgTxHash})) | ||
require.Eventually(t, func() bool { |
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.
Would be nice to wrap up these eventually check into a function inside the test manager, but is only a suggestion
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.
a couple of suggestions, but LGTM 🚀
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.
LGTM!
This PR removes btcd for running e2e tests and uses bitcoind. Reference issue