gwf cancel cancels jobs that aren't submitted

[cmkobel]

Is it possible to set up the backend such that gwf cancel only cancels batched jobs. As it is now: it cancels everything in the pipeline.

Kind regards, Carl

[dansondergaard]

Hi Carl,

I'm not entirely sure what you mean. If you just run "gwf cancel" it will ask if you want to cancel all targets, but you can also give it a list of target names: "gwf cancel Target1 Target2" and it will only cancel those targets.

So I'm not sure if you're reporting a bug or if you were just surprised about the behaviour? Do you get an error of some sort, or?

[cmkobel]

It is not a bug. I'm just surprised that when you tell it to cancel all targets, it also tries to cancel the ones not running. I would love to have an option to cancel all batched/running targets. But this is not critical of course.

[dansondergaard]

Got it. I guess it shouldn't print that it's trying to cancel targets that haven't been submitted.

[dansondergaard]

This is fixed in 1.7, which should come out this week. Closing.