Page MenuHomePhabricator

[spike] install-rust && wasmedge build inconsistent and fails depending on env
Open, MediumPublic

Description

What/Why:
In the function-evaluator, we build two images, one for WASM quickJS and python. These do not build successfully often exiting from Segmentation 103 error at rustup target add wasm32-wasi command during installation. On my MacOS M2, I run into this issue, however on Cory's machine, the build finishes fine. We should update these commands or at least indicate alternatives in the blubber.yml so to cater to our respective environment.

How:

  1. Document findings
  2. Adjust build commands in blubber as needed (?)

Event Timeline

It seems however that just running the less secure cmds install-rust && install-wasmedge-rustpython run better, and even "chmod +x /usr/local/bin/install-rust /usr/local/bin/install-wasmedge-rustpython && install-rust && install-wasmedge-rustpython" (the same goes for quickJS). Perhaps this could mean something unhappy occurs during the compile-wasm-binary and/or delete-rust-cruft because the current command on main is:

"chmod +x /usr/local/bin/install-rust /usr/local/bin/install-wasmedge-rustpython /usr/local/bin/compile-wasm-binary /usr/local/bin/delete-rust-cruft && install-rust && install-wasmedge-rustpython && compile-wasm-binary && delete-rust-cruft"