feat: add grpc socket and flattn tx batches to allow for lower allocations #2415
tac0turtleci.yml
on: pull_request
Detect code changes
4s
test
/
Run Unit Tests
3m 27s
test
/
Run Integration Tests
2m 3s
lint
/
golangci-lint
1m 51s
lint
/
hadolint
27s
lint
/
yamllint
9s
lint
/
markdown-lint
29s
lint
/
goreleaser-check
13s
test
/
Go Mod Tidy Check
1m 0s
proto
/
buf-check
7s
Matrix: docker / build-images
test
/
Combine and Upload Coverage
9s
test
/
Run E2E System Tests
12m 31s
test
/
Run EVM Execution Tests
1m 46s
docker-tests
/
Docker E2E Tests
6m 51s
docker-tests
/
Docker Upgrade E2E Tests
3m 19s
docker-tests
/
Docker Compatibility E2E Tests
4m 2s
Annotations
15 errors, 8 warnings, and 1 notice
|
proto / buf-check:
proto/evnode/v1/execution.proto#L125
Field "1" with name "tx_batch" on message "FilterTxsRequest" changed option "json_name" from "txs" to "txBatch".
|
|
proto / buf-check:
proto/evnode/v1/execution.proto#L125
Field "1" with name "tx_batch" on message "FilterTxsRequest" changed cardinality from "repeated" to "optional with explicit presence".
|
|
proto / buf-check:
proto/evnode/v1/execution.proto#L70
Field "1" on message "ExecuteTxsRequest" changed name from "txs" to "tx_batch".
|
|
proto / buf-check:
proto/evnode/v1/execution.proto#L70
Field "1" with name "tx_batch" on message "ExecuteTxsRequest" changed type from "bytes" to "message".
|
|
proto / buf-check:
proto/evnode/v1/execution.proto#L70
Field "1" with name "tx_batch" on message "ExecuteTxsRequest" changed option "json_name" from "txs" to "txBatch".
|
|
proto / buf-check:
proto/evnode/v1/execution.proto#L70
Field "1" with name "tx_batch" on message "ExecuteTxsRequest" changed cardinality from "repeated" to "optional with explicit presence".
|
|
proto / buf-check:
proto/evnode/v1/execution.proto#L64
Field "1" on message "GetTxsResponse" changed name from "txs" to "tx_batch".
|
|
proto / buf-check:
proto/evnode/v1/execution.proto#L64
Field "1" with name "tx_batch" on message "GetTxsResponse" changed type from "bytes" to "message".
|
|
proto / buf-check:
proto/evnode/v1/execution.proto#L64
Field "1" with name "tx_batch" on message "GetTxsResponse" changed option "json_name" from "txs" to "txBatch".
|
|
proto / buf-check:
proto/evnode/v1/execution.proto#L64
Field "1" with name "tx_batch" on message "GetTxsResponse" changed cardinality from "repeated" to "optional with explicit presence".
|
|
lint / markdown-lint
Process completed with exit code 1.
|
|
lint / hadolint:
tools/local-da/Dockerfile#L13
DL3003 warning: Use WORKDIR to switch to a directory
|
|
lint / hadolint:
apps/testapp/Dockerfile#L24
DL3003 warning: Use WORKDIR to switch to a directory
|
|
lint / hadolint:
apps/testapp/Dockerfile#L4
DL3008 warning: Pin versions in apt get install. Instead of `apt-get install <package>` use `apt-get install <package>=<version>`
|
|
test / Go Mod Tidy Check
Process completed with exit code 1.
|
|
Detect code changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
lint / goreleaser-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: technote-space/get-diff-action@v6.1.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
lint / yamllint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: technote-space/get-diff-action@v6.1.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
lint / markdown-lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v3, technote-space/get-diff-action@v6.1.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
lint / golangci-lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: technote-space/get-diff-action@v6.1.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / Build ev-node-testapp
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / Build ev-node-grpc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / Build ev-node-evm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Determine Image Tag
Using PR-based tag: pr-3297
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
evstack~ev-node~7H04FP.dockerbuild
Expired
|
94.3 KB |
sha256:f64e0087e260f17172cf3b31d383a69630aabcfe76afe199a911e43547bb81a9
|
|
|
evstack~ev-node~8JZOCQ.dockerbuild
Expired
|
38.6 KB |
sha256:c44f23008c71c1211f13f4772f3770f8db76f15664ba4288a9500395fbe34036
|
|
|
evstack~ev-node~QGQFMG.dockerbuild
Expired
|
87.1 KB |
sha256:8e1c439f8586ad9742ea471d8a1c76f27534b6bff84cb8aa67c75a8fc0548f98
|
|
|
evstack~ev-node~R4DIQ4.dockerbuild
Expired
|
79.2 KB |
sha256:906144702f5dc73cde7c940ed9bd1712ca17c37c607a01d943a5fcb9658da50f
|
|
|
integration-test-coverage-report-611e8a39fd0566c8bed1807e9776133b1357d4e8
Expired
|
2.34 KB |
sha256:b213943b883d3c6db41741066e736e01c778fcf750dfaf2c1fb60b1d9d68c841
|
|
|
unit-test-coverage-report-611e8a39fd0566c8bed1807e9776133b1357d4e8
Expired
|
82.8 KB |
sha256:06b05570ab3501f17092c42d389f462f56147e6a3d3c8b4da5d469b44af7089b
|
|