Skip to content

Add a workflow that records the Windows heap order on GitHub's runner - #29

Merged
opensec-intelligence merged 1 commit into
pi-boltfrom
heap-profile-workflow
Oct 15, 2026
Merged

opensec-intelligence merged 1 commit into
pi-boltfrom
heap-profile-workflow

Conversation

@opensec-intelligence

Copy link
Copy Markdown
Member

Adds heap-profile, a manual workflow that runs scripts\train-heap.ps1 on GitHub's windows-2025 runner, so a new Pi version's Windows heap order no longer needs a local Windows machine.

  • runtime (ubuntu): reads the Pi version, checks profiles/pi-X.Y.Z/bytecode.order exists, and requires scripts/runtime-stamp.sh to equal the latest release's RUNTIME_STAMP, taken from its signed SHA256SUMS.
  • train (windows-2025): the setup of release.yml's Windows job (AVX2 check, py shim, the release's runtime checked against its signed checksums, npm ci, npm run build:offline), then scripts\train-heap.ps1; uploads profiles/pi-X.Y.Z as an artifact.
  • branch (ubuntu, contents: write): commits the artifact and pushes heap-profile/pi-X.Y.Z. The pull request is opened by hand, since one opened with the workflow's token would not run ci.

docs/RELEASING.md step 2 of "A new Pi version" mentions it.


Generated by Claude Code

heap-profile runs scripts\train-heap.ps1 on windows-2025 with the latest release's runtime (when its signed RUNTIME_STAMP is this commit's), uploads profiles/pi-X.Y.Z as an artifact and pushes it to heap-profile/pi-X.Y.Z.
@opensec-intelligence
opensec-intelligence merged commit f0c8c64 into pi-bolt Oct 15, 2026
10 checks passed
@Kushalkhemka
Kushalkhemka deleted the heap-profile-workflow branch October 20, 2026 07:37
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.

2 participants