Skip to content
Go

Attempt to use go21 #1292

Sign in to view logs

Attempt to use go21

Attempt to use go21 #1292

Triggered via pull request July 17, 2024 04:25
@AskAlexSharovAskAlexSharov
opened #962
erigontech:attempt_to_use_go21
Status Failure
Total duration 6m 36s
Artifacts –

go.yml

on: pull_request
Matrix: bench
Matrix: build-wasm
Matrix: test-386
Matrix: test-benchmarks
Matrix: test
Matrix: torrentfs-linux
Fit to window
Zoom out
Zoom in

Annotations

22 errors and 18 warnings
build-wasm (1.22): peer_protocol/decoder.go#L173
cannot range over numHashes (variable of type int64): requires go1.22 or later (-lang was set to go1.21; check go.mod)
build-wasm (1.22)
Process completed with exit code 1.
torrentfs-linux (1.22, ubuntu-latest)
cannot range over numHashes (variable of type int64): requires go1.22 or later (-lang was set to go1.21; check go.mod)
torrentfs-linux (1.22, ubuntu-latest)
Process completed with exit code 1.
test-386 (1.22): peer_protocol/decoder.go#L173
cannot range over numHashes (variable of type int64): requires go1.22 or later (-lang was set to go1.21; check go.mod)
test-386 (1.22)
Process completed with exit code 1.
test (1.22, macos-latest): peer_protocol/decoder.go#L173
cannot range over numHashes (variable of type int64): requires go1.22 or later (-lang was set to go1.21; check go.mod)
test (1.22, macos-latest)
Process completed with exit code 1.
test (1.22, macos-latest): peer_protocol/decoder.go#L173
cannot range over numHashes (variable of type int64): requires go1.22 or later (-lang was set to go1.21; check go.mod)
test (1.22, macos-latest)
Process completed with exit code 1.
test-benchmarks (1.22): peer_protocol/decoder.go#L173
cannot range over numHashes (variable of type int64): requires go1.22 or later (-lang was set to go1.21; check go.mod)
test-benchmarks (1.22)
Process completed with exit code 1.
bench (1.21): peer_protocol/decoder.go#L173
cannot range over numHashes (variable of type int64): requires go1.22 or later (-lang was set to go1.21; check go.mod)
bench (1.21)
Process completed with exit code 1.
bench (1.22): peer_protocol/decoder.go#L173
cannot range over numHashes (variable of type int64): requires go1.22 or later (-lang was set to go1.21; check go.mod)
bench (1.22)
Process completed with exit code 1.
test (1.22, ubuntu-latest): peer_protocol/decoder.go#L173
cannot range over numHashes (variable of type int64): requires go1.22 or later (-lang was set to go1.21; check go.mod)
test (1.22, ubuntu-latest)
Process completed with exit code 1.
test (1.22, ubuntu-latest): peer_protocol/decoder.go#L173
cannot range over numHashes (variable of type int64): requires go1.22 or later (-lang was set to go1.21; check go.mod)
test (1.22, ubuntu-latest)
Process completed with exit code 1.
test (1.22, windows-latest): peer_protocol/decoder.go#L173
cannot range over numHashes (variable of type int64): requires go1.22 or later (-lang was set to go1.21; check go.mod)
test (1.22, windows-latest)
Process completed with exit code 1.
build-wasm (1.22)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-wasm (1.22)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
torrentfs-linux (1.22, ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
torrentfs-linux (1.22, ubuntu-latest)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-go@v2, actions/cache@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-386 (1.22)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2, actions/cache@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-386 (1.22)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-go@v2, actions/cache@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 (1.22, macos-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/cache@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 (1.22, macos-latest)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-go@v2, actions/cache@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-benchmarks (1.22)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/cache@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-benchmarks (1.22)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
bench (1.21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
bench (1.21)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
bench (1.22)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
bench (1.22)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-go@v2, actions/cache@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 (1.22, ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/cache@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 (1.22, ubuntu-latest)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-go@v2, actions/cache@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 (1.22, windows-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/cache@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 (1.22, windows-latest)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/