Skip to content
Continuous Integration (Commit)

disable check-proto-breaking-remote #2896

Sign in to view logs

disable check-proto-breaking-remote

disable check-proto-breaking-remote #2896

Triggered via push October 28, 2024 22:10
@pirtleshellpirtleshell
pushed 34aa88d
rp-bump-ethermint
Status Failure
Total duration 3m 31s
Artifacts –

ci-commit.yml

on: push
lint  /  ...  /  Check Proto
3m 22s
lint / proto-lint / Check Proto
lint  /  golangci-lint
2m 19s
lint / golangci-lint
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
lint / golangci-lint: x/evmutil/types/errors.go#L7
Magic number: 2, in <argument> detected (mnd)
lint / golangci-lint: x/evmutil/types/errors.go#L8
Magic number: 3, in <argument> detected (mnd)
lint / golangci-lint: x/evmutil/types/errors.go#L9
Magic number: 4, in <argument> detected (mnd)
lint / golangci-lint: x/evmutil/types/errors.go#L10
Magic number: 5, in <argument> detected (mnd)
lint / golangci-lint: x/evmutil/types/errors.go#L11
Magic number: 6, in <argument> detected (mnd)
lint / golangci-lint: x/evmutil/types/errors.go#L12
Magic number: 7, in <argument> detected (mnd)
lint / golangci-lint: x/evmutil/types/errors.go#L13
Magic number: 8, in <argument> detected (mnd)
lint / golangci-lint: x/evmutil/types/errors.go#L14
Magic number: 9, in <argument> detected (mnd)
lint / golangci-lint: tests/util/evmsigner.go#L84
var-naming: func parameter evmChainId should be evmChainID (revive)
lint / golangci-lint: tests/util/addresses.go#L20
Magic number: 128, in <argument> detected (mnd)
lint / golangci-lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint / proto-lint / Check Proto
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/