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
cvxopt fails its test suite #28730
Comments
comment:1
Is it related to #24657? Note my comment at the end of the ticket. |
comment:2
Thank you for pointing out that ticket. It looks different to me, though: I see
|
This comment has been minimized.
This comment has been minimized.
comment:4
I see a change from numpy ultimately. Which file is this from? I'll see if it still happens with cvxopt-1.2.3 which is what I am using in sage-on-gentoo. In fact now that I have shipped suitesparse we should be able to update cvxopt, I guess I should have taken a lead on that. |
comment:5
Replying to @kiwifb:
Not sure what you mean. The error message is from the cvxopt log file, and it refers to |
comment:6
I see, I should have spotted it. Now I see that this is the same file file but a different problem than in #24657. Upgrading cvxopt won't fix the fact that you try to run (outdated) documentation as tests. Note like I said in #24657 cvxopt' spkg-check is not running a test suite, it is running documentation examples as if it was a test suite. And then shock horror it is not foolproofed like one. I think we should ditch spkg-check in cvxopt unless we are to run the real test suite with |
comment:7
That makes sense to me. Unfortunately, I don't think we have a way of including an optional package as a dependency for testing, so should we just remove the cvxopt |
comment:8
That would be the sensible thing. At least in my opinion. The other testing dependency I can think of is |
comment:9
Actually, looking at the version of
I just downloaded version 1.2.3, and its
So we could update to 1.2.3 and use |
comment:10
I guess we can try that. Personally I didn't look at |
comment:11
I think our current broken I tried upgrading to 1.2.3, but there are too many dependencies for me to deal with right now: SuiteSparse which in turn depends on |
comment:12
I thought part of #22380 had gone in but it was blocked by cygwin :( If suitesparse now depends on cmake that means there is a new release. I should at least look into that. |
comment:13
#22380 is using suitesparse 5.4.0, upstream is now at 5.6.0 but it should all work as in that ticket. |
comment:14
I agree, we don't need |
comment:15
Now I see I made a patch to avoid calls to cmake. We should finish that ticket. |
comment:16
So should we close this ticket, or should we use this to remove |
comment:17
Replying to @jhpalmieri:
We should remove it here. Fixing the cygwin problem in #22380 may take a bit of time. I have an alternative packaging option for suitesparse, it just makes me the maintainer for both gentoo and sage until it gets a better build system [which is likely to be cmake]. |
New commits:
|
Commit: |
Author: John Palmieri |
comment:20
LGTM |
Reviewer: François Bissey |
Changed branch from u/jhpalmieri/cvxopt-no-spkg-check to |
With a Python 3 build of Sage,
./sage -f -c cvxopt
fails.See also #24657.
Component: packages: standard
Author: John Palmieri
Branch/Commit:
cee0cab
Reviewer: François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/28730
The text was updated successfully, but these errors were encountered: