Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
MiniZinc stopped with a non-zero exit code, but did not output an error message
See original GitHub issuesolver: minizinc’s gecode, gist, restart and set subsolvers CPMpy: version v0.9.9 commit e79b3afedc934a9437c2ddb3a9f54d7e2d7bd3ee minizinc-python release version 0.7.0 commit {https://github.com/MiniZinc/minizinc-python/commit/a195cf63fcfbc98665d70ab64efb5424db25bd7e)
Some MiniZinc subsolvers crash without an error message, while other solvers can solve the problem.
from cpmpy import *
file ="minimized" # don't forget to unzip
m=Model().from_file(file)
m.solve(solver='minizinc:gecode') # same with "minizinc:gist", "minizinc:restart" and "minizinc:set"
expected behavior: No crash like other solvers (“minizinc:gurobi”, “ortools” …)
bug found while working on my master thesis.
Issue Analytics
- State:
- Created 10 months ago
- Comments:8
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The same issue was raised in minizinc-python: https://github.com/MiniZinc/minizinc-python/issues/60 Adding the minizinc folder to my PATH solved the issue for me. (I am using windows)
Is there a way we could catch this exception and output a warning wrt putting the minizinc folder in the PATH? If not, can close, if yes and small effort, could help others in the same situation