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
I recently open a PR to add a new Wasm Workers Server shim. When adding this new feature, I notice the CI time is growing consistently with every new shim due compilations and other required steps.
Comparing the builds in the different repos, the wws adds around +10 minutes of compilation times. And this may grow with new shims in the future.
I don't have any proposal as I didn't check the CI pipelines in depth. For now, I created this issue for tracking purposes :)
The text was updated successfully, but these errors were encountered:
In the previous community meeting we discussed about stop using cross and rely on containers for it. I would like to give it a try with Wasm Workers Server and extend it later to the rest of the shims :)
Hello 馃憢
I recently open a PR to add a new Wasm Workers Server shim. When adding this new feature, I notice the CI time is growing consistently with every new shim due compilations and other required steps.
Comparing the builds in the different repos, the
wws
adds around +10 minutes of compilation times. And this may grow with new shims in the future.I don't have any proposal as I didn't check the CI pipelines in depth. For now, I created this issue for tracking purposes :)
The text was updated successfully, but these errors were encountered: