-
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
segfault when max number of jobs reached #6
Comments
This can be triggered by using the same approach described in #5 and:
resulting in a backtrace
From this backtrace it seems a duplicate of #10 |
Now that #5 is fixed, I can confirm that this segfault is still present. |
This now produces an informative exception and no segfault. Thanks for the fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This still requires confirmation and a proper backtrace but when submitting over 10.000 jobs on a cluster with a 10.000 limit a segfault would be seen.
The text was updated successfully, but these errors were encountered: