Skip to content
Weekly Integration Tests

Weekly Integration Tests #20

Sign in to view logs

Weekly Integration Tests

Weekly Integration Tests #20

Triggered via schedule February 2, 2026 00:37
@johanandrenjohanandren
⁠ 5843790
main
Status Failure
Total duration 6m 17s
Artifacts –

weekly.yml

on: schedule
Matrix: Compile and test
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 30 warnings
Compile and test (2.13, 1.21)
Mail command failed: 530-5.7.0 Authentication Required. For more information, go to 530 5.7.0 https://support.google.com/accounts/troubleshooter/2402620. a92af1059eb24-124a9debe5dsm18560530c88.11 - gsmtp
Compile and test (2.13, 1.21)
Process completed with exit code 1.
Compile and test (3.3, 1.17)
Mail command failed: 530-5.7.0 Authentication Required. For more information, go to 530 5.7.0 https://support.google.com/accounts/troubleshooter/2402620. 5614622812f47-45f08f73625sm8541327b6e.18 - gsmtp
Compile and test (3.3, 1.17)
Process completed with exit code 1.
Compile and test (2.13, 1.21)
Username and password not specified. You should only do this if you are using a self-hosted runner to access an on-premise mail server.
Compile and test (2.13, 1.21)
Failed to restore: Cache service responded with 400
Compile and test (2.13, 1.21)
Failed to restore: Cache service responded with 400
Compile and test (2.13, 1.25)
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>08vJ/aQAAAABk2qRcXlyvQrjwB1uH7DZhRE0yRURHRTAxMTIARWRnZQ==
Compile and test (2.13, 1.25)
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>08vJ/aQAAAABOd9sind1RTrE0heb18qo/RE0yRURHRTAxMTIARWRnZQ==
Compile and test (2.13, 1.25)
Failed to restore: Cache service responded with 400
Compile and test (2.13, 1.25)
Failed to restore: Cache service responded with 400
Compile and test (2.13, 1.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>09/J/aQAAAABctETO232YT4WWN9u3PHDKUEhYMzFFREdFMDYwOABFZGdl
Compile and test (2.13, 1.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>09vJ/aQAAAADmtR5nGRGnSZo+0eKherNIUEhYMzFFREdFMDYwOABFZGdl
Compile and test (2.13, 1.11)
Failed to restore: Cache service responded with 400
Compile and test (2.13, 1.11)
Failed to restore: Cache service responded with 400
Compile and test (3.3, 1.25)
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>0+fJ/aQAAAACDw86IgsWXSrVwCPiFCLUkUEhYMzFFREdFMDYwOQBFZGdl
Compile and test (3.3, 1.25)
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>0+PJ/aQAAAAB09eyJv9PqTJREGdBjug0zUEhYMzFFREdFMDYwOQBFZGdl
Compile and test (3.3, 1.25)
Failed to restore: Cache service responded with 400
Compile and test (3.3, 1.25)
Failed to restore: Cache service responded with 400
Compile and test (3.3, 1.17)
Username and password not specified. You should only do this if you are using a self-hosted runner to access an on-premise mail server.
Compile and test (3.3, 1.17)
Failed to restore: Cache service responded with 400
Compile and test (3.3, 1.17)
Failed to restore: Cache service responded with 400
Compile and test (2.13, 1.17)
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>0LvN/aQAAAAAgbWyoAuFTQ7Ge21FOlfmRUEhYMzFFREdFMDUxNwBFZGdl
Compile and test (2.13, 1.17)
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>0LfN/aQAAAAACc6pTdZYMQ4R91rNX+rOKUEhYMzFFREdFMDUxNwBFZGdl
Compile and test (2.13, 1.17)
Failed to restore: Cache service responded with 400
Compile and test (2.13, 1.17)
Failed to restore: Cache service responded with 400
Compile and test (3.3, 1.21)
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>0MfN/aQAAAADIVvl6syXbQLKMwx9nUV9jRE0yRURHRTA3MTAARWRnZQ==
Compile and test (3.3, 1.21)
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>0MfN/aQAAAABUrQbnZGzMSY7wVDhINUxuRE0yRURHRTA3MTAARWRnZQ==
Compile and test (3.3, 1.21)
Failed to restore: Cache service responded with 400
Compile and test (3.3, 1.21)
Failed to restore: Cache service responded with 400
Compile and test (3.3, 1.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>0TPN/aQAAAADffdizfBZRT4ekzCZNtcpfRE0yRURHRTA0MTgARWRnZQ==
Compile and test (3.3, 1.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>0TPN/aQAAAADMQf7XxCBVS76IBW6uQJsbRE0yRURHRTA0MTgARWRnZQ==
Compile and test (3.3, 1.11)
Failed to restore: Cache service responded with 400
Compile and test (3.3, 1.11)
Failed to restore: Cache service responded with 400