-
Notifications
You must be signed in to change notification settings - Fork 17
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
F/consumer rewards e2e #301
base: base/consumer-chain-support
Are you sure you want to change the base?
Conversation
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.
The test lgtm, great work! Only comment is about whether to use submodule or git clone for getting babylon-sdk repo. Also CI failed though
@@ -30,7 +30,10 @@ cosmos-relayer-rmi: | |||
docker rmi babylonlabs-io/cosmos-relayer 2>/dev/null; true | |||
|
|||
build-ibcsim-bcd: | |||
docker build --tag babylonlabs-io/ibcsim-bcd -f ibcsim-bcd/Dockerfile ${BABYLON_FULL_PATH} | |||
cp -a $(BABYLON_FULL_PATH)/babylon-sdk/ $(BABYLON_FULL_PATH)/contrib/images/ibcsim-bcd |
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.
Wdyt we use git clone
for getting babylon-sdk repo to a gitignore
-ed directory, instead of a submodule? suggesting this as submodules are quite troublesome due to those git submodule init
and git submodule update
stuff
|
||
// Ensure consumer rewards are generated and sent to the staking contract | ||
s.Eventually(func() bool { | ||
rewards, err := s.cosmwasmController.QueryStakingContractBalances() |
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.
Great 👍
Btw, shall we create a Github issue for moving the entire |
Adds rewards generation e2e test.
This first adapts / fixes the existing e2e tests to work with the new multi-contract setup.
Uses a sub-module to build the
ibcsim-bcd
container from thebabylon-sdk
reference; which is something that can clearly be improved. Perhaps in a follow-up?Also, there are some (unrelated to staking integration) e2e tests that are failing. Commented them out in the
test-e2e
Makefile target. Sorted out this target so that is both up-to-date and depending on other existing targets, for robustness.CI should use these targets as well. Perhaps in a follow-up?