Skip to content
CI

cmd error parsing: show a "try again after" message when a response sets a Retry-After header #430

Sign in to view logs

cmd error parsing: show a "try again after" message when a response sets a Retry-After header

cmd error parsing: show a "try again after" message when a response sets a Retry-After header #430

Triggered via pull request June 19, 2025 04:59
@IsaacGIsaacG
opened #1198
IsaacG:retry_after.error_output
Status Success
Total duration 1m 49s
Artifacts –

ci.yml

on: pull_request
Go Format
4s
Go Format
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
Go 1.21.x - ubuntu-latest
Failed to save: reserveCache failed: Cache service responded with 503
Go 1.21.x - ubuntu-latest
Failed to restore: getCacheEntry failed: Cache service responded with 503
Go 1.20.x - ubuntu-latest
Failed to save: reserveCache failed: Cache service responded with 503
Go 1.20.x - ubuntu-latest
Failed to restore: getCacheEntry failed: Cache service responded with 503
Go 1.20.x - macOS-latest
Failed to save: reserveCache failed: Cache service responded with 503
Go 1.20.x - macOS-latest
Failed to restore: getCacheEntry failed: Cache service responded with 503
Go 1.21.x - macOS-latest
Failed to save: reserveCache failed: Cache service responded with 503
Go 1.21.x - macOS-latest
Failed to restore: getCacheEntry failed: Cache service responded with 503
Go 1.20.x - windows-latest
Failed to save: reserveCache failed: Cache service responded with 503
Go 1.20.x - windows-latest
Failed to restore: getCacheEntry failed: Cache service responded with 503
Go 1.21.x - windows-latest
Failed to save: reserveCache failed: Cache service responded with 503
Go 1.21.x - windows-latest
Failed to restore: getCacheEntry failed: Cache service responded with 503