Cache Stuck

Describe the bug
All my actions are running, but are refusing to cache with the same error:

Post job cleanup.
Unable to reserve cache with key Linux-modules-0c1e633988f0463573ae79cec4e4e741153037a6a270a901c8bf040b3d674a4f, another job may be creating this cache.

There must be some sort of race condition, and the cache is stuck, because they all have the same precache log:

Run actions/cache@v2
  with:
    path: **/node_modules
    key: Linux-modules-0c1e633988f0463573ae79cec4e4e741153037a6a270a901c8bf040b3d674a4f
Cache not found for input keys: Linux-modules-0c1e633988f0463573ae79cec4e4e741153037a6a270a901c8bf040b3d674a4f

I imagine that if I changed my yarn lock file, which the cache is based on, this issue would resolve itself.

Expected behavior
That the cache always works, and when it gets stuck like this, it would automatically fix itself.

Additional context

• My github runner is running inside a docker container. Not deferring to a docker container, but are running inside a container where the runner is installed. I don't think this impacts things as my cache normally works.
• I don't know how to reproduce this. Normally the cache works. There just is clearly some sort of race condition where it can get stuck.

No source file or test is named. Start with the actions/cache@v2 logs and the repeated cache key, then investigate how cache reservation behaves when multiple jobs miss the same key. Done means the cache no longer remains stuck after a reservation race and recovers automatically.