Be #5287
WorksButNotTestedmain.yml
on: pull_request
Rustfmt
21s
Matrix: Check
Matrix: Check nightly-only targets
Matrix: Check --no-default-features
Matrix: Check selected Tier 3 platforms
Matrix: Test
Matrix: Test rustix_use_experimental_asm
Matrix: Test use-libc
Annotations
14 errors and 1 warning
|
Check --no-default-features (nightly)
The hosted runner: GitHub Actions 319 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.
|
|
Check nightly-only targets (nightly)
The hosted runner: GitHub Actions 193 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 rustix_use_experimental_asm (powerpc64le-linux)
The hosted runner: GitHub Actions 442 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 (aarch64-linux-stable)
The hosted runner: GitHub Actions 313 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 use-libc (i686-linux)
The hosted runner: GitHub Actions 264 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 use-libc (powerpc64le-linux)
The hosted runner: GitHub Actions 149 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 use-libc (ubuntu)
The hosted runner: GitHub Actions 328 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-22.04)
GitHub Actions has encountered an internal error when running your job.
|
|
Test (musl)
The hosted runner: GitHub Actions 459 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 (arm-linux-1.63)
The hosted runner: GitHub Actions 305 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 (s390x-linux-stable)
The job was canceled because "aarch64-linux-stable" failed.
|
|
Test (riscv64-linux-stable)
The hosted runner: GitHub Actions 160 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 (powerpc-linux)
The hosted runner: GitHub Actions 15 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 (s390x-linux)
The hosted runner: GitHub Actions 153 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-2019)
The windows-2019 runner image is being deprecated, consider switching to windows-2022(windows-latest) or windows-2025 instead. For more details see https://github.com/actions/runner-images/issues/12045.
|