Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run twiggy in CI for wasm example targets #235

Open
anp opened this issue Jan 4, 2021 · 0 comments
Open

Run twiggy in CI for wasm example targets #235

anp opened this issue Jan 4, 2021 · 0 comments
Labels
dom Related to moxie-dom and associated crates
Milestone

Comments

@anp
Copy link
Owner

anp commented Jan 4, 2021

Some options for progressively fancier setup:

  1. just run twiggy top/twigger monos so the CI logs have the output
  2. download the main branch's equivalent binary and run twiggy diff
  3. use --format json -o $SOMEFILE and upload the file as an artifact
  4. use the JSON output as an input to a test that asserts some basic properties of code size for crates in this repo (e.g. "each topo::call produces <=N bytes of optimized output")

Ideally we can find out about the next instance of #234 as it's happening, rather than much later :D.

@anp anp added the dom Related to moxie-dom and associated crates label Feb 2, 2021
@anp anp added this to the moxie-dom 1.0 milestone Apr 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dom Related to moxie-dom and associated crates
Projects
None yet
Development

No branches or pull requests

1 participant