spec_test_runner.ts: sort document changes before comparing for correctness #7020
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.
When comparing document changes for correctness in spec tests, the lists of changes in the actual and expected results were assumed to be ordered the same; however, they are not necessarily ordered in the same manner. Since order doesn't actually matter, this PR fixes potential future problems with sort order mismatches by sorting both of them using the same comparator.
Credit for this PR goes to @milaGGL from #6897. I'm merely merging a small component of that PR into the master branch to reduce the diff when her PR ultimately gets merged.