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

split up timeouts #27

Open
lamont-granquist opened this issue May 3, 2014 · 0 comments
Open

split up timeouts #27

lamont-granquist opened this issue May 3, 2014 · 0 comments

Comments

@lamont-granquist
Copy link
Contributor

timing out on gecode should be broken apart from timing out on the ruby error hander.

when we time out on the ruby error handler, we should give back as much information as we've been able to glean before hitting the expensive parts of the computation. we should also give some indication in the exception that it was the ruby code barfing rather than the c code barfing.

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