| Home | Trees | Indices | Help |
|
|---|
|
|
object --+
|
uws.UWSTransitions --+
|
uws.SimpleUWSTransitions --+
|
uws.ProcessBasedUWSTransitions --+
|
TAPTransitions
The transition function for TAP jobs.
There's a hack here: After each transition, when you've released your lock on the job, call checkProcessQueue (in reality, only PhaseAction does this).
| Instance Methods | |||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
Inherited from Inherited from Inherited from Inherited from |
|||
| Properties | |
|
Inherited from |
| Method Details |
x.__init__(...) initializes x; see help(type(x)) for signature
|
|
puts a job on the queue.
|
pushes a job to an error state. This is called by a worker; leaving the error message itself is part of the worker's duty.
|
|
tries to kill/abort job. Actually, there are two different scenarios here: Either the job has a non-NULL startTime. In that case, the child job is in control and will manage the state itself. Then kill -INT will do the right thing. However, if startTime is NULL, the child is still starting up. Sending a kill -INT may do many things, and most of them we don't want. So, in this case we kill -TERM the child, do state management ourselves and hope for the best.
|
| Home | Trees | Indices | Help |
|
|---|
| Generated by Epydoc 3.0.1 on Thu May 2 07:29:09 2019 | http://epydoc.sourceforge.net |