Repository navigation
Speed up test diff and timing calculations - #4239
Merged
Merged
Conversation
When CDash processes test results, it compares each test with the same test in the previous build. That comparison is used to count new passes and failures and to update test timing statistics. Both steps searched the previous build's whole test list for every test, so processing slowed down sharply as the number of tests grew. This change builds a lookup by test name once and uses it instead. In benchmarks of the comparison loops, a build with 5,000 tests went from 26 s to 13 ms.
josephsnyder
approved these changes
Nov 18, 2026
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.
When CDash processes test results, it compares each test with the same test in the previous build. That comparison is used to count new passes and failures and to update test timing statistics. Both steps searched the previous build's whole test list for every test, so processing slowed down sharply as the number of tests grew.
This change builds a lookup by test name once and uses it instead. In benchmarks of the comparison loops, a build with 5,000 tests went from 26 s to 13 ms.