Skip to content

chore: Make ibc integration test more resilent #171

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

Merged
merged 2 commits into from
Jul 2, 2025
Merged

Conversation

alpe
Copy link
Contributor

@alpe alpe commented Jun 30, 2025

Query balance in a loop.
(AI generated)

Summary by CodeRabbit

  • Bug Fixes
    • Improved reliability of IBC transfer tests by implementing a retry mechanism that repeatedly checks for successful transfers instead of relying on a fixed delay.

@alpe alpe requested a review from a team as a code owner June 30, 2025 14:19
Copy link

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

Copy link
Contributor

coderabbitai bot commented Jun 30, 2025

Walkthrough

The integration test workflow for IBC transfers was updated to replace a fixed sleep and single balance check with a retry loop. This loop polls the Rollkit account balance multiple times, checking for IBC tokens and improving the reliability of detecting transfer completion.

Changes

File(s) Change Summary
.github/workflows/integration_test.yml Replaced fixed sleep and single balance check with a retry loop that repeatedly polls for IBC token arrival.

Sequence Diagram(s)

sequenceDiagram
    participant Workflow
    participant Rollkit
    loop Up to 30 attempts
        Workflow->>Rollkit: Query account balance
        alt IBC denom found
            Workflow-->>Workflow: Exit loop (success)
        else
            Workflow-->>Workflow: Sleep 3 seconds
        end
    end
    alt No IBC denom after 30 attempts
        Workflow-->>Workflow: Log error and exit with failure
    end
Loading

Possibly related PRs

  • test: ibc integration test #138: The main PR refines the IBC transfer integration test workflow by replacing a fixed sleep with a retry loop to check balances, directly building upon the IBC integration test setup introduced in the retrieved PR.

Suggested reviewers

  • randygrok

Poem

In the garden of code, a test takes a leap,
No longer content with a single, fixed sleep.
It hops and it checks, up to thirty times,
Awaiting the tokens, in rhythm and rhymes.
Success when it finds them, it wiggles its nose—
A rabbit’s persistence, as everyone knows! 🐇


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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>, please review it.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.github/workflows/integration_test.yml (2)

370-385: Add set -euo pipefail to fail fast & surface unexpected errors
Inside the run: block the script keeps executing even if any of the intermediary commands (jq, gmd, etc.) error out. A single silent failure would keep the loop spinning until the max-attempts timeout, hiding the real problem.

           celestia-appd tx ibc-transfer transfer transfer channel-0 $ROLLKIT_ADDR 100utia --from validator --node http://localhost:26654 --fees 400utia --keyring-backend test -y
           
+          # fail fast on any unexpected error
+          set -euo pipefail
+
           # Wait for IBC transfer to complete with retry logic

363-386: Trim trailing whitespace & ensure final newline to satisfy YAML lint
The workflow currently triggers YAML-lint warnings (lines 363, 369, 373, 385 and missing newline at EOF). Cleaning these up prevents noisy CI failures.

-          
+         

@@
-            
+

(Apply the same deletion of stray spaces on the other flagged lines and add a terminating newline.)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ef87fbc and 1fac2cf.

📒 Files selected for processing (1)
  • .github/workflows/integration_test.yml (2 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/workflows/integration_test.yml

[error] 363-363: trailing spaces

(trailing-spaces)


[error] 369-369: trailing spaces

(trailing-spaces)


[error] 373-373: trailing spaces

(trailing-spaces)


[error] 385-385: trailing spaces

(trailing-spaces)


[error] 416-416: no new line character at the end of file

(new-line-at-end-of-file)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: test / Run Unit Tests
  • GitHub Check: Test with Rollkit Chain
  • GitHub Check: Test Migration from Cosmos SDK to Rollkit
🔇 Additional comments (1)
.github/workflows/integration_test.yml (1)

364-370: Good resiliency improvement
Replacing the fixed sleep with a bounded retry loop makes the test significantly less flaky while still keeping the overall wall-clock wait time reasonable.

Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm! do you think the other way around works too now btw? if so we should uncomment it and add this logic too.

@alpe
Copy link
Contributor Author

alpe commented Jun 30, 2025

do you think the other way around works too now btw? if so we should uncomment it and add this logic too.

It works on my box :-)

@alpe
Copy link
Contributor Author

alpe commented Jul 1, 2025

Waiting for rollkit main logger changes

@alpe alpe merged commit 8f3f524 into main Jul 2, 2025
12 of 14 checks passed
@alpe alpe deleted the alex/gh_ibc_test branch July 2, 2025 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants