Fix: GitHub schedules are consistent late #16
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
We depend that the GitHub Actions triggers within 15 minutes of the requested time, as otherwise the 17:45 run will happen in 18:NN. This in result means our TimeZone detection things it is the run of 18:45, and makes the wrong choice. Sadly, reality shows GitHub schedules workflows often more than 15 minutes after the requested time. So .. just run eints a bit earlier, hopefully avoiding this issue. For sure it won't drift 30 minutes now would it?! (famous last words).
glx22
approved these changes
Mar 22, 2021
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.
We depend that the GitHub Actions triggers within
15 minutes of the requested time, as otherwise
the 17:45 run will happen in 18:NN. This in result
means our TimeZone detection things it is the run
of 18:45, and makes the wrong choice.
Sadly, reality shows GitHub schedules workflows
often more than 15 minutes after the requested
time. So .. just run eints a bit earlier, hopefully
avoiding this issue. For sure it won't drift 30
minutes now would it?! (famous last words).