-
Notifications
You must be signed in to change notification settings - Fork 52
Mac support for or_tools #1840
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
Mac support for or_tools #1840
Conversation
Also upgrading to 9.5 Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
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.
Currently, the optimizer image is hard-coded to image: "ghcr.io/fybrik/optimizer:0.0.1" which was built quite a while ago. In order to proper test the Dockerfile, the following is required:
- replace solver.image with "optimizer" for all charts/fybrik/values*.yaml
- add docker-build for optimizer in Makefile (where manager is built)
- add docker-push for optimizer in the git push action
I'm not sure I understand which tests take which image from which location. In practice, |
Tekton tests do not use the solver image, they use the local installation instead. I believe that they pass because you changed the install script. The changes to Dockerfile do not have any effect at all because "make docker-build docker-push" is never called for the optimizer. |
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
… or_tools_mac_support
* Mac support for or_tools Also upgrading to 9.5 Signed-off-by: Ziv Nevo <nevo@il.ibm.com> Co-authored-by: Shlomit Koyfman <shlomitk@il.ibm.com>
/cherry-pick branch=releases/1.2.1
|
* Mac support for or_tools Also upgrading to 9.5 Signed-off-by: Ziv Nevo <nevo@il.ibm.com> Co-authored-by: Shlomit Koyfman <shlomitk@il.ibm.com>
Also upgrading to OR Tools version 9.5
Should solve some of the issues in #1525