ci: run goreleaser without the runner's GOCACHEPROG
schemas / vulnerabilities (pull_request) Successful in 3m32s
schemas / check (pull_request) Successful in 5m5s
schemas / check-release (pull_request) Successful in 5m12s
pre-commit / pre-commit (pull_request) Failing after 11m14s
schemas / build (pull_request) Successful in 15m19s
schemas / deploy-prod (pull_request) Skipped
schemas / vulnerabilities (pull_request) Successful in 3m32s
schemas / check (pull_request) Successful in 5m5s
schemas / check-release (pull_request) Successful in 5m12s
pre-commit / pre-commit (pull_request) Failing after 11m14s
schemas / build (pull_request) Successful in 15m19s
schemas / deploy-prod (pull_request) Skipped
goreleaser runs several go builds at once; each spawns its own gobuildcache,
and they time out on its per-entry file locks while one holds the lock
across a slow S3 call ('failed to acquire lock: context deadline exceeded',
check-release on #997). Use Go's local cache for goreleaser.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ma8eHhW59hLAJuLzBnLvUu
This commit is contained in:
1 parent
00160e172d
commit
3921de91a6
2 files changed
+8
-3
No files matched your search
@@ -27,4 +27,5 @@ jobs:
|
||||
run: |
|
||||
GITEA_TOKEN=$(cat "${RELEASE_TOKEN_FILE}")
|
||||
export GITEA_TOKEN
|
||||
goreleaser release --clean
|
||||
# Without GOCACHEPROG: parallel builds contend for gobuildcache's locks.
|
||||
env -u GOCACHEPROG goreleaser release --clean
|
||||
Reference in new issue
Block a user