Skip to content

Tests: initialize all resources and then call vshard.storage.cfg to avoid flaky test #241

Tests: initialize all resources and then call vshard.storage.cfg to avoid flaky test

Tests: initialize all resources and then call vshard.storage.cfg to avoid flaky test #241

Triggered via pull request September 11, 2025 21:38
Status Success
Total duration 1m 18s
Artifacts

check.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
golangci-lint
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>0r0HDaAAAAADMIPVPQWeFR61UqCRtXPt+QkwyQUEyMDMwMTA3MDAzAEVkZ2U=
golangci-lint
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>0rEHDaAAAAAC6MHhVEgaTSLhIpehtfgY1QkwyQUEyMDMwMTA5MDUzAEVkZ2U=
golangci-lint
Failed to restore: Cache service responded with 400
golangci-lint
Failed to restore: Cache service responded with 400
luacheck
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>0lUHDaAAAAABHPkKZvONxQLn5i7x++q0nQkwyQUEyMDMwMTA1MDM3AEVkZ2U=
luacheck
Failed to restore: Cache service responded with 400