Closed uu59 closed 8 years ago
This issue does not relate timezone. I also test UTC timezone.
% ruby -e 'puts Time.new.utc'
2016-07-27 08:44:00 UTC
test.dig
timezone: UTC
schedule:
daily>: "12:00:00"
+current_date:
sh>: echo `date`
digdag server -m
% digdag push test
2016-07-27 17:44:29 +0900: Digdag v0.8.5
Creating .digdag/tmp/archive-16238913803939729.tar.gz...
Archiving tasks/__init__.py
Archiving tasks/__init__.pyc
Archiving tasks/repeat_hello.sh
Archiving tasks/shell_sample.sh
Archiving test.dig
Workflows:
test
Uploaded:
id: 1
name: test
revision: 94598b48-8b0d-4d9d-965e-86eb59fedcc8
archive type: db
project created at: 2016-07-27T08:44:31Z
revision updated at: 2016-07-27T08:44:31Z
Use `digdag workflows` to show all workflows.
% digdag schedules
2016-07-27 17:44:39 +0900: Digdag v0.8.5
Schedules:
id: 1
project: test
workflow: test
next session time: 2016-07-28 00:00:00 +0000
next runs at: 2016-07-28 21:00:00 +0900 (27h 15m 20s later)
1 entries.
Use `digdag workflows [project-name] [workflow-name]` to show workflow details.
Fixed at v0.8.6. http://www.digdag.io/releases/release-0.8.6.html
Thanks!
I want to schedule at 2.5 hours later instead of 26.5 hours later.