api: TRANSFER_IN_PROGRESS error shoud be retryable #233
Triggered via pull request
September 10, 2025 18:48
nurzhan-saktaganov
Status
Failure
Total duration
9m 54s
Artifacts
–
Annotations
1 error and 8 warnings
|
all-tests (1.22, master)
Process completed with exit code 1.
|
|
all-tests (1.22, 2.10)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0UcjBaAAAAABWt6z18q4WSJrOElDZ2WJSRE0yRURHRTA3MTUARWRnZQ==
|
|
all-tests (1.22, 2.10)
Failed to restore: Cache service responded with 400
|
|
all-tests (1.22, 2.8)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0W8jBaAAAAABEHGS+6dqrT7vGC1SHNHbbQkwyQUEyMDMwMTEwMDE5AEVkZ2U=
|
|
all-tests (1.22, 2.8)
Failed to restore: Cache service responded with 400
|
|
all-tests (stable, 2.10)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0W8jBaAAAAABodEkxAz7VTJiepQWOaBc5QlkzRURHRTA0MTQARWRnZQ==
|
|
all-tests (stable, 2.10)
Failed to restore: Cache service responded with 400
|
|
all-tests (stable, 2.8)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ZMjBaAAAAADNRZjJDbW2RIACm3wDQLrgUEhYMzFFREdFMDIwOQBFZGdl
|
|
all-tests (stable, 2.8)
Failed to restore: Cache service responded with 400
|