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

Posting to a shutdown thread pool - JRuby consistency and better naming #201

Merged
merged 3 commits into from
Dec 8, 2014

Conversation

rkday
Copy link
Contributor

@rkday rkday commented Dec 8, 2014

As discussed in #199, this gives JRuby the same behaviour and renames the code to "fallback_X" rather than "overflow_X".

"rake spec" passes on JRuby 1.7.6 (which I think runs both the pure-Ruby and the Java-backed code?), and I've moved the relevant tests to be shared between all thread pool executors.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.03%) when pulling 6bd961c on rkday:fallback_handling into e415a38 on ruby-concurrency:master.

@jdantonio
Copy link
Member

The failing RSpec test is known to be brittle and fail intermittently. Creating behavioral test (no test doubles) around thread pools has been very challenging.

@@ -25,14 +25,14 @@ def initialize(num_threads, opts = {})
super(opts)


#@overflow_policy = opts.fetch(:overflow_policy, :abort)
#@fallback_policy = opts.fetch(:fallback_policy, :abort)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All of these commented lines can be deleted. They are left over from a previous PR and I should have removed them earlier.

jdantonio added a commit that referenced this pull request Dec 8, 2014
Posting to a shutdown thread pool - JRuby consistency and better naming
@jdantonio jdantonio merged commit 0d43d21 into ruby-concurrency:master Dec 8, 2014
@jdantonio
Copy link
Member

Thank you!

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

Successfully merging this pull request may close these issues.

3 participants