workflows/integration-test: fix Go cache architecture-specific restoration #41173
Conversation
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
…ation
Prevent GitHub runners from different architectures from restoring cache
from other architectures. Cross-architecture cache restoration causes both
amd64 and arm64 build artifacts to be loaded on a single runner, leading
to disk space exhaustion with errors like:
compile: writing output: write $WORK/b3076/_pkg_.a: no space left on device
github.com/aliyun/alibaba-cloud-sdk-go/sdk/internal: mkdir /tmp/go-build2367015974/b3083/: no space left on device
This occurred because cache cleanup happens on schedule, and during cache
recreation, the arm64 runner would pick up the amd64 cache (or vice versa),
resulting in "no space left on device" errors when trying to build for
one of architectures on the same runner using both caches.
The fix ensures each architecture maintains its own isolated cache space
by including the runner architecture in the cache key.
Fixes: 86061ff (".github/{integration,conformance}: use caches to speed up compilation")
Signed-off-by: André Martins <andre@cilium.io>
|
/test |
sayboras
approved these changes
Aug 15, 2025
brlbil
approved these changes
Aug 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prevent GitHub runners from different architectures from restoring cache from other architectures. Cross-architecture cache restoration causes both amd64 and arm64 build artifacts to be loaded on a single runner, leading to disk space exhaustion with errors like:
This occurred because cache cleanup happens on schedule, and during cache recreation, the arm64 runner would pick up the amd64 cache (or vice versa), resulting in "no space left on device" errors when trying to build for one of architectures on the same runner using both caches.
The fix ensures each architecture maintains its own isolated cache space by including the runner architecture in the cache key.
Fixes: 86061ff (".github/{integration,conformance}: use caches to speed up compilation")
Fixes: #41157