jsonrpc: fix bug in getting trxs #350
ci.yml
on: pull_request
docker-build-check
6m 20s
automated-tests
6m 36s
Matrix: tests-windows
Matrix: tests
Annotations
22 errors and 5 warnings
|
automated-tests
Process completed with exit code 1.
|
|
tests (ubuntu-20.04):
turbo/stages/blockchain_test.go#L1
: # github.com/ledgerwatch/erigon/turbo/stages_test [github.com/ledgerwatch/erigon/turbo/stages.test]
|
|
tests (ubuntu-20.04):
turbo/stages/blockchain_test.go#L1026
not enough arguments in call to m.NewHistoryStateReader
|
|
tests (ubuntu-20.04):
turbo/stages/blockchain_test.go#L1030
not enough arguments in call to m.NewHistoryStateReader
|
|
tests (ubuntu-20.04):
turbo/stages/blockchain_test.go#L1034
not enough arguments in call to m.NewHistoryStateReader
|
|
tests (ubuntu-20.04):
turbo/stages/blockchain_test.go#L1389
not enough arguments in call to m.NewHistoryStateReader
|
|
tests (ubuntu-20.04):
turbo/stages/blockchain_test.go#L1507
not enough arguments in call to m.NewHistoryStateReader
|
|
tests (ubuntu-20.04):
turbo/stages/blockchain_test.go#L1574
not enough arguments in call to m.NewHistoryStateReader
|
|
tests (ubuntu-20.04):
turbo/stages/blockchain_test.go#L1886
not enough arguments in call to m.NewHistoryStateReader
|
|
tests (ubuntu-20.04):
turbo/stages/blockchain_test.go#L1896
not enough arguments in call to m.NewHistoryStateReader
|
|
tests (ubuntu-20.04):
turbo/stages/blockchain_test.go#L2092
not enough arguments in call to m.NewHistoryStateReader
|
|
tests (macos-11)
The operation was canceled.
|
|
tests-windows (windows-2022):
turbo/stages/blockchain_test.go#L1026
not enough arguments in call to m.NewHistoryStateReader
|
|
tests-windows (windows-2022):
turbo/stages/blockchain_test.go#L1030
not enough arguments in call to m.NewHistoryStateReader
|
|
tests-windows (windows-2022):
turbo/stages/blockchain_test.go#L1034
not enough arguments in call to m.NewHistoryStateReader
|
|
tests-windows (windows-2022):
turbo/stages/blockchain_test.go#L1389
not enough arguments in call to m.NewHistoryStateReader
|
|
tests-windows (windows-2022):
turbo/stages/blockchain_test.go#L1507
not enough arguments in call to m.NewHistoryStateReader
|
|
tests-windows (windows-2022):
turbo/stages/blockchain_test.go#L1574
not enough arguments in call to m.NewHistoryStateReader
|
|
tests-windows (windows-2022):
turbo/stages/blockchain_test.go#L1886
not enough arguments in call to m.NewHistoryStateReader
|
|
tests-windows (windows-2022):
turbo/stages/blockchain_test.go#L1896
not enough arguments in call to m.NewHistoryStateReader
|
|
tests-windows (windows-2022):
turbo/stages/blockchain_test.go#L2092
not enough arguments in call to m.NewHistoryStateReader
|
|
tests-windows (windows-2022):
turbo/stages/blockchain_test.go#L2133
not enough arguments in call to m.NewHistoryStateReader
|
|
docker-build-check
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
automated-tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
tests (ubuntu-20.04)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-go@v4, golangci/golangci-lint-action@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
tests (macos-11)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-go@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
tests-windows (windows-2022)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-go@v4, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|