Add the OPAMSOLVERTOLERANCE environment variable to allow users to fix solver timeouts for good #5510
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Partially fixes #5504
Partially fixes #3447
Partially fixes #5353
Partially fixes #4794
Fixes #3230
Requires ocaml-opam/ocaml-mccs#40
Optimizing solvers can be an annoying breed, sometimes a problem is just too complex for solver A but easy for solver B, and on some other problem solver B might take too long where solver A takes no time at all.
To partly solve the numerous timeout issues that have been plagued opam, I introduce this new environment variable that allows
builtin-mccs+glpk
(default solver) to not wait around for too long when it found a solution but the solution is not the optimum solution.The downside of having unoptimized solutions is that opam might install out-of-date packages so it is to be used parsimoniously.
TODO: add teststoo complicated to do reliably