Skip to content
Tests

Fix new gRPC methods to use camel case (non-breaking change) (#560) #114

Sign in to view logs

Fix new gRPC methods to use camel case (non-breaking change) (#560)

Fix new gRPC methods to use camel case (non-breaking change) (#560) #114

Triggered via push September 16, 2024 21:24
@smartgoosmartgoo
pushed 613d082
master
Status Failure
Total duration 45m 46s
Artifacts –

ci.yaml

on: push
Check
0s
Check
Test Suite
0s
Test Suite
Lints
8m 8s
Lints
Check WASM32
0s
Check WASM32
Build WASM32 SDK
0s
Build WASM32 SDK
Build Linux Release
0s
Build Linux Release
Fit to window
Zoom out
Zoom in

Annotations

5 errors
Check
The hosted runner: GitHub Actions 13 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.
Build WASM32 SDK
The hosted runner: GitHub Actions 10 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 WASM32
The hosted runner: GitHub Actions 4 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.
Build Linux Release
The hosted runner: GitHub Actions 11 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 Suite
The hosted runner: GitHub Actions 18 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.