specify the erlang system module name while calling monitor/2 #115
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
closed this
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
thanks for rebar!
Today, the master branch fails to compile on Erlang R13B03:
Recompile: src/rebar_eunit
src/rebar_eunit.erl:565: function monitor/2 undefined
The call to monitor/2 was introduced by merging with slf-eunit-process-isolation2 branch, 3 days ago: 9832a5c#src/rebar_eunit.erl
The proposed update restores the ability to compile on R13B03 by simply specifying the erlang system module name while calling monitor/2.
Cheers,
alfonso