test(envdsmoke): the e2b flavor's envd smoke lives with the e2b layer - #81
Merged
Merged
Conversation
The harness that drives the e2b flavor image's envd through the guest-port relay moves here from the sandbox repo, rewritten on pkg/sandboxd: sandbox keeps no envd knowledge, and what the smoke asserts (the version the compat API reports, the Connect surface, the default user, HTTP/1.1 only) is what this repo's e2b surface and envd proxy depend on. The silkd read-back of an envd upload becomes an envd read-back; the service-active check is envd's own /health.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves the envd hardware smoke from sandbox (e2e/cmd/envdsmoke, scripts/envd-e2e.sh) into this repo as
test/envdsmoke(build tagenvdsmoke, listed in TAGGED_HARNESSES) andscripts/envd-e2e.sh, rewritten onpkg/sandboxdinstead of the sandbox Go SDK: claim, then every check through the guest-port relay against the real envd (health, version, POST/GET /files, a Connect unary, process start over the server stream, the user account with sudo via the process API, HTTP/1.1 only, optional code-interpreter 1+1, -hold). Docs: "Proving envd on hardware" in e2b-compat.md. Companion: sandbox PR removing the old harness (CMGS 2026-09-28: sandbox has no envd concept).