cylc
Skip mode tasks do not need to queue
Problem
When broadcasting run mode = skip to a an entire cycle point, I have found that the tasks can be sat there in the queued state when they don't need to obey the queue at all.
Proposed Solution
Skip mode tasks should be excluded from queues? (Edit: but should still obey runahead limit etc.)
Yes I think simply excluding skip-mode tasks from queue membership would do it.
(agreed, removed the question label and moved to a bugfix milestone)
I would argue it is more of a feature than a bugfix (or at least potentially more disruptive to user experience than a simple bugfix)
I can't think of any ways this would be disruptive to users?
Given the documented description of skip-mode, the user expectation of it, the documentation for queues, and the illogical situation where tasks configured to skip immediately just hang for a long period of time, I'm struggling to not see this as a bug.