🤖 perf: speed up CI with approx tokenizer and parallel static-check #962
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Speeds up CI by:
length/4token counting instead of loading the 10s WASM tokenizer-j3limit, allowing all 6 subtasks to run in parallelChanges
Tokenizer (
src/node/utils/main/tokenizer.ts)shouldUseApproxTokenizer()that checksMUX_APPROX_TOKENIZER=1MUX_FORCE_REAL_TOKENIZER=1for tests needing real tokenizationTest setup (
tests/setup.ts)MUX_APPROX_TOKENIZER=1in JestCI (
.github/workflows/pr.yml)make -j static-check(was-j3)fetch-depth: 0from test-unit, test-integration, test-storybook, test-e2eTest fix (
src/cli/run.test.ts)vX.Y.Zand hash-only formats (shallow clones don't have tags)Generated with
mux