feat: integrate with v0.52.x (1/n) #14216
Triggered via pull request
September 19, 2024 08:59
julienrbrt
Status
Failure
Total duration
2h 1m 40s
Artifacts
–
Annotations
23 errors
|
test relayer on ubuntu-latest
Process completed with exit code 1.
|
|
test relayer on macos-latest
Process completed with exit code 1.
|
|
test faucet on macos-latest
Process completed with exit code 1.
|
|
test faucet on ubuntu-latest
Process completed with exit code 1.
|
|
test tx on ubuntu-latest
Process completed with exit code 1.
|
|
test list on macos-latest
Process completed with exit code 1.
|
|
test single on ubuntu-latest
Process completed with exit code 1.
|
|
test tx on macos-latest
Process completed with exit code 1.
|
|
test list on ubuntu-latest
Process completed with exit code 1.
|
|
test map on ubuntu-latest
Process completed with exit code 1.
|
|
test single on macos-latest
Process completed with exit code 1.
|
|
test map on macos-latest
Process completed with exit code 1.
|
|
test app on ubuntu-latest
The hosted runner: GitHub Actions 378 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 params on ubuntu-latest
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test params on ubuntu-latest
Process completed with exit code 143.
|
|
test params on macos-latest
Process completed with exit code 1.
|
|
test other_components on macos-latest
Process completed with exit code 1.
|
|
test chain on macos-latest
Process completed with exit code 1.
|
|
test chain on ubuntu-latest
The hosted runner: GitHub Actions 249 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 other_components on ubuntu-latest
The hosted runner: GitHub Actions 304 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 app on macos-latest
undefined: genutil.NewAppModuleBasic
|
|
test app on macos-latest
Process completed with exit code 1.
|
|
status
Process completed with exit code 1.
|