Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
If a user creates a job that contains tasks with the same process name, that info is happily passed on to thermos, which will happily run one of those processes, but maybe display a separate one in the UI. In general the behavior in this case is non-deterministic and can lead to hard to track down bugs.
We should just short circuit and fail in the client if we detect multiple processes with the same name.