Skip to content

fix: arbitrum slowpath processing #12083

fix: arbitrum slowpath processing

fix: arbitrum slowpath processing #12083

Triggered via pull request August 25, 2024 16:37
Status Success
Total duration 20m 33s
Artifacts

build-test-deploy.yml

on: pull_request
build-and-push-router-publisher-image
0s
build-and-push-router-publisher-image
build-and-push-router-subscriber-image
0s
build-and-push-router-subscriber-image
build-and-push-router-executor-image
0s
build-and-push-router-executor-image
build-and-push-sequencer-server-image
0s
build-and-push-sequencer-server-image
build-and-push-sequencer-publisher-image
0s
build-and-push-sequencer-publisher-image
build-and-push-sequencer-subscriber-image
0s
build-and-push-sequencer-subscriber-image
build-and-push-cartographer-image
0s
build-and-push-cartographer-image
build-and-push-lighthouse-image
0s
build-and-push-lighthouse-image
build-and-push-lighthouse-prover-subscriber-image
0s
build-and-push-lighthouse-prover-subscriber-image
build-and-push-relayer-image
0s
build-and-push-relayer-image
build-and-push-watcher-image
0s
build-and-push-watcher-image
build-and-push-sdk-server-image
0s
build-and-push-sdk-server-image
smoke-tests
0s
smoke-tests
e2e-tests
0s
e2e-tests
terraform-infra
0s
terraform-infra
terraform-services-core-prod-testnet
0s
terraform-services-core-prod-testnet
terraform-services-backend-prod-testnet
0s
terraform-services-backend-prod-testnet
terraform-services-backend-staging-testnet
0s
terraform-services-backend-staging-testnet
terraform-services-core-staging-testnet
0s
terraform-services-core-staging-testnet
terraform-services-backend-prod-mainnet
0s
terraform-services-backend-prod-mainnet
terraform-services-core-prod-mainnet
0s
terraform-services-core-prod-mainnet
Fit to window
Zoom out
Zoom in

Annotations

1 warning
build-and-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/