| commit | b32d9c6f7864fd5f3535110373d9cac500031aaa | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Dec 19 03:36:54 2024 |
| committer | Emscripten-releases LUCI CQ <emscripten-releases-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Dec 19 05:12:59 2024 |
| tree | d772bd61f5041c6fee5c676ff2c256790d1a95c0 | |
| parent | f359f18b6c85784b014490324982eefeb0e303dc [diff] |
Roll emscripten from f66b5d706e17 to 0186a3f32ae6 (14 revisions) https://chromium.googlesource.com/external/github.com/emscripten-core/emscripten.git/+log/f66b5d706e17..0186a3f32ae6 2024-12-19 sbc@chromium.org Disable test_fs_mkdir_dotdot on windows. NFC (#23223) 2024-12-19 sbc@chromium.org Convert `createWasm` async/await where possible (#23157) 2024-12-18 sbc@chromium.org Remove unnecessary `await` in `MODULARIZE=instance` mode. NFC (#23219) 2024-12-18 dschuff@chromium.org Enable WASM_BIGINT by default (#22993) 2024-12-18 sbc@chromium.org [ci] Fix "Check test expectations" step so it checks out the target branch (#23220) 2024-12-18 sbc@chromium.org Automatic rebaseline of codesize expectations. NFC 2024-12-18 roberthoodchatham@gmail.com Return EISDIR when trying to create a path ending in / with open (#23135) 2024-12-18 sbc@chromium.org Assert if `MODULARIZE` factory function is used with `new`. (#23210) 2024-12-18 roberthoodchatham@gmail.com Fix dup of pipe (#23217) 2024-12-18 sbc@chromium.org Micro-optimize PATH.basename. NFC (#23198) 2024-12-18 sbc@chromium.org Automatic rebaseline of codesize expectations. NFC 2024-12-18 sbc@chromium.org Add codesize test for EXPORT_ES6. NFC (#23215) 2024-12-18 roberthoodchatham@gmail.com Fix `mkdir("a/b/..")` should return `EEXIST` (#23136) 2024-12-18 sbc@chromium.org Avoid excessive variable reuse in `modularize` function. NFC (#23208) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/emscripten-emscripten-releases Please CC dschuff@google.com,wasm-waterfall@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: wasm-waterfall@grotations.appspotmail.com Change-Id: Ifeb97db3425d7a6a77a8eb4b10b435cd0c4dc81a Reviewed-on: https://chromium-review.googlesource.com/c/emscripten-releases/+/6109536 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
This is meta-repository which brings together all the repositories needed to produce an emscripten release. The revisions used in each release are tracked in a DEPS file (See depot_tools for more information). This file contains a history of revisions that have been built and tested together and represent a known good state.
Each release is automatically built and uploaded to to Google Cloud Storage and can be used standalone or with emsdk.
The build status for the automated builds can be seen here
Install depot_tools and then check out: gclient config https://chromium.googlesource.com/emscripten-releases (Do this only once)
Update working trees:
git pullgclient syncUpdate a DEPS entry:
cd emscripten-releasesgit checkout -b <branch>roll-dep emscripten-releases/llvm-projectgit cl uploadThe argument to roll-dep must match one of the keys in the ‘deps’ dictionary in the DEPS file. See roll-dep -h for more options.
src/This directory was forked from the WebAssembly waterfall repo That repo was retired because it was only used by emscripten-releases.
depot_tools. Follow the instructionspkg-config if you don't have it installed already, e.g. # apt install pkg-configpython src/build.pyBuild.py has 3 types of actions:
Each of these types has multiple steps (e.g. a build step for each component). If you run build.py with no arguments, it will run all the sync, build, and test steps. If you make a change and only want to run a subset of steps, you can apply filters from the command line, via exclusions (to prevent specified steps from running) or inclusions (to run only the specified steps). Sync, build, and test exclusions are specified separately. For example:
$ src/build.py --no-sync --build-exclude=llvm$ src/build.py --sync-include=binaryen --build-include=llvm,binaryen --test-exclude=emtest,emtest-asmThe script should throw an error if you specify nonexistent steps or if you specify both includes and excludes for the same type of action.
When run, the script creates a directory src/work inside the waterfall‘s git checkout. All modifications are made inside this directory (checking and out and building the sources, as well as the test builds and execution results). You can also use the git checkouts (e.g. src/work/llvm) with your own branches; the sync steps will check out the latest revision from the script’s remote repositories but will not overwrite or destroy any local work.