hardcoresushi
/
libcryfs
1
0
Fork 0
Code Issues Pull Requests Releases Activity

Don't fail a CI run if the cache download fails

This commit is contained in:
Sebastian Meßmer 2021-04-25 13:01:43 -07:00 committed by GitHub
parent 5c28675ec0
commit c90909013e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.github/workflows/main.yaml vendored
View File

@ -231,6 +231,8 @@ jobs:
echo "::set-output name=pip_cache_dir::$(python3 -m pip cache dir)"
shell: bash
- name: Retrieve pip cache
# Sometimes, the cache can get corrupted and the download fails with a checksum error. Let's not fail the CI job but continue it, later on this job will upload a new fixed cache as part of the regular job run.
continue-on-error: true
# We're using an S3 based cache because the standard GitHub Action cache (actions/cache) only gives us 5GB of storage and we need more
uses: leroy-merlin-br/action-s3-cache@8d75079437b388688b9ea9c7d73dff4ef975c5fa # v1.0.5
with:
@ -284,6 +286,8 @@ jobs:
rm /tmp/hash_flags
shell: bash
- name: Retrieve ccache cache
# Sometimes, the cache can get corrupted and the download fails with a checksum error. Let's not fail the CI job but continue it, later on this job will upload a new fixed cache as part of the regular job run.
continue-on-error: true
# We're using an S3 based cache because the standard GitHub Action cache (actions/cache) only gives us 5GB of storage and we need more
uses: leroy-merlin-br/action-s3-cache@8d75079437b388688b9ea9c7d73dff4ef975c5fa # v1.0.5
with:
@ -301,6 +305,8 @@ jobs:
ccache -s
# TODO Ideally, the Setup conan cache step would be part of the build action, but Github doesn't support nested actions yet, see https://github.com/actions/runner/issues/862
- name: Retrieve conan cache
# Sometimes, the cache can get corrupted and the download fails with a checksum error. Let's not fail the CI job but continue it, later on this job will upload a new fixed cache as part of the regular job run.
continue-on-error: true
# We're using an S3 based cache because the standard GitHub Action cache (actions/cache) only gives us 5GB of storage and we need more
uses: leroy-merlin-br/action-s3-cache@8d75079437b388688b9ea9c7d73dff4ef975c5fa # v1.0.5
with: