Continuous Forge Tests - Stable

use one forge namespace for each branch #1050

Sign in to view logs

Triggered via pull request April 8, 2024 22:17

aluon

synchronize #12633

aluon/one-forge-stable-per-branch

Status Success

Total duration 1m 45s

Artifacts –

forge-stable.yaml

on: pull_request

determine-test-metadata

run-forge-realistic-env-max-load-long / forge

run-forge-realistic-env-load-sweep / forge

run-forge-realistic-env-workload-sweep / forge

run-forge-realistic-env-graceful-overload / forge

run-forge-realistic-network-tuned-for-throughput / forge

run-forge-consensus-stress-test / forge

run-forge-workload-mix-test / forge

run-forge-single-vfn-perf / forge

run-forge-haproxy / forge

run-forge-fullnode-reboot-stress-test / forge

run-forge-compat / forge

run-forge-changing-working-quorum-test / forge

run-forge-changing-working-quorum-test-high-load / forge

run-forge-pfn-const-tps-realistic-env / forge

Annotations

1 warning

determine-test-metadata

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, aptos-labs/setup-buildx-action@7952e9cf0debaf1f3f3e5dc7d9c5ea6ececb127e, docker/login-action@v2, actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.