decrease frequency of test duration update workflow #13016
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
k-a-il
approved these changes
Aug 18, 2025
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.
Motivation
#12748 introduced a workflow to automatically update our test duration records (used to split the tests across parallel runners). The cron trigger was meant to trigger every month, but instead triggers every week:
Unfortunately, cron schedules don't easily allow a "on the first Monday of the month" schedule.
@k-a-il @silv-io It would also be great if we could move this functionality to the
localstack/metarepo and reuse it in other repositories, like our LocalStack Pro codebase. Are there any plans for that? 🤩Changes
CODEOWNERSfor these files.