fix: Fixing remote-relative-with-slash fixture on ARM tests

[yhakbar]

Description

Fixes a busted test.

TODOs

Read the Gruntwork contribution guidelines.

• Update the docs.
• Run the relevant tests successfully, including pre-commit checks.
• Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
• Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Added / Removed / Updated [X].

Migration Guide

Summary by CodeRabbit

• Chores
  • Updated the referenced version of the remote Terragrunt module in test fixtures.
  • Improved test reliability by adjusting error output expectations to account for informational logs.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
terragrunt-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 19, 2025 8:16pm

[coderabbitai]

📝 Walkthrough

Walkthrough

The change updates the version of a remote Terragrunt module referenced in a test fixture by modifying the source attribute in the terraform block from v0.77.22 to v0.78.4. Additionally, a test was modified to remove an assertion that stderr is empty, allowing for informational logs on stderr without causing test failures.

Changes

File(s)	Change Summary
test/fixtures/download/remote-relative-with-slash/terragrunt.hcl	Updated the terraform block's source attribute to a new version
test/integration_run_test.go	Removed assertion that stderr is empty in TestRunNoStacksGenerate, added comment explaining logs may appear on stderr

Suggested reviewers

• levkohimins
• denis256

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.

---

Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 602d44a and de2dbc1.

📒 Files selected for processing (1)

• test/integration_run_test.go (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

`**/*.go`: Review the Go code for quality and correctness. Make sure that the Go code follows best practices, is performant, and is easy to understand and maintain.

**/*.go: Review the Go code for quality and correctness. Make sure that the Go code follows best practices, is performant, and is easy to understand and maintain.

• test/integration_run_test.go

⏰ Context from checks skipped due to timeout of 90000ms (20)

• GitHub Check: Build (windows/amd64)
• GitHub Check: Build (windows/386)
• GitHub Check: Build (darwin/amd64)
• GitHub Check: Build (darwin/arm64)
• GitHub Check: Test (Mock)
• GitHub Check: Test (Parse)
• GitHub Check: Test (AWS Terraform 1.11)
• GitHub Check: Test (Provider Cache Tofu)
• GitHub Check: Test (Windows)
• GitHub Check: Test (Provider Cache Terraform 1.11)
• GitHub Check: Test (Tflint)
• GitHub Check: Test (AWS Terraform 1.5)
• GitHub Check: Test (GCP)
• GitHub Check: Test (AWS Tofu)
• GitHub Check: Test (Fixtures Terraform 1.5)
• GitHub Check: Test (Fixtures Terraform 1.11)
• GitHub Check: Test (Fixtures OpenTofu 1.9)
• GitHub Check: Test (macos)
• GitHub Check: Test (ubuntu)
• GitHub Check: Pull Request has non-contributor approval

🔇 Additional comments (1)

test/integration_run_test.go (1)

109-114: Good adjustment to make tests more resilient.

Removing the assertion on stderr is a sensible change that makes the tests more robust by avoiding false failures due to informational logs. This is especially important for cross-platform testing (like ARM) where different architectures might produce slightly different output.

The added comment clearly explains the rationale behind this change, which is excellent for future maintainers.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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.

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.