Skip to content

Missing options: work level timeouts, work completion status in log, option #10

@PushpakNarasimhan

Description

@PushpakNarasimhan

Hi Developers,
Would love to have following options or possible workarounds (was unable to find):

  1. Work/Script level timeout so that script retry can be effective
  2. work1....n folder custom naming option
  3. Submitted jobID: XXX jobcmd: XXXX in the local_cycle is present, however when the job completes is missing in logs, this would help in understanding and debugging which job took more time or is currently active.
  4. subtask.done, subtask.sh.e, subtask.sh.o be with .txt extention to help applications/editors recognize them

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions