Skip to content

(MOT-4299) fix(ci): unbreak cold registry-lane harness e2e builds #739

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ytallo merged 2 commits into from
Aug 7, 2026
Merged

(MOT-4299) fix(ci): unbreak cold registry-lane harness e2e builds #739

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cb4b6ca
fix(ci): save the plain harness-e2e rust cache
ytallo Aug 7, 2026
be6a71b
fix(ci): set up pnpm for registry-lane e2e builds
ytallo Aug 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions .github/workflows/_harness-e2e.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,15 +179,14 @@ jobs:
with:
ref: ${{ inputs.source_ref }}

# state/build.rs builds its embedded UI when the checked-out assets are
# stale, so the isolated E2E build needs the same Node/pnpm toolchain as
# the regular CI worker builds.
# state/build.rs and harness/build.rs build their embedded UIs when the
# checked-out assets are stale, and the harness crate compiles in every
# stack mode (Test/Lint E2E crate), so both lanes need the same
# Node/pnpm toolchain as the regular CI worker builds.
- name: Setup pnpm
if: inputs.stack_mode == 'source'
uses: pnpm/action-setup@v5

- name: Setup Node
if: inputs.stack_mode == 'source'
uses: actions/setup-node@v5
with:
node-version: 22
Expand Down Expand Up @@ -294,9 +293,11 @@ jobs:
uses: Swatinem/rust-cache@v2
with:
# Instrumented builds have different fingerprints; keep them on their
# own key so coverage runs never poison the normal cache.
# own key so coverage runs never poison the normal cache. Both lanes
# save their own key: with coverage-only saving, the plain key was
# never written and every registry-lane build compiled from scratch.
shared-key: ${{ inputs.coverage && 'harness-e2e-coverage' || 'harness-e2e' }}
save-if: ${{ inputs.coverage }}
save-if: true
workspaces: |
harness -> target
database -> target
Expand Down
Loading