feat: test kyve image in interchaintest

[shifty11]

Summary by CodeRabbit

• New Features
  • Enhanced the Makefile to support building Kyve and Kaon images.
  • Improved testing framework to include upgrades for the Kyve cosmos chain alongside Kaon.
• Refactor
  • Updated test setup and teardown functions to accommodate new configurations for Kyve.

[coderabbitai]

Walkthrough

The recent updates involve integrating the Kyve blockchain with existing systems, paralleling the setup previously done for Kaon. This includes modifying the Makefile to build images for Kyve, and adjusting test configurations and scripts to support both Kyve and Kaon, ensuring they are properly initialized and tested during upgrades.

Changes

File Path	Change Summary
Makefile	Added functionality to build Kyve and Kaon images.
interchaintest/.../v1_5/upgrade_test.go	Added kyve initialization and included it in test setup and teardown alongside kaon.
interchaintest/.../v1_5/upgrade_utils_test.go	Introduced a new mainnetConfig for the Kyve cosmos chain.

🐇💻
In the realm of code where the data hops around,
A rabbit crafted changes, with hardly a sound.
Kyve joins the dance, with Kaon in the fray,
Together they'll test, and frolic all day.
Oh, what a sight, these blockchains in sync,
Thanks to the rabbit, who's smarter than you think! 🌟🚀

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f6ace3e and 8da9d2f.

Files selected for processing (3)

• Makefile (1 hunks)
• interchaintest/upgrades/v1_5/upgrade_test.go (3 hunks)
• interchaintest/upgrades/v1_5/upgrade_utils_test.go (1 hunks)

Additional comments not posted (6)

interchaintest/upgrades/v1_5/upgrade_utils_test.go (1)

40-59: The configuration for the Kyve blockchain in mainnetConfig is correctly set up and matches the project requirements.

interchaintest/upgrades/v1_5/upgrade_test.go (4)

36-36: The initialization of the kyve variable is consistent with the existing blockchain setup and correctly integrates the Kyve blockchain into the test environment.

---

44-44: The setup of kyveWallet is correctly implemented to handle wallet operations for the Kyve blockchain, mirroring the setup for kaonWallet.

---

56-70: The modifications in the BeforeAll function to include both kaon and kyve in the test setup are correctly implemented and necessary for comprehensive testing.

---

90-91: The modifications in the AfterAll function to stop all nodes for both kaon and kyve are correctly implemented, ensuring proper resource cleanup after tests.

Makefile (1)

192-194: The addition of build commands for the Kyve image in the Makefile is correctly implemented, mirroring the existing process for the Kaon image.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2