Skip to content

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

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 #242

Triggered via pull request September 11, 2025 21:50
Status Success
Total duration 1m 21s
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>0ikTDaAAAAADDdpNgqjK6T6XltNNAl1STQ0hJMzBFREdFMDExOABFZGdl
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>0h0TDaAAAAABlnG/hQe8oQa6RLZ9GegBvQ0hJMzBFREdFMDIxNgBFZGdl
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>0bETDaAAAAAD+H2qmANkJSZ4kWhqpXf3nRE0yRURHRTA3MTYARWRnZQ==
luacheck
Failed to restore: Cache service responded with 400