Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • autosubmit autosubmit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 338
    • Issues 338
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Earth SciencesEarth Sciences
  • autosubmitautosubmit
  • Issues
  • #338
Closed
Open
Issue created Jul 04, 2018 by Raffaele Bernardello@rbernardDeveloper

setstatus to WAITING does not propagate to dependent jobs

1- I used setstatus to set *17_SIM to COMPLETED by mistake.

2- I used again setstatus to set *17_SIM to WAITING.

3- autosubmit run

*17_SIM submitted

*18_SIM submitted

I guess at step 1 *18_SIM went to READY but at step 2 it did not revert to WAITING.

Possibly a bug?

I can see that if *18_SIM was COMPLETED you don't want it to be changed to WAITING if, for example you want to repeat only *17_SIM (at step 2). But since it was set to READY it means it was not executed yet and it depends on *17_SIM.

Edited Jul 04, 2018 by Raffaele Bernardello
Assignee
Assign to
Time tracking