Skip to content

ci: cache the pooch example datasets on the e2e jobs #128

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
CSSFrancis merged 1 commit into from
Aug 9, 2026
+14 −0
Merged

ci: cache the pooch example datasets on the e2e jobs #128

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 14 additions & 0 deletions .github/workflows/build.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -308,6 +308,20 @@ jobs:
working-directory: electron
run: npx playwright install --with-deps chromium

# Example datasets (pyxem's sped_ag) download through pooch with a
# checksum on first use; three slow-slice specs load it, so uncached
# runners re-fetch it from Zenodo every run — slow, and a stalled
# download eats the spec's whole budget (the hyperspy orgs cache the
# same way, e.g. hyperspy/.github's pooch-cache workflows). Keyed on
# the lock so a pyxem bump re-saves; restore-keys keeps it warm across
# unrelated dependency changes (pooch re-verifies checksums on load).
- name: Cache example datasets (pooch)
uses: actions/cache@v4
with:
path: ~/.cache/pyxem
key: pooch-pyxem-${{ hashFiles('uv.lock') }}
restore-keys: pooch-pyxem-

- name: Run Electron e2e
working-directory: electron
env:
Expand Down
Loading