Skip to content
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

Open
Kobzol opened this issue Oct 29, 2024 · 4 comments
Open

Improve error message when binary is not found #780

Kobzol opened this issue Oct 29, 2024 · 4 comments

Comments

@Kobzol
Copy link
Collaborator

Kobzol commented Oct 29, 2024

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.

@spirali
Copy link
Collaborator

spirali commented Oct 29, 2024

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.

@Kobzol
Copy link
Collaborator Author

Kobzol commented Oct 29, 2024

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.

@spirali
Copy link
Collaborator

spirali commented Oct 29, 2024

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.

@spirali
Copy link
Collaborator

spirali commented Oct 29, 2024

When thinking more about it. If we promise output solely for this particular error, it should be ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants