Make queued assigned jobs more distinguishable
START_DIRECTLY_AFTER_TEST multiple jobs are assigned to a worker at the same time. The worker processes these jobs one after another. In other words, jobs are queued by the worker. So far these queued jobs are displayed as assigned like any other assigned jobs within the web UI (e.g. on the 'All tests' page).
This behavior can lead to confusion, e.g. users might be wondering why the worker does not start processing its assigned job and why multiple jobs are assigned to the same worker slot. Hence it would be great if it would be more obvious that those jobs are already queued by the worker.
- We could show these jobs as "blocked by ..." similar to scheduled jobs which are not assigned to a worker because of a
START_AFTER_TESTdependency. That's only the first idea which comes to my mind so it would make sense to put some more thought into this.
- I would refrain from unnecessarily changing internal details. That these jobs are internally in the state "assigned" is not a problem. Only the way these jobs are presented to the user is the problem.