Make missing test case check more granular #2210
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
… benchmark parameters
Jamesbarford
requested changes
Jul 29, 2025
|
Second attempt, let's see what happens in production.. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is a reland of #2161, which was reverted in #2187. I fixed the issue with recomputing incremental doc builds, and also made sure that when something is recomputed, the corresponding step won't be restarted from scratch (
start_time), to avoid weirdly short steps (now they will be weirdly long instead, but that's good, as it can tell us on the status page that some recomputation happened).This will be needed soon for the new benchmarking scheme.