-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve error message when binary is not found #780
Comments
I do not think this is a good idea. HQ commands should be a ground truth for task status. Stdout/Stderr is something produced by the task and we should not interfere with this. |
We could give a very explicit annotation that the content was generated by HQ, or create a separate file on disk with this error. Sometimes people just take a look at stdout/stderr and expect to see everything there (which is mostly how PBS/Slurm works). In HQ, you also need to examine the job status to see the details. |
There are still errors that cannot be solved like this, e.g. task fails because its dependency fail. Or task fails because worker cannot create a stderr because of permissions. So it cannot be universal, and having semantics "sometimes you will find error from HQ in stderr and sometimes not, is worse than the current situation. |
When thinking more about it. If we promise output solely for this particular error, it should be ok. |
When you start a program that does not exist, HQ shows the error in
hq job info last
, but nothing is included in the stdout/stderr files of the tasks. Maybe we could add this error also to stderr, to make it easier to figure out what went wrong.The text was updated successfully, but these errors were encountered: