Tests: initialize all resources and then call vshard.storage.cfg to avoid flaky test #240
Triggered via pull request
September 11, 2025 21:37
nurzhan-saktaganov
Status
Failure
Total duration
3m 11s
Artifacts
–
Annotations
6 errors and 8 warnings
|
all-tests (1.22, master)
Process completed with exit code 2.
|
|
all-tests (stable, master)
Process completed with exit code 2.
|
|
all-tests (1.22, 2.10)
Process completed with exit code 2.
|
|
all-tests (stable, 2.10)
Process completed with exit code 2.
|
|
all-tests (1.22, 2.8)
Process completed with exit code 2.
|
|
all-tests (stable, 2.8)
Process completed with exit code 2.
|
|
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>0XkHDaAAAAACuPC6bnKNSQqikkvnfWAdHQ0hJMzBFREdFMDQxNQBFZGdl
|
|
all-tests (1.22, 2.10)
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>0Y0HDaAAAAAB88pq8nPT2QIawrtsyoj5IQlkzRURHRTAyMDkARWRnZQ==
|
|
all-tests (stable, 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>0c0HDaAAAAACPsDPrRRizQo3/kA/+mocKQlkzRURHRTAzMDkARWRnZQ==
|
|
all-tests (1.22, 2.8)
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>0fkHDaAAAAABf7MrOV6abQ5rw0Wbmsf/fQkwyQUEyMDMwMTEwMDMxAEVkZ2U=
|
|
all-tests (stable, 2.8)
Failed to restore: Cache service responded with 400
|