Skip to content

Conversation

ntn-x2
Copy link
Contributor

@ntn-x2 ntn-x2 commented Dec 2, 2024

If I try to specify a different RUSTC version than the one the container was built with, I guess an error when compiling the runtime: Cannot compile the WASM runtime: the wasm32-unknown-unknown target is not installed!. The link to the failing Gitlab pipeline is here: https://gitlab.com/kiltprotocol/kilt-node/-/jobs/8516236006.

If I try to add the relevant rustup instruction myself in the image setup step, I get the error /usr/bin/bash: line 166: rustup: command not found. A link to the failing pipeline is here: https://gitlab.com/kiltprotocol/kilt-node/-/jobs/8516444684.

Hence I believe the fix is to add the wasm32-unknown-unknown target by default after overriding the rustc info.

@ntn-x2 ntn-x2 force-pushed the aa/wasm-target-install branch from db14630 to 7d35603 Compare December 2, 2024 08:57
@ntn-x2
Copy link
Contributor Author

ntn-x2 commented Dec 5, 2024

Cc @chevdor and @EgorPopelyaev

alvicsam added a commit that referenced this pull request Feb 24, 2025
EgorPopelyaev added a commit that referenced this pull request Feb 25, 2025
* Update uploadt-artifact to v4

* update action/cache

* test

* bumping rustc_version to 1.84

* add wasm32v1-none

* keep 1.81 for fellowship

* add wasm32-unknown-unknown to srtool run

* try suggestion from #90

* Bump srtool version

---------

Co-authored-by: alvicsam <[email protected]>
Co-authored-by: EgorPopelyaev <[email protected]>
@EgorPopelyaev
Copy link
Contributor

@ntn-x2 sorry for this delay, we merged your changes with this pr: #92
So I'll colse this one

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