workflows: Schedule benchmark to run every few days #1035
Merged
Conversation
This file contains 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
The previous benchmark results are stored in the GitHub Cache, but cache entries are deleted if they are not accessed in over 7 days. And if the cache is empty, we will not detect that the rules are slower. So schedule the benchmark to run automatically every Tuesday and Friday at 05:00 in the morning, to avoid this deletion. It might also be helpful as a double-check. The scheduled run will be on the develop branch.
|
Merging without review, as it's a small change in the benchmark workflow. |
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.
The previous benchmark results are stored in the GitHub Cache, but cache entries are deleted if they are not accessed in over 7 days. And if the cache is empty, we will not detect that the rules are slower.
So schedule the benchmark to run automatically every Tuesday and Friday at 05:00 in the morning, to avoid this deletion. It might also be helpful as a double-check.
The scheduled run will be on the develop branch.