Skip to content

ci: add e2e tests against the real cache service - #4

Draft
janakiram7755 wants to merge 2 commits into
feat/test-harnessfrom
feat/e2e-tests
Draft

ci: add e2e tests against the real cache service#4
janakiram7755 wants to merge 2 commits into
feat/test-harnessfrom
feat/e2e-tests

Conversation

@janakiram7755

Copy link
Copy Markdown
Collaborator

Stacked on #3. First CI here that runs warp-cache against the real cache service, on warp runners.

10 jobs: save + restore across x64/arm64/macOS in separate jobs, restore-key fallback, miss-returns-undefined, lookupOnly writing nothing, cross-arch both directions, behind a proxy, and default-branch restore. A preflight fails loudly if isFeatureAvailable() is false so a misconfigured runner cannot produce a green run that tested nothing.

Ported from the workflow that got 21 green in the old fork, adapted for ESM — every node -e "require(...)" became node --input-type=module -e "await import(...)" — and for the repo root layout.

Expect the two cross-arch restore jobs to fail: the equivalent jobs fail on WarpBuilds/cache@main today (save succeeds, restore 404s). Included deliberately so the bug is covered rather than invisible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant