fix: preserve log files on failure and fix MultiWriterCloser (#173) #748
build.yaml
on: push
build-binaries
/
build-contracts
40s
build-binaries
/
build-reth
18m 24s
build-binaries
/
build-geth
2m 35s
build-binaries
/
build-base-reth-node
21m 59s
build-binaries
/
build-op-program
3m 40s
go-lint
2m 22s
go-test
2m 11s
basic-benchmarks
8m 22s
Annotations
1 error and 8 warnings
|
basic-benchmarks
Process completed with exit code 1.
|
|
build-binaries / build-contracts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@2f8e54208210a422b2efd51efaa6bd6d7ca8920f, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@6f51ac03b9356f520e9adb1b1b7802705f340c2b, foundry-rs/foundry-toolchain@82dee4ba654bd2146511f85f0d013af94670c4de, step-security/harden-runner@002fdce3c6a235733a90a27c80493a3241e56863. 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/
|
|
go-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, step-security/harden-runner@002fdce3c6a235733a90a27c80493a3241e56863. 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/
|
|
go-lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, golangci/golangci-lint-action@1481404843c368bc19ca9406f87d6e0fc97bdcfd, step-security/harden-runner@002fdce3c6a235733a90a27c80493a3241e56863. 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/
|
|
build-binaries / build-geth
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@2f8e54208210a422b2efd51efaa6bd6d7ca8920f, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@6f51ac03b9356f520e9adb1b1b7802705f340c2b, step-security/harden-runner@002fdce3c6a235733a90a27c80493a3241e56863. 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/
|
|
build-binaries / build-op-program
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@2f8e54208210a422b2efd51efaa6bd6d7ca8920f, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@6f51ac03b9356f520e9adb1b1b7802705f340c2b, step-security/harden-runner@002fdce3c6a235733a90a27c80493a3241e56863. 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/
|
|
build-binaries / build-reth
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@2f8e54208210a422b2efd51efaa6bd6d7ca8920f, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@6f51ac03b9356f520e9adb1b1b7802705f340c2b, step-security/harden-runner@002fdce3c6a235733a90a27c80493a3241e56863. 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/
|
|
build-binaries / build-base-reth-node
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@2f8e54208210a422b2efd51efaa6bd6d7ca8920f, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@6f51ac03b9356f520e9adb1b1b7802705f340c2b, step-security/harden-runner@002fdce3c6a235733a90a27c80493a3241e56863. 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/
|
|
basic-benchmarks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@fa0a91b85d4f404e444e00e005971372dc801d16, actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, step-security/harden-runner@002fdce3c6a235733a90a27c80493a3241e56863. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
base-reth-node
Expired
|
30 MB |
sha256:4fa600a446dd7dd4b32a20923b3932ddad105bc7dc2f8f85c1921d0d72ac4e75
|
|
|
builder
Expired
|
26.3 MB |
sha256:9ae980fa19d25f0b9ed574d1ac18fb1a44ebf477446c32ae111ec795f2439f66
|
|
|
contracts
Expired
|
79.5 KB |
sha256:5219ed0b914ada275248c63756294585fc0ee3101129e6592a0a1422b736c278
|
|
|
geth
Expired
|
27.5 MB |
sha256:3ee2d6f90098b64c975927918d8886def026bd1931835cbd4f9bbbe8229ec066
|
|
|
op-program
Expired
|
29.3 MB |
sha256:78afbdfe900a60cd34c01ce870edc8f91f1383afceacf6b58df27f6a788221db
|
|
|
optimism
Expired
|
29.7 MB |
sha256:2064a915cf13dc431a8331cc07878a2b32ca6261807d3e7e85925be5da08c6fa
|
|