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.

Sign up for GitHub

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

Jump to bottom

Cache failures shouldn't kill the jobs #26

Open
ManasJayanth opened this issue Jul 19, 2024 · 0 comments
Open

Cache failures shouldn't kill the jobs #26

ManasJayanth opened this issue Jul 19, 2024 · 0 comments

Comments

@ManasJayanth
Copy link
Member

Along with #13 , cache failures such as

Error: Unable to reserve cache with key build-darwin-arm64-6e54f555c98a94353c6fe600c1d2a2acb4b678152cb3960d58ae5ccec69c382d-20240515-1, another job may be creating this cache.

ref

.. should not stop other jobs from proceeding. Cache restores are after all optional. They should notify the user, however.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ManasJayanth