What happened to binary releases?

[cmichi]

In the past you had always attached the binary build for various platforms to a release. What's the reason for stopping in the latest release?

This impacts us, since we used these binary releases in our CI setup. I only noticed that they no longer exist since our CI broke.

Moreover, we often recommended installing the binary release directly in our community. A number of stable Linux distributions still contain ancient binaryen releases, so this was an easy way to get the latest release for e.g. Ubuntu LTS (IIRC).

Yeah, so would be great if you could add them back :-).

[kripken]

I don't think we changed anything intentionally, but yes, the new version 102 lacks binaries.

Looks like builds failed:

https://github.com/WebAssembly/binaryen/actions/runs/1222083042

I'm not very familiar with github actions so those errors don't immediately suggest anything to me...

@sbc100 any ideas?

[sbc100]

Looks like the "upload-release-asset" step is failing for each of the builders.

binaryen/.github/workflows/build_release.yml

Lines 69 to 77 in 5b90e03

	- name: upload tarball
	uses: actions/upload-release-asset@v1
	env:
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
	with:
	upload_url: ${{ github.event.release.upload_url }}
	asset_path: ./${{ steps.archive.outputs.tarball }}
	asset_name: ${{ steps.archive.outputs.tarball }}
	asset_content_type: application/gzip

I have no clues yet as to why.

[maurolacy]

Looks like a temporary failure to me. I would just retry it, at least once.

[cmichi]

Just noticed that another release was created today and the GHA failed for that one as well: https://github.com/WebAssembly/binaryen/actions/runs/1233610300.

[sbc100]

Indeed, looks like the upload recipe we were using has become unmaintained: #4151

[sbc100]

Well I tried 3 different alternative github action and they all failed in different ways :(

For now I guess we could download the aritfacts form the CI builder and then upload them manually to the release.. :(

[sbc100]

You can find the CI artifacts here: https://github.com/WebAssembly/binaryen/actions/runs/1222068571

Do those work for you?

[maurolacy]

Looks like a timeout error or so.

Lots of info / workarounds here and here (notice these are pretty old). Didn't find anything conclusive on how to fix this, though.

[maurolacy]

You can find the CI artifacts here: https://github.com/WebAssembly/binaryen/actions/runs/1222068571

Do those work for you?

Not for us, as we are interested in the alpine-based build. I guess we'll switch to compiling our own version for both archs (Amd64 and Arm64).