-
Notifications
You must be signed in to change notification settings - Fork 392
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
Make riak_core_util:safe_rpc catch exit correctly #598
Conversation
- change 'EXIT':{noproc, ...} to exit:{noproc, ...}
Thanks for catching this, I've assigned the 2.0-RC milestone to both of these issues. |
cc @lordnull |
👍 as the riak_test proves it's correctness. Of course, bors isn't happy due to a spurious eunit failure (sha_test timeout). |
@borshop merge |
👍 b01f400 |
Make riak_core_util:safe_rpc catch exit correctly Reviewed-by: lordnull
@borshop merge |
Make riak_core_util:safe_rpc catch exit correctly Reviewed-by: lordnull
The failure we're seeing here is #590. |
Can we manually merge, @reiddraper? |
Sure, and I appreciate that we talked about it in the comments. I just want there to at least be an explanation in the comments every time we decide to manually merge. In this case, the explanation is that another test is blocking us, and we'd like to get a better handle on the outstanding issues, so having this closed will help us gain better visibility into what's remaining. |
Make riak_core_util:safe_rpc catch exit correctly
The function was attempting to catch exit exception with 'EXIT':{noproc, ...}; should be exit:{noproc, ...}
http://erlang.org/doc/reference_manual/errors.html
Related riak_test PR:
basho/riak_test#624