Skip to content
CI

Fix panic when providing 0 to ilog10 in line number length logic (#26… #47309

Sign in to view logs

Fix panic when providing 0 to ilog10 in line number length logic (#26…

Fix panic when providing 0 to ilog10 in line number length logic (#26… #47309

Triggered via push March 15, 2025 19:10
@mgsloanmgsloan
pushed c220fb3
main
Status Failure
Total duration 17m 35s
Billable time 23m
Artifacts –

ci.yml

on: push
Decide which jobs to run
6s
Decide which jobs to run
(Linux) Run Clippy and tests
14m 55s
(Linux) Run Clippy and tests
(macOS) Run Clippy and tests
4m 33s
(macOS) Run Clippy and tests
Check Postgres and Protobuf migrations, mergability
9s
Check Postgres and Protobuf migrations, mergability
Check formatting and spelling
30s
Check formatting and spelling
(Linux) Build Remote Server
1m 29s
(Linux) Build Remote Server
(Windows) Run Clippy
7m 57s
(Windows) Run Clippy
(Windows) Run Tests
14m 3s
(Windows) Run Tests
Linux x86_x64 release bundle
0s
Linux x86_x64 release bundle
Linux arm64 release bundle
0s
Linux arm64 release bundle
Create a macOS bundle
0s
Create a macOS bundle
Tests Pass
0s
Tests Pass
Auto release preview
0s
Auto release preview
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
(Linux) Run Clippy and tests
The self-hosted runner: buildjet.com_b89c25ae-f953-40e6-8773-cc522d7bd5d9 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.
Tests Pass
Process completed with exit code 1.
Check Postgres and Protobuf migrations, mergability
No github_token supplied, API requests will be subject to stricter rate limiting