Increase timeouts for actions that rely on actions (again) #289
Conversation
This file contains 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
In buildpacks#214 the timeouts for Actions that rely on other Actions was bumped from 2 minutes to 8 minutes. However, there are still occasionally instances where the registry request issue isn't processed for up to 15-16 minutes due to delays in the GitHub Actions runner being started. As such this raises the timeout again, from 8 minutes to 20 minutes. Signed-off-by: Ed Morley <501702+edmorley@users.noreply.github.com>
jkutner
approved these changes
Jul 8, 2024
jkutner
added
type:task
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.
In #214 the timeouts for Actions that rely on other Actions was bumped from 2 minutes to 8 minutes.
However, there are still occasionally instances where the registry request issue isn't processed for up to 15-16 minutes due to delays in the GitHub Actions runner being started.
This results in failures on the upstream job, eg:
https://github.com/heroku/buildpacks-nodejs/actions/runs/9781380433/job/27005632116
https://github.com/heroku/buildpacks-procfile/actions/runs/9763056515/job/26948174660
For example in the last ~month the following all exceeded the 8 minute timeout:
As such this raises the timeout again, from 8 minutes to 20 minutes.