Skip to content
Run tests

v1.0.0 #13

Sign in to view logs

v1.0.0

v1.0.0 #13

Triggered via pull request January 27, 2026 00:06
@aaTmanaaTman
synchronize #325
develop
Status Success
Total duration 4m 32s
Artifacts –

run-tests.yaml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
build (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>0NgJ4aQAAAACW74aVYGZvQpZkY41myHfnUEhMMzBFREdFMDExMwBFZGdl
build (3.13)
Failed to restore: Cache service responded with 400
build (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>0QwJ4aQAAAACwnIwK+C69TqTrpWl+bRo1Q0hHRURHRTE3MDcARWRnZQ==
build (3.12)
Failed to restore: Cache service responded with 400
build (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>0WQJ4aQAAAAAw55icpPm9RpwgUIscA5KAUEFPRURHRTA2MTMARWRnZQ==
build (3.11)
Failed to restore: Cache service responded with 400
build (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>0egJ4aQAAAADkZDSVgOVATbwrQN2E0CZWUEFPRURHRTA1MTQARWRnZQ==
build (3.10)
Failed to restore: Cache service responded with 400