Repository navigation
Use 1M spikes for default stress tests; make 9M opt-in - #56
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ordinary browser runs and CI now stress-test 1M spikes and 100 cells. The 9M case is skipped unless
WAVEFORM_STRESS_9M=1is set explicitly; the demo URL also distinguishes?demo=stressfrom?demo=stress-9m.The stress test still verifies merge, exact undo/export round trips and restoring cut history across tetrodes. README and architecture notes document the opt-in command.
Validation: production build, ESLint, 20 unit tests, and the synthetic browser tests passed (three passed; the optional 9M case skipped).