From 4059ccf863909a777932f6d8f2e937a2bf97b7bb Mon Sep 17 00:00:00 2001 From: Patric Stout Date: Fri, 8 Jan 2021 15:20:27 +0100 Subject: Fix: [Actions] circumvent Windows tar warning about read-only files (#8524) Because certain files are read-only, the "restore-cache" step fails, as Windows tar refuses to overwrite those files (even if they are identical). Instead of hoping upstream fixes "restore-cache", just remove the read-only flag on these files instead. --- .github/workflows/ci-build.yml | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to '.github') diff --git a/.github/workflows/ci-build.yml b/.github/workflows/ci-build.yml index 08f3a7a19..8b9a160d9 100644 --- a/.github/workflows/ci-build.yml +++ b/.github/workflows/ci-build.yml @@ -220,6 +220,18 @@ jobs: - name: Checkout uses: actions/checkout@v2 + # "restore-cache" which is done by "run-vcpkg" uses Windows tar. + # A git clone on windows marks a few files as read-only; when Windows tar + # tries to extract the cache over this folder, it fails, despite the files + # being identical. This failure shows up as an warning in the logs. We + # avoid this by simply removing the read-only mark from the git folder. + # In other words: this is a hack! + # See: https://github.com/lukka/run-vcpkg/issues/61 + - name: Remove read-only flag from vcpkg git folder + shell: powershell + run: | + attrib -r "c:\vcpkg\.git\*.*" /s + - name: Prepare vcpkg (with cache) uses: lukka/run-vcpkg@v6 with: -- cgit v1.2.3-54-g00ecf