Skip to content
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

Test: default bypass msg test with relayers #2486

Closed
7 tasks
yaruwangway opened this issue May 11, 2023 · 0 comments · Fixed by #2571
Closed
7 tasks

Test: default bypass msg test with relayers #2486

yaruwangway opened this issue May 11, 2023 · 0 comments · Fixed by #2571
Assignees
Labels
status: waiting-triage This issue/PR has not yet been triaged by the team. type: feature-request New feature or request improvement

Comments

@yaruwangway
Copy link
Contributor

yaruwangway commented May 11, 2023

Problem

In present e2e test, "withdraw reward" is proposed as bypass msg, because it is easily tested with one chain setup.
Gaia global fee params will use default "bypass_min_fee_msg_types":

 "bypass_min_fee_msg_types": [
    "/ibc.core.channel.v1.MsgRecvPacket",
    "/ibc.core.channel.v1.MsgAcknowledgement",
    "/ibc.core.client.v1.MsgUpdateClient",
    "/ibc.core.channel.v1.MsgTimeout",
    "/ibc.core.channel.v1.MsgTimeoutOnClose"
  ],

The default bypass msg need to be tested with running relayer.
A test plan and test procedures need to be provided for local and public testnet.

Closing criteria

  • add default bypass-msg test to e2e test as described in test procedures
  • test default bypass-msg in public testnet

For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
  • Is a spike necessary to map out how the issue should be approached?
@yaruwangway yaruwangway added type: feature-request New feature or request improvement status: waiting-triage This issue/PR has not yet been triaged by the team. labels May 11, 2023
@yaruwangway yaruwangway self-assigned this May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-triage This issue/PR has not yet been triaged by the team. type: feature-request New feature or request improvement
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant