Skip to content
Rust

Fetch clock later to avoid sync issues when the reserve is refreshed - do not bail when clock is behind #5

Sign in to view logs

Fetch clock later to avoid sync issues when the reserve is refreshed - do not bail when clock is behind

Fetch clock later to avoid sync issues when the reserve is refreshed - do not bail when clock is behind #5

Triggered via pull request September 16, 2024 11:32
@elliotkennedyelliotkennedy
synchronize #1
elliot/clock-fetch
Status Failure
Total duration 42s
Artifacts –

rust.yml

on: pull_request
rust_fmt_and_test
31s
rust_fmt_and_test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
rust_fmt_and_test
The process '/home/runner/.cargo/bin/cargo' failed with exit code 1
rust_fmt_and_test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
rust_fmt_and_test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/