Skip to content

Ad-hoc Forge Run

Ad-hoc Forge Run #1942

Manually triggered November 5, 2024 06:44
Status Failure
Total duration 26m 48s
Artifacts

adhoc-forge.yaml

on: workflow_dispatch
determine-forge-run-metadata
3s
determine-forge-run-metadata
adhoc-forge-test  /  forge
26m 9s
adhoc-forge-test / forge
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
adhoc-forge-test / forge
Failed latency check, for ["P50 latency for 3000 is 1.4s and exceeds limit of 1.4s"]
adhoc-forge-test / forge
Failed latency check, for ["P50 latency for 3000 is 1.4s and exceeds limit of 1.4s"]
adhoc-forge-test / forge
Failed latency check, for ["P50 latency for 3000 is 1.4s and exceeds limit of 1.4s"]
adhoc-forge-test / forge
Process completed with exit code 1.
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.319.1. Please update to the latest version 2.320.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/