Skip to content
Test

blockRange feature to configure transaction max block (#160) #977

Sign in to view logs

blockRange feature to configure transaction max block (#160)

blockRange feature to configure transaction max block (#160) #977

Triggered via push October 28, 2024 18:27
@TymKhTymKh
pushed 06a42c8
main
Status Failure
Total duration 49s
Artifacts –

test.yml

on: push
Test
41s
Test
Lint
40s
Lint
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
Lint
Process completed with exit code 2.
Test
Process completed with exit code 2.
Lint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/