Clone this repo:
  1. 637a22a Switch to (#191) by Sam Clegg · 2 days ago master
  2. 76717ec Fix spelling and grammar in comment (#190) by Sam Clegg · 8 days ago
  3. 2ae4b4d Ensure git URLs end in '.git' by Sam Clegg · 9 days ago
  4. dba2fdb Switch to pulling llvm from directly until llvm mirror is fixed. (#189) by Sam Clegg · 9 days ago
  5. 23fedbd Use 'main' consistently for python entry point name (#188) by Sam Clegg · 10 days 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.