Skip to content

Ad-hoc Forge Run

Ad-hoc Forge Run #2077

Re-run triggered December 19, 2024 00:40
Status Failure
Total duration 31m 20s
Artifacts

adhoc-forge.yaml

on: workflow_dispatch
determine-forge-run-metadata
1s
determine-forge-run-metadata
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 3 warnings
adhoc-forge-test / forge
Failed latency check, for ["P50 latency for 1000 is 1.9s and exceeds limit of 0.9s", "P90 latency for 1000 is 3s and exceeds limit of 1.1s", "P99 latency for 1000 is 3.5s and exceeds limit of 1.2s"]
adhoc-forge-test / forge
Failed latency check, for ["P50 latency for 1000 is 1.9s and exceeds limit of 0.9s", "P90 latency for 1000 is 3s and exceeds limit of 1.1s", "P99 latency for 1000 is 3.5s and exceeds limit of 1.2s"]
adhoc-forge-test / forge
Failed latency check, for ["P50 latency for 1000 is 1.9s and exceeds limit of 0.9s", "P90 latency for 1000 is 3s and exceeds limit of 1.1s", "P99 latency for 1000 is 3.5s and exceeds limit of 1.2s"]
adhoc-forge-test / forge
Process completed with exit code 1.
determine-forge-run-metadata
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
adhoc-forge-test / forge
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
adhoc-forge-test / forge
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, aptos-labs/setup-buildx-action@7952e9cf0debaf1f3f3e5dc7d9c5ea6ececb127e, docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/