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
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
With switch to new Substrate version we started hitting space limits in GitHub Actions CI.
Turned out, wasm-opt-sys contributes a lot and generally with growing number of runtimes size of wbuild becomes a growing challenge.
It would be very helpful to be able to control whether wasm-builder can delete corresponding target after building WASM files (that are the only ones needed AFAK in the end). This would allow to use such a flag in CI because runtimes there are compiled once and never change.
The text was updated successfully, but these errors were encountered:
With switch to new Substrate version we started hitting space limits in GitHub Actions CI.
Turned out,
wasm-opt-sys
contributes a lot and generally with growing number of runtimes size ofwbuild
becomes a growing challenge.It would be very helpful to be able to control whether wasm-builder can delete corresponding
target
after building WASM files (that are the only ones needed AFAK in the end). This would allow to use such a flag in CI because runtimes there are compiled once and never change.The text was updated successfully, but these errors were encountered: