feat: Avoid spawning async-io thread if possible #962
Triggered via pull request
February 15, 2026 22:29
notgull
Status
Failure
Total duration
6h 6m 24s
Artifacts
–
ci.yml
on: pull_request
fmt
/
fmt
14s
clippy
/
clippy
28s
security_audit
/
security_audit
22s
wine
6h 5m
Matrix: cross
Matrix: msrv
Matrix: test
Matrix: windows_gnu
Annotations
10 errors
|
clippy / clippy
Process completed with exit code 101.
|
|
test (windows-latest, beta)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
test (windows-latest, stable)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
test (windows-latest, nightly)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
windows_gnu (nightly, x86_64-pc-windows-gnu)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
test (ubuntu-latest, beta)
The job has exceeded the maximum execution time of 6h0m0s
|
|
test (ubuntu-latest, beta)
The operation was canceled.
|
|
cross (ubuntu-latest, nightly)
The job has exceeded the maximum execution time of 6h0m0s
|
|
wine
The job has exceeded the maximum execution time of 6h0m0s
|
|
test (macos-latest, stable)
The job has exceeded the maximum execution time of 6h0m0s
|