Track the runtime of PROCESS regression tests#4092
Open
timothy-nunn wants to merge 1 commit intomainfrom
Open
Conversation
timothy-nunn
force-pushed
the
track-runtime
branch
from
ab8c22f to
a02d97c
Compare
timothy-nunn
force-pushed
the
track-runtime
branch
from
a02d97c to
b56e6ac
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4092 +/- ##
==========================================
- Coverage 46.49% 46.49% -0.01%
==========================================
Files 124 124
Lines 28955 28961 +6
==========================================
+ Hits 13464 13465 +1
- Misses 15491 15496 +5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
3 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.
There has been some desire to track the runtime of PROCESS so we can reason about the speed impact of pull requests. Obviously, this tracking won't be perfect and we expect reasonable fluctuations depending on the GitHub runner, the load of the runner, and other random factors. However, it will shows us the trend and will be able to flag any drastic changes.