Skip to content
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.

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

release: unset SKIP_WASM_BUILD #7074

Merged

Conversation

iulianbarbu
Copy link
Contributor

@iulianbarbu iulianbarbu commented Jan 7, 2025

Description

Seems like I added SKIP_WASM_BUILD=1 💀 for arch64 binaries, which results in various errors like: #6966. This PR unsets the variable.

Closes #6966.

Integration

People who found workarounds as in #6966 can consume the fixed binaries again.

Review Notes

I introduced SKIP_WASM_BUILD=1 for some reason for aarch64 (probably to speed up testing) and forgot to remove it. It slipped through and interfered with stable2412 release artifacts. Needs backporting to stable2412 and then rebuilding/overwriting the aarch64 artifacts.

Signed-off-by: Iulian Barbu <iulian.barbu@parity.io>
@paritytech-review-bot paritytech-review-bot bot requested a review from a team January 7, 2025 12:06
@iulianbarbu iulianbarbu added R1-breaking_change This PR introduces a breaking change and should be highlighted in the upcoming release. I2-bug The node fails to follow expected behavior. and removed R1-breaking_change This PR introduces a breaking change and should be highlighted in the upcoming release. labels Jan 7, 2025
Signed-off-by: Iulian Barbu <iulian.barbu@parity.io>
@iulianbarbu iulianbarbu enabled auto-merge January 7, 2025 13:09
@iulianbarbu iulianbarbu added this pull request to the merge queue Jan 7, 2025
Merged via the queue into paritytech:master with commit a578052 Jan 7, 2025
203 of 205 checks passed
@iulianbarbu iulianbarbu deleted the ib-remove-skip-wasm-build branch January 7, 2025 16:11
@iulianbarbu iulianbarbu added the A4-needs-backport Pull request must be backported to all maintained releases. label Jan 8, 2025
@paritytech-cmd-bot-polkadot-sdk

Created backport PR for stable2407:

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-7074-to-stable2407
git worktree add --checkout .worktree/backport-7074-to-stable2407 backport-7074-to-stable2407
cd .worktree/backport-7074-to-stable2407
git reset --hard HEAD^
git cherry-pick -x a5780527041e39268fc8b05b0f3d098cde204883
git push --force-with-lease

@paritytech-cmd-bot-polkadot-sdk

Created backport PR for stable2409:

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-7074-to-stable2409
git worktree add --checkout .worktree/backport-7074-to-stable2409 backport-7074-to-stable2409
cd .worktree/backport-7074-to-stable2409
git reset --hard HEAD^
git cherry-pick -x a5780527041e39268fc8b05b0f3d098cde204883
git push --force-with-lease

@paritytech-cmd-bot-polkadot-sdk

Git push to origin failed for stable2412 with exitcode 1

@iulianbarbu iulianbarbu had a problem deploying to subsystem-benchmarks January 8, 2025 08:09 — with GitHub Actions Failure
EgorPopelyaev pushed a commit that referenced this pull request Jan 8, 2025
# Description

Unsets SKIP_WASM_BUILD which was introduced by mistake for aarch64
binaries release: #7074.

## Integration

Aarch64 binaries can be consumed as the x86_64 ones.

## Review Notes

Details on #7074 .

---------

Signed-off-by: Iulian Barbu <iulian.barbu@parity.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A4-needs-backport Pull request must be backported to all maintained releases. I2-bug The node fails to follow expected behavior.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error: Rococo development wasm not available
4 participants