Skip to content
Lint

Update errorCode return type #21330

Sign in to view logs

Update errorCode return type

Update errorCode return type #21330

Triggered via push May 22, 2025 07:32
@ondrejmirtesondrejmirtes
pushed 0c4660d
1.12.x
Status Failure
Total duration 50m 5s
Artifacts –

lint.yml

on: push
Coding Standard
0s
Coding Standard
Dependency Analysis
0s
Dependency Analysis
Name Collision Detector
21s
Name Collision Detector
Matrix: Lint
Fit to window
Zoom out
Zoom in

Annotations

7 errors
Coding Standard
The hosted runner: GitHub Actions 478 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.
Dependency Analysis
The hosted runner: GitHub Actions 202 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.
Lint (7.4)
The hosted runner: GitHub Actions 299 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.
Lint (8.0)
The hosted runner: GitHub Actions 169 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.
Lint (8.2)
The hosted runner: GitHub Actions 342 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.
Lint (8.3)
The hosted runner: GitHub Actions 309 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.
Lint (8.1)
The hosted runner: GitHub Actions 72 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.