tree 7b96ff87e401362a3a9f599b35f98c07eee11e8a
parent 65d829368583f9ad2610785b02905231c108ef87
author Scott Todd <scotttodd@google.com> 1664388074 -0700
committer GitHub <noreply@github.com> 1664388074 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJjNIvqCRBK7hj4Ov3rIwAAuOQIAExBhQZEaKFgJumirINISEJQ
 k+JD5QQfpEX5kHO8EYbwyCPfnjvoy9zOHJePf86yU/Hwpy2LGeK9K78Fn4/CgSpL
 s4TOeq32MZCBnSvjEZvhziZLhYu3J7pi/wMqV24X4UOGidr5ghaMDDGKKluJxD3l
 eq8S/5OM0eH3sJHo8R4xYIiT7QOgQXeK1YGIeTnrslrsunb52axrRlCh8hJD6fMX
 AEterR9hza5sGFoXzgAM9Bt0N3mfpenerruiVLsdSu6U1OPQhWVxp1yCBwW08GUp
 R4DbXTKz9eDzBINPZhtNa3Msqma5I/Odj2gFOLZjEesQnFBCICc2P16uCqTKme8=
 =QtFi
 -----END PGP SIGNATURE-----
 

Test runtime Emscripten builds. (#10319)

Progress on https://github.com/iree-org/iree/issues/9855

* Update Emscripten SDK in our Dockerfile
* Delete the Buildkite wasm runtime job (and prerequisite host install
job)
* Add a new `emscripten` job to ci.yml (GitHub Actions post-submit for
now, pre-submit later)

This currently just builds the runtime (and `iree-test-deps`) using
Emscripten. Running tests or building the samples at
[`experimental/web`](https://github.com/iree-org/iree/tree/main/experimental/web)
will come later (likely as that code gets promoted to
[`runtime/bindings/`](https://github.com/iree-org/iree/tree/main/runtime/bindings)
in some way)

I also posted an RFC for this and future work: [Promoting IREE web
platform / Emscripten builds to
"stable"](https://groups.google.com/g/iree-discuss/c/2K5VJ9P8K8I/m/elidhfFMCAAJ)