Closed mweinelt closed 1 year ago
It is flaky it seems.
given that this fails at, say, 4am localtime, and editing that hour=5 to hour=3 makes it pass instantly, and editing it back to =5 makes it consistently fail, i assume that is just setting current_date.hour, and so it is not 'in the past' as what it tries to test, and so doesn't fail as it's not invalid to schedule something just slightly in the future from localtime.
i could also be misunderstanding what it means, but based on the behaviour it seems to explain why it fails at a certain time of day
This has been resolved in #563. Thanks to everyone here for reporting and debugging! :rocket:
After upgrading to 1.1.0 we see the following test fail:
It was introduced in https://github.com/dbader/schedule/commit/1849e0165278f1cdfaf41972f73e02ecda4d09a6.