fix(ci): pass ACTIONS_CACHE_SERVICE_V2 into Docker for sccache v2 cache API#325
Merged
DorianZheng merged 1 commit intomainfrom Mar 2, 2026
Merged
fix(ci): pass ACTIONS_CACHE_SERVICE_V2 into Docker for sccache v2 cache API#325DorianZheng merged 1 commit intomainfrom
DorianZheng merged 1 commit intomainfrom
Conversation
…he API sccache inside Docker containers was failing to write cache entries (1790/1790 write errors) because it defaulted to the legacy v1 GHA cache API, which GitHub sunset in April 2025. The host worked fine because sccache-action sets ACTIONS_CACHE_SERVICE_V2=on, but this env var was not forwarded into Docker containers. Add ACTIONS_CACHE_SERVICE_V2 to: - Docker -e flags in build-runtime, build-node, warm-caches - environment-pass in pyproject.toml for cibuildwheel - github-script exports in all four workflows
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ACTIONS_CACHE_SERVICE_V2env varsccache-actionsets this var, but it wasn't forwarded into DockerRoot cause
mozilla-actions/[email protected]setsACTIONS_CACHE_SERVICE_V2=onon the host. OpenDAL (sccache's storage backend) checks this env var to choose between v1/v2 cache API. Without it, Docker containers fell back to the dead v1 API — confirmed by the cache name difference: host used a SHA256 hash (v2), Docker usedsccache-v0.14.0(v1).Changes
Added
ACTIONS_CACHE_SERVICE_V2to:-eflags inbuild-runtime.yml,build-node.yml,warm-caches.ymlenvironment-passinpyproject.tomlfor cibuildwheelgithub-scriptexports in all four workflowsTest plan
Warm Cachesworkflow shows cache writes succeeding (0 write errors)Build Runtimeworkflow gets cache hits from warm cache