Skip to content

fix: Make StdClock monotonic using std::time::Instant #16294

fix: Make StdClock monotonic using std::time::Instant

fix: Make StdClock monotonic using std::time::Instant #16294

Triggered via pull request March 14, 2026 22:32
Status Cancelled
Total duration 11m 53s
Artifacts

rust.yml

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

Annotations

10 errors and 1 warning
Documentation
Process completed with exit code 101.
Test (windows-latest)
Canceling since a higher priority waiting request for Continuous integration-4841 exists
Test (windows-latest)
The operation was canceled.
Lint
Canceling since a higher priority waiting request for Continuous integration-4841 exists
Lint
The operation was canceled.
Build & run examples
Canceling since a higher priority waiting request for Continuous integration-4841 exists
Build & run examples
The operation was canceled.
Coverage
Canceling since a higher priority waiting request for Continuous integration-4841 exists
Coverage
The operation was canceled.
Continuous integration
Canceling since a higher priority waiting request for Continuous integration-4841 exists
Check SemVer compatibility
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: obi1kenobi/cargo-semver-checks-action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/