Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S Super-SloMo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Avinash Paliwal
  • Super-SloMo
  • Issues
  • #81
Closed
Open
Issue created May 11, 2020 by Administrator@rootContributor

resume work after unexpected interruption

Created by: htc1977

Is your feature request related to a problem? Please describe. I had a SloMo job running and my desktop environment restarted and killed the job unfortunately.

Describe the solution you'd like It would be nice to have some kind of parameter to resume the work on the latest frame, because recreating of a multi-day-job isn't very productive. Alternatively, the script could check, if the tmp directory exists and if the amount of file within the output subdir meet the amount of files in the input subdir times the parameter of the last script execution and ask if it should continue the work or if it should restart from scratch.

Assignee
Assign to
Time tracking