Skip to content

Progress tracking

Progress tracking #46

Triggered via pull request September 12, 2025 13:42
Status Success
Total duration 3m 24s
Artifacts

main.yml

on: pull_request
Check coding standards
28s
Check coding standards
Matrix: Run tests
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Check coding standards
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>0RiPEaAAAAAA7usAXjSocQYNrKisxoxLcQ0hJMzBFREdFMDQxMQBFZGdl
Check coding standards
Failed to restore: Cache service responded with 400
Run tests (Ubuntu, 3.11)
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>01SPEaAAAAACkuaMTc/coQKElrvCY3UzXUEFPRURHRTA1MTUARWRnZQ==
Run tests (Ubuntu, 3.11)
Failed to restore: Cache service responded with 400
Run tests (Ubuntu, 3.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>01yPEaAAAAABLWlNA7XlUQJnFjqc38ehbRE0yRURHRTA3MDkARWRnZQ==
Run tests (Ubuntu, 3.10)
Failed to restore: Cache service responded with 400
Run tests (Ubuntu, 3.12)
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>03iPEaAAAAAAbumUbwfbXS441hcbo8gLrREVOMzAxMDAwMTA4MDM5AEVkZ2U=
Run tests (Ubuntu, 3.12)
Failed to restore: Cache service responded with 400
Run tests (Ubuntu, 3.13)
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>08iPEaAAAAAB9Z0Lw2MpdS42LWr3Al/F8QkwyQUEyMDMwMTA2MDI3AEVkZ2U=
Run tests (Ubuntu, 3.13)
Failed to restore: Cache service responded with 400