You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the work on the wasm32 architecture, we'd like to add a new builder for running the wasip1 tests. This builder will need to have wasmtime installed and set the following environment variables:
GOARCH should be wasm32 instead of wasm, is that right?
Related to the above—will GOROOT/misc/wasm be used for both wasm and wasm32 exec helpers? That seems good to me, just confirming.
GO_DISABLE_OUTBOUND_NETWORK is an internal implementation detail of the old build system, no need to set it for this builder in LUCI.
If the above is right, the definition of this builder in main.star will be very similar to the wasip1-wasm_wasmtime builder. There'll be a few places to consider wasm32 architecture value in addition to wasm, both in main.star (e.g., here and here) and in golangbuild (e.g., here), maybe by checking for their common "wasm" prefix.
dmitshur
changed the title
x/build: add LUCI wasip1-wasm32-wasmtime builder
x/build: add LUCI wasip1-wasm32_wasmtime builder
Apr 7, 2024
As part of the work on the wasm32 architecture, we'd like to add a new builder for running the wasip1 tests. This builder will need to have wasmtime installed and set the following environment variables:
CC @dmitshur
The text was updated successfully, but these errors were encountered: