How to avoid “chmod .venv/bin/python: no such file or directory” warning when restoring

GitLab CI/CD
1

While scouring jobs on a new project for any warnings I ran into this on gitlab.com :

 Restoring cache
Checking cache for lint...
Downloading cache.zip from https://storage.googleapis.com/gitlab-com-runners-cache/project/22614446/lint 
WARNING: .venv/bin/python: chmod .venv/bin/python: no such file or directory (suppressing repeats) 
Successfully extracted cache

Am I using the cache wrongly somehow? My configuration:

---
image: python:3.9
…
cache:
  key: "$CI_COMMIT_REF_SLUG"
  paths:
    - .cache
    - .venv

A quick search reveals that tons of other projects are seeing the same warning in their job output. Is there something I can do to avoid it, even if it might be harmless?