8000 test(minvmd): give the vm_escape harness a package source for its boxes · Issue #1819 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

test(minvmd): give the vm_escape harness a package source for its boxes #1819

Closed

Description

@norrietaylor

Problem

crates/minvmd/tests/vm_escape_integration.rs (vm_escape_bounded_to_resident_union) has never executed its body: until #1815 it returned early whenever MINVMD_GVPROXY_BIN was unset, which is every lane. With the switch provisioned it fails on both VM lanes and locally at vm_escape_integration.rs:1147 ("box-a CapEff read exited nonzero").

The exec's stderr, which BoxSession::exec drops, says why:

minimald: failed to spawn process: session spawn: no such package: base

A shell exec runs /usr/bin/bash -c inside the session sandbox, and launching that sandbox resolves the baseline packages (base, coreutils, socat, plus bash) against the project's package graph. The harness uploads a task-only minimal.toml with no [upstream] (copied from minimald_session_integration.rs, which only runs an echo task that never spawns a sandbox), so the graph is empty.

Adding the pinned [upstream] moves the failure to git clone https://github.com/gominimal/pkgs: Could not resolve host: github.com in the harness boot (locally).

Wanted

The harness gives the box a package graph without depending on a live GitHub clone inside the guest: a seeded or offline package source (cache disk or prebuilt base/coreutils/socat/bash layer), or proven guest egress plus the pinned upstream with a cache. BoxSession::exec surfaces the exec's stderr on failure so the next failure names its cause.

Related

  • #1815 makes the VM harnesses run for real under MINVMD_E2E=1.
  • #1792 added the test.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0