Skip to content

replace deprecated Lwt_unix.run with recommended Lwt_main.run #28

replace deprecated Lwt_unix.run with recommended Lwt_main.run

replace deprecated Lwt_unix.run with recommended Lwt_main.run #28

Triggered via push September 10, 2025 14:27
Status Failure
Total duration 22m 53s
Artifacts

ci.yml

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

Annotations

4 errors, 40 warnings, and 5 notices
build (windows-latest, 4.10.x, v2)
Process completed with exit code 1.
build (windows-latest, 4.08.x, v2)
Process completed with exit code 1.
build (windows-latest, 4.12.x, v2)
Process completed with exit code 1.
build (windows-latest, 4.14.x, v2)
Process completed with exit code 1.
build (windows-latest, 4.10.x, v2)
Failed to restore: Cache service responded with 400
build (windows-latest, 4.10.x, v2)
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>0l4vBaAAAAADZ1Q8C6zJCTI1YRmqp8AucQkwyQUEyMDMwMTA3MDIxAEVkZ2U=
build (windows-latest, 4.10.x, v2)
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>0MIvBaAAAAABXECRushlMR6o6qvU9jIf3QkwyQUEyMDMwMTA1MDM3AEVkZ2U=
build (windows-latest, 4.10.x, v2)
Failed to restore: Cache service responded with 400
build (windows-latest, 4.10.x, v2)
Failed to restore: Cache service responded with 400
build (windows-latest, 4.08.x, v2)
Failed to restore: Cache service responded with 400
build (windows-latest, 4.08.x, v2)
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>0mIvBaAAAAACjSBnL0WaWS41gUchtFMMxUEhYMzFFREdFMDYxNgBFZGdl
build (windows-latest, 4.08.x, v2)
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>0KYvBaAAAAAAjeGsgu8zRRJKshS6ZRXOxUEhYMzFFREdFMDIxNgBFZGdl
build (windows-latest, 4.08.x, v2)
Failed to restore: Cache service responded with 400
build (windows-latest, 4.08.x, v2)
Failed to restore: Cache service responded with 400
build (windows-latest, 4.12.x, v2)
Failed to restore: Cache service responded with 400
build (windows-latest, 4.12.x, v2)
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>0oIvBaAAAAADrSv3BPt2UQZuetA7pEXj4QkwyQUEyMDMwMTA4MDMxAEVkZ2U=
build (windows-latest, 4.12.x, v2)
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>0N4vBaAAAAADMd+YYwHMnSLqg8+gsdXU2QkwyQUEyMDMwMTA3MDIzAEVkZ2U=
build (windows-latest, 4.12.x, v2)
Failed to restore: Cache service responded with 400
build (windows-latest, 4.12.x, v2)
Failed to restore: Cache service responded with 400
build (macos-13, 4.08.x, v2)
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>0TI3BaAAAAABtiOZ475mdTL4ZWN8VXfhJU04xRURHRTIzMjIARWRnZQ==
build (macos-13, 4.08.x, v2)
Failed to restore: Cache service responded with 400
build (macos-13, 4.08.x, v2)
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>0lozBaAAAAADVM70HSjjDTIVn4Y21XqzHU04xRURHRTIxMTcARWRnZQ==
build (macos-13, 4.08.x, v2)
Failed to restore: Cache service responded with 400
build (windows-latest, 4.14.x, v2)
Failed to restore: Cache service responded with 400
build (windows-latest, 4.14.x, v2)
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>07IzBaAAAAAAC9gpCVFkhTLrUvayP8+uuUEFPRURHRTA1MTgARWRnZQ==
build (windows-latest, 4.14.x, v2)
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>0HYvBaAAAAACWnAcGtCcGSoCvteBY1sqJUEFPRURHRTA1MjIARWRnZQ==
build (windows-latest, 4.14.x, v2)
Failed to restore: Cache service responded with 400
build (windows-latest, 4.14.x, v2)
Failed to restore: Cache service responded with 400
build (macos-13, 4.14.x, v2)
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>0ro3BaAAAAACXoKDBK4LERJIZLvYthB4WQkwyQUEyMDMwMTA2MDUzAEVkZ2U=
build (macos-13, 4.14.x, v2)
Failed to restore: Cache service responded with 400
build (macos-13, 4.14.x, v2)
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>0iozBaAAAAAAUPxf1d8bKTLUW/JB7uj46QkwyQUEyMDMwMTA1MDI3AEVkZ2U=
build (macos-13, 4.14.x, v2)
Failed to restore: Cache service responded with 400
build (macos-13, 5.02.x, v2)
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>0Y47BaAAAAAA4PZRK/oOVQb2vdpPn0IvkU04xRURHRTE4MTQARWRnZQ==
build (macos-13, 5.02.x, v2)
Failed to restore: Cache service responded with 400
build (macos-13, 5.02.x, v2)
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>0RY3BaAAAAAA14kgvqiS3SInCJVHMUr5nU04xRURHRTE2MjIARWRnZQ==
build (macos-13, 5.02.x, v2)
Failed to restore: Cache service responded with 400
build (macos-13, 4.12.x, v2)
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>0b47BaAAAAAB12TzcQ535TK3ZbZq0J61DQkwyQUEyMDMwMTA5MDM3AEVkZ2U=
build (macos-13, 4.12.x, v2)
Failed to restore: Cache service responded with 400
build (macos-13, 4.12.x, v2)
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>0Mo3BaAAAAAAEef1CJd6dT5jQ6r8x6l2XQkwyQUEyMDMwMTA2MDAzAEVkZ2U=
build (macos-13, 4.12.x, v2)
Failed to restore: Cache service responded with 400
build (macos-13, 4.10.x, v2)
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>0s47BaAAAAAAD/sb5YlGESqZPgJmtRYLnU04xRURHRTIwMTcARWRnZQ==
build (macos-13, 4.10.x, v2)
Failed to restore: Cache service responded with 400
build (macos-13, 4.10.x, v2)
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>0bI3BaAAAAABQq6ZvLtHFSKi2/EZkiBDnU04xRURHRTIxMTUARWRnZQ==
build (macos-13, 4.10.x, v2)
Failed to restore: Cache service responded with 400
build (windows-latest, 4.10.x, v2)
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
build (windows-latest, 4.08.x, v2)
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
build (windows-latest, 4.12.x, v2)
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
build (windows-latest, 4.14.x, v2)
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
build (windows-latest, 5.02.x, v3)
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