fix: documentation deployment #1951
tac0turtleci.yml
on: pull_request
Determine Image Tag
3s
test
/
Run Unit Tests
2m 51s
test
/
Run Integration Tests
2m 11s
test
/
Build All ev-node Binaries
1m 40s
lint
/
golangci-lint
34s
lint
/
hadolint
10s
lint
/
yamllint
8s
lint
/
markdown-lint
18s
lint
/
goreleaser-check
11s
test
/
Go Mod Tidy Check
34s
proto
/
buf-check
6s
Matrix: docker / build-images
test
/
Combine and Upload Coverage
8s
test
/
Run E2E System Tests
14m 31s
test
/
Run EVM Execution Tests
1m 54s
docker-tests
/
Docker E2E Tests
6m 57s
docker-tests
/
Docker Upgrade E2E Tests
3m 47s
docker-tests
/
Docker Compatibility E2E Tests
5m 9s
Annotations
8 errors, 28 warnings, and 1 notice
|
lint / yamllint
command [git diff] exited with code 128. message: fatal: ambiguous argument 'get-diff-action/main...get-diff-action/pull/3190/merge': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
|
|
lint / hadolint:
tools/local-da/Dockerfile#L13
DL3003 warning: Use WORKDIR to switch to a directory
|
|
lint / hadolint:
apps/testapp/Dockerfile#L24
DL3062 warning: Pin versions in go. Instead of `go install <package>` use `go install <package>@<version>`
|
|
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>`
|
|
lint / goreleaser-check
command [git diff] exited with code 128. message: fatal: ambiguous argument 'get-diff-action/main...get-diff-action/pull/3190/merge': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
|
|
lint / markdown-lint
command [git diff] exited with code 128. message: fatal: ambiguous argument 'get-diff-action/main...get-diff-action/pull/3190/merge': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
|
|
lint / golangci-lint
command [git diff] exited with code 128. message: fatal: ambiguous argument 'get-diff-action/main...get-diff-action/pull/3190/merge': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
|
|
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. 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
>> 'git <command> [<revision>...] -- [<file>...]'
|
|
lint / yamllint
>> Use '--' to separate paths from revisions, like this:
|
|
lint / yamllint
>> fatal: ambiguous argument 'get-diff-action/main...get-diff-action/pull/3190/merge': unknown revision or path not in the working tree.
|
|
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. 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
>> 'git <command> [<revision>...] -- [<file>...]'
|
|
lint / goreleaser-check
>> Use '--' to separate paths from revisions, like this:
|
|
lint / goreleaser-check
>> fatal: ambiguous argument 'get-diff-action/main...get-diff-action/pull/3190/merge': unknown revision or path not in the working tree.
|
|
lint / markdown-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. 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
>> 'git <command> [<revision>...] -- [<file>...]'
|
|
lint / markdown-lint
>> Use '--' to separate paths from revisions, like this:
|
|
lint / markdown-lint
>> fatal: ambiguous argument 'get-diff-action/main...get-diff-action/pull/3190/merge': unknown revision or path not in the working tree.
|
|
test / Go Mod Tidy Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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. 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
>> 'git <command> [<revision>...] -- [<file>...]'
|
|
lint / golangci-lint
>> Use '--' to separate paths from revisions, like this:
|
|
lint / golangci-lint
>> fatal: ambiguous argument 'get-diff-action/main...get-diff-action/pull/3190/merge': unknown revision or path not in the working tree.
|
|
test / Build All ev-node Binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test / Run Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test / Run Unit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test / Run EVM Execution Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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. 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. 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/
|
|
test / Run E2E System Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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. 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-tests / Docker Upgrade E2E Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-tests / Docker Compatibility E2E Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-tests / Docker E2E Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-3190
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
evstack~ev-node~8P9KAQ.dockerbuild
Expired
|
82.1 KB |
sha256:a28ed0e9f337fb62d3811ac5598887a3caa924490e663fa18d5358a1b5e67010
|
|
|
evstack~ev-node~AZYJMM.dockerbuild
Expired
|
80.5 KB |
sha256:e57c61b91bab92812681eda220d8da4c1a2301e9d2383459c4e1b6f3faf06dd3
|
|
|
evstack~ev-node~GGAB1X.dockerbuild
Expired
|
77.3 KB |
sha256:4e803ada662cf09c01191a30270a8ae072b9dc7acd94df71d1420d414f52dd53
|
|
|
evstack~ev-node~ZV48J4.dockerbuild
Expired
|
35.4 KB |
sha256:51627fe65c14308f2daa7c1aea56c80dbf8e83b6f59d31abfb26ded8d9a01517
|
|
|
integration-test-coverage-report-25a59539bd4e305ee934e7c290e4c81e234cf1bf
Expired
|
2.24 KB |
sha256:a73022ee4b7cd4f096cbef261dc6f71645d018edc9b153b7479a51c9ee2ea5ca
|
|
|
unit-test-coverage-report-25a59539bd4e305ee934e7c290e4c81e234cf1bf
Expired
|
78.2 KB |
sha256:e3c27cc7cab04df31755a9f206706d5389a336fb55f4fba1911d7c2e90176367
|
|