You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to test a sensor, that checks if a job has run successfully today. The definition of "today" may depend on timezones. Hence I want to fake a situation where a job runs close to a day switch and in one tz has already run but not in the other. However the creation_timestamp of the RunRecord wont be faked correctly.
What did you expect to happen?
The first assertion in test_job_run_today_with_tz_gap should pass, but it does not. The creation_timestamp of the run record will be the current datetime e.g. FakeDatetime(2024, 5, 16, 14, 47, 34)
Dagster version
1.7.4
What's the issue?
I am trying to test a sensor, that checks if a job has run successfully today. The definition of "today" may depend on timezones. Hence I want to fake a situation where a job runs close to a day switch and in one tz has already run but not in the other. However the creation_timestamp of the RunRecord wont be faked correctly.
What did you expect to happen?
The first assertion in test_job_run_today_with_tz_gap should pass, but it does not. The creation_timestamp of the run record will be the current datetime e.g. FakeDatetime(2024, 5, 16, 14, 47, 34)
How to reproduce?
Deployment type
None
Deployment details
No response
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
The text was updated successfully, but these errors were encountered: