-
Notifications
You must be signed in to change notification settings - Fork 364
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
Modify warning logic in WindowsJNAAffinity.setAffinity #118
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @yevgenp thanks for sorting this out 👍
Please can you get the Windows build green before merging - I believe it has been broken for a while but this is a good opportunity to fix it.
@@ -89,7 +89,7 @@ public void setAffinity(final BitSet affinity) { | |||
throw new IllegalStateException("SetThreadAffinityMask((" + pid + ") , &(" + affinity + ") ) errorNo=" + e.getErrorCode(), e); | |||
} | |||
BitSet affinity2 = getAffinity0(); | |||
if (!affinity2.equals(affinity)) { | |||
if (!affinity2.intersects(affinity)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to cover this with a Windows specific unit test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That warning is being produced on every Windows test (except when run on a single CPU). IMO it would not yield too much value to test a single log line. Especially, when we can't reproduce a negative case.
Closes #117