An ill-formed or empty batchscript should result in some kind of error for the user.
Expected Behavior
We should get something like schedule failed (-3).
Current Behavior
Nothing happens. The job stays in the preprocessing (2) state.
Possible Solution
Look into how the schedule failed state is caught and how to catch errors from schedulers. If this is hard, maybe a timeout that is triggered if the job isn't in a queued, running, completed, or error state.
Steps to Reproduce (for bugs)
create a broken batchscript to see how it breaks and how it can be caught manually
have OnRamp generate the broken batchscript
launch a job that will create a broken batchscript and try to run it
4.
Context
Your Environment
Version used:
Environment name and version (e.g. Chrome 39, node.js 5.4):
An ill-formed or empty batchscript should result in some kind of error for the user.
Expected Behavior
We should get something like schedule failed (-3).
Current Behavior
Nothing happens. The job stays in the preprocessing (2) state.
Possible Solution
Look into how the schedule failed state is caught and how to catch errors from schedulers. If this is hard, maybe a timeout that is triggered if the job isn't in a queued, running, completed, or error state.
Steps to Reproduce (for bugs)
Context
Your Environment
┆Issue is synchronized with this Asana task