CI: Add better/longer retries to AIO workflow TF #1939
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
Member
Author
|
The one time I want to test a CI failure, every AIO works perfectly first time 🙃 |
Alex-Welsh
force-pushed
the
better-aio-retries
branch
from
b2ecf4f to
c5fc4fa
Compare
priteau
requested changes
Oct 22, 2025
Alex-Welsh
force-pushed
the
better-aio-retries
branch
from
c5fc4fa to
6ba3f40
Compare
Alex-Welsh
force-pushed
the
better-aio-retries
branch
from
6ba3f40 to
62e53e0
Compare
Alex-Welsh
had a problem deploying
to
Leafcloud
GitHub Actions
Failure
Alex-Welsh
had a problem deploying
to
Leafcloud
GitHub Actions
Failure
priteau
approved these changes
Oct 23, 2025
Member
priteau
left a comment
priteau
left a comment
There was a problem hiding this comment.
The jump from 60-180 seconds to 7200 is huge (an exponential backoff is more conventional), but let's see how it works. We can keep tuning it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the terraform apply would just run 5 times. If it failed, it would wait 60 seconds.
All AIOs are triggered at the same time, so might conflict.
Now, it runs 6 times. After 3 attempts, wait for 2 hours (the cloud is probably at capacity, waits for other jobs to finish)
Normal waits are randomised from 1 to 3 minutes