Skip to content
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

CI times out on satackey/action-docker-layer-caching step #1834

Closed
RyanGlScott opened this issue Mar 6, 2023 · 2 comments
Closed

CI times out on satackey/action-docker-layer-caching step #1834

RyanGlScott opened this issue Mar 6, 2023 · 2 comments
Assignees
Labels
tooling: CI Issues involving CI/CD scripts or processes

Comments

@RyanGlScott
Copy link
Contributor

Recently, CI builds of saw-script (both PRs and nightly builds) are consistently timing out on the satackey/action-docker-layer-caching step, even for normally quick-running jobs such as the drbg job (example). While I am unclear on the exact cause of this, I do note that this action is deprecated and unmaintained, and modern development appears to have switched over to this fork. As a first step, we should switch over to the modern fork to see if that resolves the issue.

@RyanGlScott RyanGlScott added the tooling: CI Issues involving CI/CD scripts or processes label Mar 6, 2023
@RyanGlScott RyanGlScott self-assigned this Mar 6, 2023
@RyanGlScott
Copy link
Contributor Author

Fixed in #1835.

@RyanGlScott
Copy link
Contributor Author

Sadly, even the newly forked version still appears to time out, and it has been doing so consistently as of the last week or so. See this workflow, for example, where all of the Docker-related jobs time out on the action-docker-layer-caching step. Unfortunately, I'm really not sure what to do about this, as I'm unclear if there is an alternative that works reliably. We may just have to disable Docker layer caching altogether.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tooling: CI Issues involving CI/CD scripts or processes
Projects
None yet
Development

No branches or pull requests

1 participant