-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
More tests for common MIP TestSuite: add_col, solve; some fixes for backends #20424
Comments
This comment has been minimized.
This comment has been minimized.
Commit: |
comment:3
Branch is on top of #20323. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
comment:5
Rebased on top of #20323 branch on top of 7.2.beta4 |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:7
Rebased on top of 7.2.beta5. |
comment:8
How do you do test autogeneration (mentioned in 850b817) ? |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:11
rebased on 7.2.beta6 |
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
comment:18
rebased on 7.3.beta5 |
Reviewer: Dima Pasechnik |
comment:19
looks good to me |
Changed branch from u/mkoeppe/backend_testsuite_failing_tests to |
Changed commit from |
comment:21
Replying to @sagetrac-git:
Are there any plans to support this for other backends? I noticed that it's not even documented in The interface between backends should be consistent, so even just |
comment:22
IMHO different backends might have different features, which might be impossible to have for each backend. Only if there are multiple backend supporting this, we can think of adding it to the generic backend, with the default implementation as you propose. |
comment:23
Replying to @jdemeyer:
Yes, there is a plan, see #20324. |
Split out from #20323.
This patch adds new _test methods for
add_col
,solve
, and for #18572 (but disabled for CVXOPT, where it fails).To make the new test methods happy,
add_col
for Gurobi;add_col
for COIN;If anyone at all cares about the CVXOPT backend, perhaps they could fix it?
From dimpase:
I recall asking how one deals with different backends producing different, albeit equivalent, outputs. E.g. some of them would even introduce extra variables for some constraints (see e.g. #13148 comment:2). Some backends assign names to constraints automatically.
Depends on #20323
Depends on #20600
Depends on #20325
CC: @dimpase @videlec @jdemeyer @fchapoton @nbruin
Component: numerical
Author: Matthias Koeppe
Branch:
97c4542
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/20424
The text was updated successfully, but these errors were encountered: