Skip to content

release.yml: nasm on Windows runners that lack it - #146

Merged
shinyobjectz merged 1 commit into
mainfrom
win-nasm
Nov 13, 2026
Merged

shinyobjectz merged 1 commit into
mainfrom
win-nasm

Conversation

@shinyobjectz

Copy link
Copy Markdown
Owner

rc3's dry run on Namespace's Windows runner stopped after 3 minutes: rav1d's build script couldn't find nasm. GitHub's Windows image has it, Namespace's windows-2022 doesn't. An inventory of that image (cmake, ninja, jq, perl, python, git, bash, choco, rustup, clang, ImageMagick, 7z, node, VS 2022 all there) found nasm the only missing tool. The step installs it with Chocolatey, else from NASM's own zip.

…hocolatey, else NASM's zip). rav1d's build script runs nasm; GitHub's Windows image has it and Namespace's doesn't, so rc3's dry run on Namespace stopped there after 3 minutes. An inventory of Namespace's windows-2022 image found nasm the only missing tool the build uses
@shinyobjectz
shinyobjectz merged commit cceec65 into main Nov 13, 2026
4 checks passed
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