Skip to content

Fix timestamp clamping to prevent overflow when converting to milliseconds #2032

Fix timestamp clamping to prevent overflow when converting to milliseconds

Fix timestamp clamping to prevent overflow when converting to milliseconds #2032

Re-run triggered January 30, 2026 21:11
Status Failure
Total duration 23m 11s
Artifacts

test.yml

on: pull_request
Matrix: nextest / test
ci-success
ci-success
Fit to window
Zoom out
Zoom in

Annotations

4 errors
cargo deny check
Process completed with exit code 1.
nextest / test integration / issue-repros (2/2) (x86_64-unknown-linux-gnu)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
nextest / test integration / issue-repros (1/2) (x86_64-unknown-linux-gnu)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
nextest / test integration (2/3) (x86_64-unknown-linux-gnu)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.