Clone this repo:
  1. 2d85553 Add test for SIMD operations compiled to intrinsic instructions. (#212) by Rebecca G. Bettencourt · 9 days ago master
  2. 92cd5a6 Make JSC build failure not abort the whole process (#223) by Heejin Ahn · 5 weeks ago
  3. 240cabe Bring back gnuwin32 tools for preparing musl sources on Windows (#222) by Derek Schuff · 5 weeks ago
  4. f6e093d Update expectations for lld tests (#221) by Sam Clegg · 5 weeks ago
  5. cb00ec5 Update lld git url to (#220) by Sam Clegg · 5 weeks ago


༼ ༎ຶ ෴ ༎ຶ༽ If it’s not tested, it’s already broken.

Luckily, this repository has some tests: Build Status

What's this?

This repository holds the code which make the WebAssembly waterfall‘s heart beat. You may want to see the waterfall in action, and if you don’t like what you see you may even want to contribute.

What's a waterfall?

WebAssembly has many moving parts and no central owner. Some of these interact closely, some implement the same thing. A build and test waterfall allows us to:

  • Have simple build instructions for each component.
  • Archive build logs and build artifacts.
  • Identify which build artifacts are known-good.
  • Know which tests matter.
  • Make tests easily executable.
  • Know which configurations matter (build flavor, host OS, host architecture, ...).
  • Cause inadvertent breakage less often.
  • When breakage occurs, identify it quickly and reverted / silenced / fixed easily.
  • When a big change is required, know which moving parts should synchronize.
  • Make the feature implementation status straightforward to check for each component.

We should keep process to a minimum, try things out, see what works.