[move][coverage] Improve performance of coverage map generation#25901
Open
tzakian wants to merge 1 commit intotzakian/sparse-tracing2from
Open
[move][coverage] Improve performance of coverage map generation#25901tzakian wants to merge 1 commit intotzakian/sparse-tracing2from
tzakian wants to merge 1 commit intotzakian/sparse-tracing2from
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
35a3a14 to
11ff3a2
Compare
awelc
approved these changes
Mar 19, 2026
1b3dbdf to
c201871
Compare
11ff3a2 to
059fc58
Compare
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.
Description
This parallelizes the creation of a coverage map from a
tracedirectory, greatly speeding up coverage generation (drops e.g., generation on the move-stdlib from ~19s to ~1.7s)Test plan
CI + local testing
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.