The eval-server side of the index cache is gone, but the docker harness
still carried the producer half: every container setup ran
_restore_or_skip_cache, which resolved a cache key, mkdir'd
/root/.gortex-cache and put_archive'd index.tar.gz into it, then logged
"Cached index restored". Nothing inside the container ever read that
tarball, so each eval instance paid the copy and emitted a cache-hit line
that did not correspond to a cache hit.
Remove the whole plumbing: the restore call and its method, _make_cache_key,
DEFAULT_CACHE_DIR, the cache_dir constructor parameter, _get_repo_identity
(its only caller was the restore path), the run_eval pass-through of
env_cfg["cache_dir"], and the cache-key/cache_dir assertions in the eval
tests. The module docstring no longer promises to mount cached indexes.
Andrey Kumanyaev
dbc0feffe6