feat: ci-network-scenario label #17505

just-mitch · 2025-10-04T09:36:59Z

Add GitHub Actions for Network Scenario Tests on PRs

This PR adds a new workflow that allows developers to trigger network scenario tests on pull requests by adding the ci-network-scenario label. The workflow deploys a full Aztec network in a PR-specific Kubernetes namespace and runs scenario tests against it.

Key features:

New GitHub workflow ci3-network-scenario.yml triggered by the ci-network-scenario label
Reusable GitHub Actions for GCP authentication and network environment setup
Automatic cleanup of Kubernetes resources after tests complete
PR comments with test results and status information
Caching to prevent redundant test runs for the same code

The implementation extracts common functionality from the existing test-network-scenarios.yml workflow into reusable GitHub Actions:

setup-gcp-auth - Handles GCP service account authentication and kubectl setup
setup-network-env - Creates network environment configuration and SSH keys

This allows developers to run the same network scenario tests that are run on releases, but on their PRs before merging.

just-mitch · 2025-10-04T09:37:18Z

feat: ci-network-scenario label #17505 👈 (View in Graphite)
next

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

github-actions · 2025-10-04T10:57:40Z

✅ Network Scenario Tests PASSED

Test Status: passed
Namespace: pr-17505-scenario
Cleanup Status: ✅ Cleaned up successfully
Workflow Run: View logs

To re-run tests, add the ci-network-scenario label again

github-actions · 2025-10-04T11:27:58Z

❌ Network Scenario Tests FAILED

Test Status: failed
Namespace: pr-17505-scenario
Cleanup Status: ✅ Cleaned up successfully
Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

github-actions · 2025-10-04T14:34:56Z

❌ Network Scenario Tests FAILED

Test Status: failed
Namespace: pr-17505-scenario
Cleanup Status: ✅ Cleaned up successfully
Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

github-actions · 2025-10-16T16:25:44Z

❌ Network Scenario Tests FAILED

Test Status: failed
Namespace: pr-17505-scenario
Cleanup Status: ✅ Cleaned up successfully
Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

github-actions · 2025-10-16T23:16:09Z

❌ Network Scenario Tests FAILED

Test Status: failed
Namespace: pr-17505-scenario
Cleanup Status: ✅ Cleaned up successfully
Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

PhilWindle · 2025-10-20T10:39:49Z

.github/actions/setup-network-env/action.yml

+        SALT=1757186002
+        NAMESPACE=${{ inputs.namespace }}
+        AZTEC_DOCKER_IMAGE="${{ inputs.docker-image }}"
+        AZTEC_EPOCH_DURATION=8


Doesn't this network perpetually re-org? 8 slots isn't enough time to prove the epoch. The nightly runs are set to 32.

github-actions · 2025-10-25T16:58:39Z

❌ Network Scenario Tests FAILED

Test Status: failed
Namespace: pr-17505-scenario
Cleanup Status: ✅ Cleaned up successfully
Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

github-actions · 2025-10-25T19:13:18Z

❌ Network Scenario Tests FAILED

Test Status: failed
Namespace: pr-17505-scenario
Cleanup Status: ✅ Cleaned up successfully
Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

github-actions · 2025-10-25T19:58:48Z

✅ Network Scenario Tests PASSED

Test Status: passed
Namespace: pr-17505-scenario
Cleanup Status: ✅ Cleaned up successfully
Workflow Run: View logs

To re-run tests, add the ci-network-scenario label again

github-actions · 2025-10-25T21:38:18Z

❌ Network Scenario Tests FAILED

Test Status: failed
Namespace: pr-17505-scenario
Cleanup Status: ⚠️ Cleanup may have failed
Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

Manual Cleanup Required

If cleanup failed, you may need to manually delete the namespace:

kubectl delete namespace pr-17505-scenario

To re-run tests, add the ci-network-scenario label again

github-actions · 2025-10-26T14:42:14Z

❌ Network Scenario Tests FAILED

Test Status: failed
Namespace: pr-17505-scenario
Cleanup Status: ⚠️ Cleanup may have failed
Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

Manual Cleanup Required

If cleanup failed, you may need to manually delete the namespace:

kubectl delete namespace pr-17505-scenario

To re-run tests, add the ci-network-scenario label again

ludamad · 2025-10-26T16:16:35Z

.github/workflows/ci3-network-scenario.yml

+
+on:
+  pull_request:
+    types: [labeled]


I think I'm of the camp that ci3.yml could handle everything here. We have already have a mix of machines running with diff CI settings on them for the merge queue path

github-actions · 2025-10-26T18:25:49Z

❌ Network Scenario Tests FAILED

Test Status: failed
Namespace: pr-17505-scenario
Cleanup Status: ⚠️ Cleanup may have failed
Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

Manual Cleanup Required

If cleanup failed, you may need to manually delete the namespace:

kubectl delete namespace pr-17505-scenario

To re-run tests, add the ci-network-scenario label again

release-image/bootstrap.sh

github-actions · 2025-10-26T20:21:19Z

✅ Network Scenario Tests PASSED

Test Status: passed
Namespace: pr-17505-scenario
Cleanup Status: ⚠️ Cleanup may have failed
Workflow Run: View logs

Manual Cleanup Required

If cleanup failed, you may need to manually delete the namespace:

kubectl delete namespace pr-17505-scenario

To re-run tests, add the ci-network-scenario label again

just-mitch · 2026-01-04T14:12:58Z

Closing because @ludamad did this better elsewhere 👍

just-mitch marked this pull request as ready for review October 4, 2025 09:37

just-mitch requested a review from charlielye as a code owner October 4, 2025 09:38

just-mitch added the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 4, 2025

AztecBot removed the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 4, 2025

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from 99620f8 to b84378a Compare October 4, 2025 10:39

just-mitch added the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 4, 2025

AztecBot removed the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 4, 2025

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from b84378a to 430d20e Compare October 4, 2025 11:00

just-mitch added the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 4, 2025

AztecBot removed the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 4, 2025

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from 430d20e to 37056c7 Compare October 4, 2025 14:33

just-mitch added the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 4, 2025

just-mitch had a problem deploying to master October 4, 2025 14:33 — with GitHub Actions Failure

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from 37056c7 to 8cd6ff8 Compare October 7, 2025 07:24

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from 8cd6ff8 to 4886832 Compare October 16, 2025 12:11

just-mitch removed the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 16, 2025

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from 4886832 to 704a0e6 Compare October 16, 2025 16:17

just-mitch added the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 16, 2025

AztecBot removed the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 16, 2025

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from 704a0e6 to 78cf923 Compare October 16, 2025 21:35

just-mitch added the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 16, 2025

AztecBot removed the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 16, 2025

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from 78cf923 to 78794a5 Compare October 17, 2025 18:44

PhilWindle reviewed Oct 20, 2025

View reviewed changes

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from 6e7b6f7 to f7b526b Compare October 25, 2025 18:49

just-mitch added the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 25, 2025

AztecBot removed the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 25, 2025

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from f7b526b to 1b97f02 Compare October 25, 2025 19:31

just-mitch added the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 25, 2025

AztecBot removed the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 25, 2025

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from 1b97f02 to ad58f0a Compare October 25, 2025 21:23

just-mitch added the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 25, 2025

AztecBot removed the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 25, 2025

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from ad58f0a to 318defc Compare October 26, 2025 14:40

just-mitch added the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 26, 2025

AztecBot removed the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 26, 2025

ludamad reviewed Oct 26, 2025

View reviewed changes

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from 318defc to 67cffac Compare October 26, 2025 18:23

just-mitch added the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 26, 2025

AztecBot removed the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 26, 2025

ludamad reviewed Oct 26, 2025

View reviewed changes

release-image/bootstrap.sh Show resolved Hide resolved

feat: ci-network-scenario label

7bb68d7

just-mitch force-pushed the mitch/a-66-github-label-for-running-scenario-tests branch from 67cffac to 7bb68d7 Compare October 26, 2025 19:56

just-mitch added the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 26, 2025

AztecBot removed the ci-network-scenario Run network scenario tests using an image built from this PR label Oct 26, 2025

just-mitch closed this Jan 4, 2026

feat: ci-network-scenario label #17505

feat: ci-network-scenario label #17505

Uh oh!

Conversation

just-mitch commented Oct 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Add GitHub Actions for Network Scenario Tests on PRs

Uh oh!

just-mitch commented Oct 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Oct 4, 2025

✅ Network Scenario Tests PASSED

Uh oh!

github-actions bot commented Oct 4, 2025

❌ Network Scenario Tests FAILED

⚠️ Tests Failed

Uh oh!

github-actions bot commented Oct 4, 2025

❌ Network Scenario Tests FAILED

⚠️ Tests Failed

Uh oh!

github-actions bot commented Oct 16, 2025

❌ Network Scenario Tests FAILED

⚠️ Tests Failed

Uh oh!

github-actions bot commented Oct 16, 2025

❌ Network Scenario Tests FAILED

⚠️ Tests Failed

Uh oh!

PhilWindle Oct 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Oct 25, 2025

❌ Network Scenario Tests FAILED

⚠️ Tests Failed

Uh oh!

github-actions bot commented Oct 25, 2025

❌ Network Scenario Tests FAILED

⚠️ Tests Failed

Uh oh!

github-actions bot commented Oct 25, 2025

✅ Network Scenario Tests PASSED

Uh oh!

github-actions bot commented Oct 25, 2025

❌ Network Scenario Tests FAILED

⚠️ Tests Failed

Manual Cleanup Required

Uh oh!

github-actions bot commented Oct 26, 2025

❌ Network Scenario Tests FAILED

⚠️ Tests Failed

Manual Cleanup Required

Uh oh!

ludamad Oct 26, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Oct 26, 2025

❌ Network Scenario Tests FAILED

⚠️ Tests Failed

Manual Cleanup Required

Uh oh!

Uh oh!

github-actions bot commented Oct 26, 2025

✅ Network Scenario Tests PASSED

Manual Cleanup Required

Uh oh!

just-mitch commented Jan 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

just-mitch commented Oct 4, 2025 •

edited

Loading

just-mitch commented Oct 4, 2025 •

edited

Loading

PhilWindle Oct 20, 2025 •

edited

Loading