refactor: replace context.WithCancel with t.Context #1920
ci.yml
on: pull_request
Determine Image Tag
4s
test
/
Run Unit Tests
2m 50s
test
/
Run Integration Tests
1m 54s
test
/
Build All ev-node Binaries
1m 33s
lint
/
golangci-lint
1m 39s
lint
/
hadolint
11s
lint
/
yamllint
9s
lint
/
markdown-lint
21s
lint
/
goreleaser-check
12s
test
/
Go Mod Tidy Check
1m 16s
proto
/
buf-check
7s
Matrix: docker / build-images
test
/
Combine and Upload Coverage
9s
test
/
Run E2E System Tests
14m 17s
test
/
Run EVM Execution Tests
3m 20s
docker-tests
/
Docker Compatibility E2E Tests
docker-tests
/
Docker E2E Tests
docker-tests
/
Docker Upgrade E2E Tests
Annotations
9 errors, 13 warnings, and 1 notice
|
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>`
|
|
docker / Build ev-node-grpc
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/evstack/ev-node-grpc:pr-3183: denied: installation not allowed to Write organization package
|
|
docker / Build ev-node-testapp
The strategy configuration was canceled because "docker.build-images.ev-node-grpc_apps_grpc_Do" failed
|
|
docker / Build ev-node-testapp
The operation was canceled.
|
|
docker / Build ev-node-evm
The strategy configuration was canceled because "docker.build-images.ev-node-grpc_apps_grpc_Do" failed
|
|
docker / Build ev-node-evm
The operation was canceled.
|
|
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 / 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 / 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/
|
|
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/
|
|
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/
|
|
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/
|
|
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/
|
|
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/
|
|
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/
|
|
Determine Image Tag
Using PR-based tag: pr-3183
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
evstack~ev-node~75RAK5.dockerbuild
|
36.2 KB |
sha256:aa0585de68ebab9a3d66861cbdd3c7e2a6b6e377920f96bbd39e886410d0a7e1
|
|
|
evstack~ev-node~X3I42R.dockerbuild
|
75 KB |
sha256:f590ea921e70972b2c3ca8555504c9ccc2500cb67154f0dde81ebc8ea632d969
|
|
|
integration-test-coverage-report-761840796077b19c9ba59387e941e102ec63ec72
|
2.25 KB |
sha256:c2d5ed21bb7d769f8380c7928d23a15460d5c795160584b348a31ba8ac4f7b37
|
|
|
unit-test-coverage-report-761840796077b19c9ba59387e941e102ec63ec72
|
78.1 KB |
sha256:88ed1e316974c94ae8fddaa44d90b93e83b91ce587e2c052ffe6096109982283
|
|