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

e2e tests with gaia fail #1568

Open
5 tasks
Tracked by #2283
mpoke opened this issue Jan 17, 2024 · 3 comments
Open
5 tasks
Tracked by #2283

e2e tests with gaia fail #1568

mpoke opened this issue Jan 17, 2024 · 3 comments
Assignees
Labels
scope: testing Code review, testing, making sure the code is following the specification. type: bug Issues that need priority attention -- something isn't working

Comments

@mpoke
Copy link
Contributor

mpoke commented Jan 17, 2024

Summary of Bug

The e2e tests with Gaia fail. First it’s an issue with Dockerfile.gaia as it needs to build Gaia with go 1.20, but ICS requires go 1.21. Then, it fails because gaiad doesn’t have the genesis command, i.e., Error: unknown command "genesis" for "gaiad".

Version

bd5b1ef

Steps to Reproduce

Run make test-gaia-e2e-short


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?
@mpoke mpoke added type: bug Issues that need priority attention -- something isn't working scope: testing Code review, testing, making sure the code is following the specification. labels Jan 17, 2024
@mpoke
Copy link
Contributor Author

mpoke commented Jan 17, 2024

The most likely issue is that the genesis root command was introduced with SDK v0.47, while the current version of Gaia (v14.1.0) uses SDK 0.45. Thanks @glnro for pointing this out.

@p-offtermatt
Copy link
Contributor

Hey @bermuell this sounds like we might be able to fix with the infra you are building for the compatibility tests, wdyt?

@bermuell
Copy link
Contributor

bermuell commented Jan 17, 2024

Hey @bermuell this sounds like we might be able to fix with the infra you are building for the compatibility tests, wdyt?

need to look into that in detail but I'd say that should be possible with the new infra by adding a new test driver for that version.

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. type: bug Issues that need priority attention -- something isn't working
Projects
Status: 📥 F2: Todo
Development

No branches or pull requests

4 participants