You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When anyone changes compiler-related code, the numbers in symbolic-examples:bench-compiler are bound to change.
Should we add the golden test run to CI to track changes?
The text was updated successfully, but these errors were encountered:
Rather than golden tests, why not run symbolic-examples:bench-compiler in CI right after linting and before auto-committing? Then optimizations and regressions will show up in PRs and we can pull them from remote. It may be a little less to write and help shorten the dev cycle.
Edit: Now I think probably that's exactly what you mean!
When anyone changes compiler-related code, the numbers in
symbolic-examples:bench-compiler
are bound to change.Should we add the golden test run to CI to track changes?
The text was updated successfully, but these errors were encountered: