Execution time tracking tweaks #1994
Merged
Commits on Aug 6, 2024
-
tweaks to how execution time is tracked:
- don't update if crawl state is not in running state - reset lastUpdatedTime if two consecutive updates of non-running state, to ensure non-running states don't count - webhooks: move start webhook to when crawl actually starts for first time (db lastUpdatedTime is not yet + crawl is running) - don't set lastUpdatedTime until pods actually running - frontend: show seconds in 'Execution Time' display
-
rename STARTING_STATES -> WAITING_STATES for clarity
don't count execution time when in WAITING_STATES
-
qa runs: use qa._lut to track qa last update time, to avoid conflicti…
…ng with crawl last update time, properly detecting when it hasn't been set yet
-
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.