[DONOTCOMMIT] temp override forge to forge-1 to test PR jobs

[perryjrandall]

Description

How Has This Been Tested?

Key Areas to Review

Type of Change

• New feature
• Bug fix
• Breaking change
• Performance improvement
• Refactoring
• Dependency update
• Documentation update
• Tests

Which Components or Systems Does This Change Impact?

• Validator Node
• Full Node (API, Indexer, etc.)
• Move/Aptos Virtual Machine
• Aptos Framework
• Aptos CLI/SDK
• Developer Infrastructure
• Move Compiler
• Other (specify)

Checklist

• I have read and followed the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I identified and added all stakeholders and component owners affected by this change as reviewers
• I tested both happy and unhappy path of the functionality
• I have made corresponding changes to the documentation

[trunk-io]

⏱️ 59m total CI duration on this PR

Slowest 15 Jobs	Cumulative Duration	Recent Runs
execution-performance / single-node-performance	23m	🟩
rust-move-tests	13m	🟩
rust-doc-tests	5m	🟩
check	3m	🟩
test-target-determinator	3m	🟩
execution-performance / test-target-determinator	3m	🟩
check-dynamic-deps	2m	🟩 🟩
rust-cargo-deny	2m	⬜ 🟩
fetch-last-released-docker-image-tag	2m	🟩
semgrep/ci	50s	🟩 🟩
general-lints	33s	⬜ 🟩
file_change_determinator	17s	🟩 🟩
file_change_determinator	10s	🟩
permission-check	8s	🟩 🟩
permission-check	6s	🟩 🟩

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[perryjrandall]

• [DONOTCOMMIT] temp test forge-2 cluster before enabling #15646
• [DONOTCOMMIT] temp override forge to forge-1 to test PR jobs #15645 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

Based on the PR title [DONOTCOMMIT], this change appears to be temporary testing code. The hardcoded cluster name aptos-forge-1 should be removed before merging, restoring the line to its original form: @envoption("FORGE_CLUSTER_NAME"). This ensures the cluster name remains configurable through environment variables as intended.

Spotted by Graphite Reviewer

Is this helpful? React 👍 or 👎 to let us know.

[github-actions]

✅ Forge suite compat success on 6593fb81261f25490ffddc2252a861c994234c2a ==> fe40dc0b3f080ebfb547f41aa329371e6eab722d

Compatibility test results for 6593fb81261f25490ffddc2252a861c994234c2a ==> fe40dc0b3f080ebfb547f41aa329371e6eab722d (PR)
1. Check liveness of validators at old version: 6593fb81261f25490ffddc2252a861c994234c2a
compatibility::simple-validator-upgrade::liveness-check : committed: 17155.67 txn/s, latency: 2032.08 ms, (p50: 1800 ms, p70: 2000, p90: 2900 ms, p99: 5100 ms), latency samples: 558300
2. Upgrading first Validator to new version: fe40dc0b3f080ebfb547f41aa329371e6eab722d
compatibility::simple-validator-upgrade::single-validator-upgrading : committed: 7768.95 txn/s, latency: 3859.63 ms, (p50: 4500 ms, p70: 4700, p90: 4900 ms, p99: 4900 ms), latency samples: 143540
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 7771.73 txn/s, latency: 4352.06 ms, (p50: 4800 ms, p70: 4900, p90: 5000 ms, p99: 5200 ms), latency samples: 258620
3. Upgrading rest of first batch to new version: fe40dc0b3f080ebfb547f41aa329371e6eab722d
compatibility::simple-validator-upgrade::half-validator-upgrading : committed: 7553.61 txn/s, latency: 3974.27 ms, (p50: 4500 ms, p70: 4800, p90: 4900 ms, p99: 5000 ms), latency samples: 141960
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 7459.88 txn/s, latency: 4519.85 ms, (p50: 4900 ms, p70: 5000, p90: 5100 ms, p99: 5400 ms), latency samples: 251420
4. upgrading second batch to new version: fe40dc0b3f080ebfb547f41aa329371e6eab722d
compatibility::simple-validator-upgrade::rest-validator-upgrading : committed: 10759.70 txn/s, latency: 2728.88 ms, (p50: 3100 ms, p70: 3300, p90: 3500 ms, p99: 3700 ms), latency samples: 189500
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 11038.92 txn/s, latency: 2996.68 ms, (p50: 3000 ms, p70: 3400, p90: 3700 ms, p99: 4000 ms), latency samples: 359960
5. check swarm health
Compatibility test for 6593fb81261f25490ffddc2252a861c994234c2a ==> fe40dc0b3f080ebfb547f41aa329371e6eab722d passed
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Validator CPU Profile
• Fullnode CPU Profile
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite realistic_env_max_load success on fe40dc0b3f080ebfb547f41aa329371e6eab722d

two traffics test: inner traffic : committed: 15034.43 txn/s, latency: 2643.22 ms, (p50: 2700 ms, p70: 2700, p90: 2700 ms, p99: 3000 ms), latency samples: 5716420
two traffics test : committed: 99.97 txn/s, latency: 1366.77 ms, (p50: 1300 ms, p70: 1400, p90: 1500 ms, p99: 2500 ms), latency samples: 1800
Latency breakdown for phase 0: ["MempoolToBlockCreation: max: 1.554, avg: 1.513", "ConsensusProposalToOrdered: max: 0.287, avg: 0.285", "ConsensusOrderedToCommit: max: 0.305, avg: 0.297", "ConsensusProposalToCommit: max: 0.591, avg: 0.583"]
Max non-epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.51s no progress at version 20907 (avg 0.19s) [limit 15].
Max epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.93s no progress at version 6477398 (avg 0.74s) [limit 16].
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Validator CPU Profile
• Fullnode CPU Profile
• Test runner output
• Test run is land-blocking