You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gate explicit container-topology tests behind an opt-in environment flag or
docker-backed topology settings so routine host-host e2e runs avoid the extra
Docker setup cost.
Keep the dedicated container e2e workflow and local container helper scripts
opted in explicitly.
Refines how the target is launched inside the selected target sandbox. Default: `same`.
211
211
`child-container` currently means "launch the target in a nested child container inside the outer `docker-private` sandbox".
212
+
-`E2E_RUN_CONTAINER_TOPOLOGY=1`
213
+
Enables the explicit `container_topology_execution` tests. These tests are skipped in routine host-host e2e runs unless this flag is set or a docker-backed `E2E_GHOSTSCOPE_SANDBOX`/`E2E_TARGET_SANDBOX`/`E2E_TARGET_MODE` is requested.
212
214
-`E2E_CHILD_CONTAINER_IMAGE=<image-ref>`
213
215
Overrides the image used for nested `child-container` targets. By default it inherits `E2E_CONTAINER_IMAGE`, so the outer sandbox and nested child container use the same runtime image unless you explicitly split them.
- These commands keep the Rust test harness on the host and move GhostScope plus the traced target into the requested container sandbox topology.
295
297
- When GhostScope and target use the same sandbox kind, the topology-aware e2e helper automatically reuses the same sandbox instance.
296
-
-The main `CI` workflow runs the full `ghostscope-e2e-tests` suite under the default host-host environment, including `container_topology_execution`.
298
+
-Routine host-host e2e, including the main `CI` workflow, skips the explicit `container_topology_execution` cases by default.
297
299
-`host -> docker-private`, `docker-private -> same docker-private`, and `docker-private -> child-container` are the explicit topology scenarios that currently run the full e2e suite in the dedicated `Container E2E` workflow.
298
300
-`docker-private -> child-container` uses `E2E_TARGET_MODE=child-container` and launches the target in a nested Docker child container inside the outer private sandbox. The full suite now runs in CI for that topology, while nested child-container `-t` cases still follow the existing explicit skip path inside the Rust tests.
299
301
-`docker-host -> same docker-host` remains a smoke run because it is close to the default host PID view.
0 commit comments