Unable to reserve cache with key X another job may be creating this cache

[ruudk]

Describe the bug
Since today our workflows started failing 80% of the time.

Version

• Latest version

Runners

• GitHub Hosted

Operating systems

• Ubuntu 20.04

PHP versions

• 8.0

To Reproduce

env:
    REQUIRED_PHP_TOOLS: cs2pr
    REQUIRED_PHP_EXTENSIONS: mbstring,bcmath,intl,gd,zip,memcached,redis,rdkafka
    PHP_VERSION: '8.0'
jobs:
    checks-and-guards:
        strategy:
            fail-fast: false
        runs-on: ubuntu-20.04
        steps:
            -   name: Checkout
                uses: actions/checkout@v2.4.0
                with:
                    ref: ${{ github.event.pull_request.head.sha }}
                    fetch-depth: 0
            -   name: Setup cache environment
                id: extcache
                uses: shivammathur/cache-extensions@1.6.2
                with:
                    php-version: ${{ env.PHP_VERSION }}
                    extensions: ${{ env.REQUIRED_PHP_EXTENSIONS }}
                    key: php-build-v1

Expected behavior
No error

Additional context
Feels like a race condition similar to ramsey/composer-install#195

[shivammathur]

@ruudk try bumping the key input in cache-extensions

[ruudk]

Does not make a difference :(

[shivammathur]

Can you provide links to the workflow runs

[ruudk]

They are in private repos so I cannot share them. For now, I removed the caching of extensions and it works fine.

if more people report this, it might be related to cache race conditions mentioned above.

[shivammathur]

The "Unable to reserve cache ..." error is not because of a race condition, but a known issue when something breaks between reserving the cache and the final upload in the post cache step. Because of this failure, the cache gets stuck in a reserved state and new runs are not able to use that cache key again. So resetting the key should have fixed it.
This comment on actions/cache explains it.

I released 1.7.0 of this action today and that should reset every cache. Whenever you have time please try running it again in a public test repo and let me know if you still get that error.

[ruudk]

Thank you for the followup. I just enabled the actions on my private repo again. Let's see how it goes. If you don't hear from me after a week, all should be fixed 😊

[angrybrad]

Running into this myself.

Have tried various things like changing the extension list, updating cache keys, creating dynamic cache keys from the build matrix, etc. with no luck.

Can't help but think I'm doing something wrong, but not sure what.

https://github.com/craftcms/cms/runs/5635773446

[shivammathur]

@angrybrad

This can happen when a cache is reserved but not saved for some reason. Now that key cannot be used again till 24hrs till that reserved lock is released.

I improved how we handle cache errors in 257e3c9. So try again and let me know. Also, you don't need to set dynamic keys, a simple string would work, the action will parameterize it as needed.

[angrybrad]

@shivammathur So far that appears to have resolved the issue. I will report back if it comes up again. Thank you!