times_run doesn't count when using at: option about clockwork-test

[kevin-j-m]

Hi there,

I believe your issue is your value for tick_speed. I pulled down your example, changed the tick_speed to 1.hour, and the test passes.

The reason for this is because if you set the tick speed to a day, it'll only evaluate once per day; however, the time it runs will be based on your current time. Given this test setup, I believe that's 23:00. The job you're looking to verify shouldn't run at 23:00, which is why it fails with the at and does run without it.

The README for tick_speed mentions:

Note that tick_speed should not be set any higher than the minimum amount of granularity used in the clock file under test. Should the tick_speed be set to a higher amount, the number of times a job is run, or if the job is run at all, is subject to inconsistent and inaccurate results.

For example, with a tick_speed of 30.minutes and a job that runs every 1.minute over the course of an hour, the times_ran for that job will not be 60. It will be 2, assuming minimal passage of time in evaluating the actual clock tick.

I would welcome and appreciate any documentation PRs to clarify that if you have suggestions for how to improve upon that.

Let me know if that works for you and makes sense. Thanks!

[kevin-j-m]

@tiendo1011 did that clear anything up?

[kevin-j-m]

I'm closing this due to inactivity. Please let me know if you're still having an issue I can help with.