Skip to content

Conversation

CodeByDrescher
Copy link
Contributor

Fixed issues with linux library linking in recent containers

@CodeByDrescher CodeByDrescher self-assigned this Dec 7, 2023
Copy link
Member

@jcschaff jcschaff left a 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).

Copy link
Member

@jcschaff jcschaff left a 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) {
Copy link
Member

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.

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.

2 participants