-
Notifications
You must be signed in to change notification settings - Fork 20
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
Recursive dependency linking #1073
base: master
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.
is this code exercised by a unit test? The default GitHub runner is a linux box, and the code should be safe for windows and macos (if tests are run there also).
I imagine that a simple unit test which just runs the local native solvers with no inputs and check for bad return code would work. later we can run that test on multiple runners (windows, mac, linux).
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.
add a test for "running" one (or all) native solvers in a basic way (e.g. no args). This is a blind spot for us so is needed anyway. We can chat about the easiest way to test this.
} | ||
File[] temp = mySolverLinkDir.listFiles(); | ||
if (temp == null) throw new NullPointerException(); | ||
for (File file : temp) { |
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.
in the latest java, null pointer exceptions give nice contextual messages. I you are going to throw a raw NullPointerException, then you might as well let the for loop fail with a nicely formatted NullPointerException.
This reverts commit d4dd0a1.
Fixed issues with linux library linking in recent containers