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: upgrade test #1870

Closed
5 tasks
yaruwangway opened this issue Nov 3, 2022 · 2 comments
Closed
5 tasks

test: upgrade test #1870

yaruwangway opened this issue Nov 3, 2022 · 2 comments
Assignees
Labels
scope: testing Code review, testing, making sure the code is following the specification.

Comments

@yaruwangway
Copy link
Contributor

yaruwangway commented Nov 3, 2022

Summary

Add upgrade test in workflow for major release/rc-release during release process.
This test is triggered by a label "major_release", and is configured to upgrade from last major release to present version.

EDIT: create nightly build that can be passed to Hypha for testing version-specific features and simulating an upgrade from the current mainnet version

Problem Definition

Proposal


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 the scope: testing Code review, testing, making sure the code is following the specification. label Nov 3, 2022
@okwme
Copy link
Contributor

okwme commented Nov 8, 2022

  • fix the denom KV storage issue and overwrite with correct data
  • make issue on sdk about bank kv store being inconsistent between v045 and v0.46
  • convert script to use cosmovisor so that the panic will actually kill gaiad running and allow the upgrade to take place
  • make a new script that uses recent theta testnet genesis instead of modified genesis from scratch
  • build last release as part of action CI and move to ./build/gaiad7 to run legacy node
  • figure out a way to read the output automatically to determine whether the upgrade succeeded or not
    • check the liveness test logic

@okwme okwme removed their assignment Dec 22, 2022
@mpoke mpoke added this to Cosmos Hub Jan 26, 2023
@github-project-automation github-project-automation bot moved this to 🩹 Triage in Cosmos Hub Jan 26, 2023
@mpoke mpoke moved this from 🩹 Triage to 📥 Todo in Cosmos Hub Jan 26, 2023
@MSalopek
Copy link
Contributor

Closing as completed in #2328

Please favor reopening #2328 in case additional work needs to be done or there is more information.

EDIT: create nightly build that can be passed to Hypha for testing version-specific features and simulating an upgrade from the current mainnet version

Currently the relevant release/* branches and main are used.

@github-project-automation github-project-automation bot moved this from 📥 Todo to ✅ Done in Cosmos Hub Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: testing Code review, testing, making sure the code is following the specification.
Projects
Status: ✅ Done
Development

No branches or pull requests

3 participants