Increase retry count for triggered actions test

[ogenstad]

From time to time this test fails, adding some additional retries to see if it's timing related.

Summary by CodeRabbit

• Tests
  • Enhanced test resilience by increasing retry attempts for synchronization validation in integration tests, improving reliability of test execution.

[coderabbitai]

Walkthrough

The change modifies a test file to adjust the retry behavior of the wait_for_sync_to_complete function. An explicit retries parameter set to 20 is now passed to the function invocation. This adjustment increases the number of retry attempts before the operation fails. The surrounding test logic and data flow remain unaltered by this modification.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Increase retry count for triggered actions test" is fully related to and accurately summarizes the main change in the changeset. The modification involves adding an explicit retries parameter (20) to the wait_for_sync_to_complete invocation in the triggered actions test file, which directly aligns with the title's description of increasing the retry count. The title is concise, specific, and clear enough that a teammate reviewing the history would immediately understand the primary purpose of this change—addressing intermittent test failures through additional retry attempts.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch pog-triggered-actions

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 128fa7b and e27323c.

📒 Files selected for processing (1)

• backend/tests/integration_docker/test_triggered_actions.py (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

backend/tests/**/*

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Place backend tests in backend/tests/

Files:

• backend/tests/integration_docker/test_triggered_actions.py

backend/**/*

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Run backend tests with pytest or via invoke tasks

Files:

• backend/tests/integration_docker/test_triggered_actions.py

**/*.py

📄 CodeRabbit inference engine (.github/instructions/python-docstring.instructions.md)

**/*.py: Use triple double quotes (""") for all Python docstrings
Write docstrings in Google-style format
Include a brief one-line description at the top of each docstring
Add a detailed description section when additional context is needed
Document function/method parameters under an Args/Parameters section without typing information
Include a Returns section describing the return value
Include a Raises section listing possible exceptions
Provide an Examples section demonstrating usage when helpful

Use ruff and mypy to validate and lint Python files

**/*.py: Use type hints for all Python function parameters and return values
Prefer asynchronous code in Python when feasible
Define asynchronous Python functions with async def
Use await for asynchronous calls in Python
Use Pydantic models instead of standard dataclasses
Use ruff and mypy for linting and type checking

**/*.py: Use type hints for all Python function parameters and return values
Use async/await whenever possible in Python code
Define asynchronous functions with async def
Await asynchronous calls with await
Use Pydantic models instead of standard dataclasses for data modeling
Use triple quotes (""") for all Python docstrings
Write docstrings in Google-style format
Include docstring sections when applicable: one-line summary, optional details, Args (without types), Returns, Raises, Examples
Validate and lint Python with ruff and mypy

Files:

• backend/tests/integration_docker/test_triggered_actions.py

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Cloudflare Pages

🔇 Additional comments (1)

backend/tests/integration_docker/test_triggered_actions.py (1)

88-88: Appropriate approach for investigating timing-related test flakiness.

Adding explicit retries=20 for repository synchronization is a reasonable strategy for Docker-based integration tests where external operations can be slower than expected. The retry count aligns with similar patterns elsewhere in the test (e.g., 30 retries in wait_until_automations_are_configured).

If this resolves the intermittent failures, consider whether the default retry count in the SDK's wait_for_sync_to_complete method should be increased or made more configurable.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codspeed-hq]

CodSpeed Performance Report

Merging #7529 will not alter performance

_{Comparing pog-triggered-actions (e27323c) with release-1.5 (128fa7b)}

Summary

✅ 10 untouched