crim-ca / weaver

Weaver: Workflow Execution Management Service (EMS); Application, Deployment and Execution Service (ADES); OGC API - Processes; WPS; CWL Application Package
https://pavics-weaver.readthedocs.io
Apache License 2.0
24 stars 6 forks source link

[Feature] More details about job status timings #249

Closed fmigneault closed 2 years ago

fmigneault commented 3 years ago

All jobs currently provide the following:

We should add the following:

Once the job is done core execution computation (the actual processing: WPS, CWL, docker app, script, etc.), processed gets set, but updated can still receive more updates after this (processing outputs, storing results, destroy docker instances, etc.).

Finally, finished gets set around the time when email notification is sent for final hand-off of the results location. Final status = failed/succeeded is set and duration = finished - started is computed (already the case at the moment).

Follow up on https://github.com/opengeospatial/ogcapi-processes/issues/184 for any update and alignment with specification if fields that more concrete definitions.

Refer to descriptions in PR: https://github.com/opengeospatial/ogcapi-processes/pull/185/files

Also, add the /rec/core/job-status in conformsTo since above fields would all be supported.

fmigneault commented 2 years ago

Resolved in https://github.com/crim-ca/weaver/commit/f259b2ecbf1db97d53daa1a1f684309c137090ed (https://github.com/crim-ca/weaver/tree/4.2.0).