buildkit: GHA export cache fails with mode=max
With mode=max, export cache fails due to some blocking on the GitHub side (I assume?).
This is with buildkit 0.9.0
failed to parse error response 429: {“$id”:“1”,“innerException”:null,“message”:“Request was blocked due to exceeding usage of resource ‘Count’ in namespace ‘’.”,“typeName”:“Microsoft.TeamFoundation.Framework.Server.RequestBlockedException, Microsoft.TeamFoundation.Framework.Server”,“typeKey”:“RequestBlockedException”,“errorCode”:0,“eventId”:3000}: invalid character ‘ï’ looking for beginning of value
/cc @crazy-max
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 17 (7 by maintainers)
Commits related to this issue
- ci(web-server): limit workflow concurrency to avoid GHA rate limits There seems to be an issue currently where concurrent builds cause the Docker GHA cache exporter to trip over GitHub throttling lim... — committed to ntls-io/nautilus-wallet by PiDelport 3 years ago
- ci(web-server): limit workflow concurrency to avoid GHA rate limits There seems to be an issue currently where concurrent builds cause the Docker GHA cache exporter to trip over GitHub throttling lim... — committed to ntls-io/nautilus-wallet by PiDelport 3 years ago
- ci(web-server): limit workflow concurrency to avoid GHA rate limits There seems to be an issue currently where concurrent builds cause the Docker GHA cache exporter to trip over GitHub throttling lim... — committed to ntls-io/nautilus-wallet by PiDelport 3 years ago
- ci(web-server): limit workflow concurrency to avoid GHA rate limits There seems to be an issue currently where concurrent builds cause the Docker GHA cache exporter to trip over GitHub throttling lim... — committed to ntls-io/nautilus-wallet by PiDelport 3 years ago
- ci(web-server): limit workflow concurrency to avoid GHA rate limits There seems to be an issue currently where concurrent builds cause the Docker GHA cache exporter to trip over GitHub throttling lim... — committed to ntls-io/nautilus-wallet by PiDelport 3 years ago
- feat: use gha cache exporter when building via buildkit Buildkit builds expose custom cache exporters which can be used to locally speed up builds on Github Actions. The gha cacher will use the Githu... — committed to porter-dev/porter by jose-fully-ported 7 months ago
- feat: use gha cache exporter when building via buildkit Buildkit builds expose custom cache exporters which can be used to locally speed up builds on Github Actions. The gha cacher will use the Githu... — committed to porter-dev/porter by jose-fully-ported 7 months ago
- feat: use gha cache exporter when building via buildkit Buildkit builds expose custom cache exporters which can be used to locally speed up builds on Github Actions. The gha cacher will use the Githu... — committed to porter-dev/porter by jose-fully-ported 7 months ago
fixed the bom part in https://github.com/tonistiigi/go-actions-cache/pull/6 in our side
@lucacome Thanks! I’ll take an in-depth look tomorrow, but it certainly seems like the multiple build jobs targeting different OS’es + each job creating multiple caches is hitting the throttling limits.
@tonistiigi Is there a separate issue here with how the client is handling the response from the cache server? Specifically with the
invalid character 'ï' looking for beginning of valuemessage? Should it retry or treat this as a cache-miss?