You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once separation of workflow and electron statuses is done, the electron level statuses need to be updated to accommodate executor dependent statuses. In this case the following status definitions will be updated:
REGISTERING - Connection established to the remote machine and files are being transferred, slurm script also submitted
PENDING_BACKEND - Task is in the PENDING state in the slurm database
STARTING - Task is in the CONFIGURING state in the slurm database
RUNNING - Task is in the RUNNING state in the slurm database
COMPLETING - Task is in the COMPLETING state in the slurm database, result files are being retrieved, temporary files are being deleted
The classes for these statuses will need to be created similar to status classes defined in covalent/_shared_files/statuses.py. Then, in order to save the status, one can do:
Just adding on here that it would probably be good to have a timestamp or some indication of when the job starts running from the queued state, in addition to a more accurate description of the total elapsed runtime (since right now, the elapsed time starts ticking once the job script is submitted).
Once separation of workflow and electron statuses is done, the electron level statuses need to be updated to accommodate executor dependent statuses. In this case the following status definitions will be updated:
REGISTERING
- Connection established to the remote machine and files are being transferred, slurm script also submittedPENDING_BACKEND
- Task is in the PENDING state in the slurm databaseSTARTING
- Task is in the CONFIGURING state in the slurm databaseRUNNING
- Task is in the RUNNING state in the slurm databaseCOMPLETING
- Task is in the COMPLETING state in the slurm database, result files are being retrieved, temporary files are being deletedThe classes for these statuses will need to be created similar to status classes defined in
covalent/_shared_files/statuses.py
. Then, in order to save the status, one can do:This will propagate the status updation to the DB.
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: