Skip to content

[OMCProcessDocker*] update exception message - make them specific to … #578

[OMCProcessDocker*] update exception message - make them specific to …

[OMCProcessDocker*] update exception message - make them specific to … #578

Triggered via push August 19, 2025 13:18
Status Success
Total duration 12m 2s
Artifacts

Test.yml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings and 2 notices
test (3.12, windows-latest, stable)
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>0K3qkaAAAAAA0yCRiiZzMTbkRm52qdgN7QkwyQUEyMDMwMTA3MDExAEVkZ2U=
test (3.12, windows-latest, stable)
Failed to restore: Cache service responded with 400
test (3.10, windows-latest, stable)
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>0RnqkaAAAAAAAP2F7YvZrSrZOghqpW4VpRE0yRURHRTA3MjAARWRnZQ==
test (3.10, windows-latest, stable)
Failed to restore: Cache service responded with 400
test (3.12, windows-latest, stable)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
test (3.10, windows-latest, stable)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677