-
Notifications
You must be signed in to change notification settings - Fork 12
Closed
Description
There are a couple of tests failing, precisely because jobq.start() [1], called without passing in job, can't find jobs pushed (jobq.push()) recently [2].
[1]
python-hubstorage/hubstorage/jobq.py
Lines 91 to 106 in 31525d3
| def start(self, job=None, **start_params): | |
| """Start a new job | |
| If a job is passed, it is changed to the started state and metadata | |
| updated with the start_params. Otherwise the next job is pulled from | |
| hubstorage, using the start_params which will be saved as metadata. | |
| If a 'botgroup' parameter is present in start_params, only jobs from | |
| that botgroup will be started. | |
| It may take up to a second for a previously added job to be available. | |
| """ | |
| if job: | |
| return self.update(job, state='running', **start_params) | |
| for o in self.apipost('startjob', jl=start_params): | |
| return o |
[2]
python-hubstorage/hubstorage/jobq.py
Lines 105 to 106 in 31525d3
| for o in self.apipost('startjob', jl=start_params): | |
| return o |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels