Bug 1347889 - use 'relative-datestamp' instead of typo 'relative-timestamp' in morphs, to unbreak task submission. r=dustin

MozReview-Commit-ID: 8GCKi6r4WUD

--HG--
extra : rebase_source : 511a7d54d23133b255d364b87207244d4cff7775
This commit is contained in:
Justin Wood 2017-03-16 09:44:36 -04:00
parent f7296422da
commit 54a5d59c87
2 changed files with 2 additions and 2 deletions

View File

@ -190,7 +190,7 @@ using simple parameterized values, as follows:
``{"relative-datestamp": "certain number of seconds/hours/days/years"}``
Objects of this form will be replaced with an offset from the current time
just before the ``queue.createTask`` call is made. For example, an
artifact expiration might be specified as ``{"relative-timestamp": "1
artifact expiration might be specified as ``{"relative-datestamp": "1
year"}``.
``{"task-reference": "string containing <dep-name>"}``

View File

@ -57,7 +57,7 @@ def derive_misc_task(task, purpose, image, taskgraph, label_to_taskid):
'provisionerId': 'aws-provisioner-v1',
'workerType': 'gecko-misc',
'dependencies': [task.task_id, image_taskid],
'created': {'relative-timestamp': '0 seconds'},
'created': {'relative-datestamp': '0 seconds'},
'deadline': task.task['deadline'],
# no point existing past the parent task's deadline
'expires': task.task['deadline'],