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

Scheduler error such as run out of memory is not propagated to the hq #20

Open
unkcpz opened this issue Jun 24, 2024 · 0 comments
Open

Comments

@unkcpz
Copy link
Member

unkcpz commented Jun 24, 2024

Like in slurm scheduler plugin there is a some exit_codes for such errors explicitly, but those not catch by hyperqueue (probably it cached?)
Anyway, when the problem happened, we should do the same to set the exit code so user can use it to handle the problem.

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

1 participant