Skip to content

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

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

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

check.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
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>0RUHDaAAAAACejp5DsuBdQY54JNL8laI7UEFPRURHRTA2MTUARWRnZQ==
luacheck
Failed to restore: Cache service responded with 400
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>0a0HDaAAAAACx6M7VhHgqTIxl4IbxDqTcREVOMzAxMDAwMTAyMDI3AEVkZ2U=
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>0aEHDaAAAAADFeTMELjvbRrE4bMJkzFG1REVOMzAxMDAwMTA1MDQ1AEVkZ2U=
golangci-lint
Failed to restore: Cache service responded with 400
golangci-lint
Failed to restore: Cache service responded with 400