Skip to content
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

Cygwin spkg-check meta-ticket #22866

Closed
embray opened this issue Apr 24, 2017 · 4 comments
Closed

Cygwin spkg-check meta-ticket #22866

embray opened this issue Apr 24, 2017 · 4 comments

Comments

@embray
Copy link
Contributor

embray commented Apr 24, 2017

I'm running the spkg-check scripts for each standard package (I haven't normally built with SAGE_CHECK=yes). It could reveal some bugs that are not caught by Sage's test suite, but that could nevertheless affect Sage.

For now I will just list packages whose tests are failing for me; I will open separate tickets for individual packages that look worth investigating (for example, the failures in cysignals are worth looking into; whereas the failing tests for curl maybe not so much as it is not a direct dependency of Sage...). The packages that have failing checks/tests are:

  • curl (7.53.1)
  • cysignals (1.3.2)
  • cython (0.25.2.p0)
  • flint (2.5.2.p1)
  • giac (1.2.3.25)
  • pcre (8.40)
  • python2 (2.7.13.p1)
  • python3 (3.5.1)
  • r (3.3.3.p2)
  • zeromq (4.2.5)

Component: porting: Cygwin

Issue created by migration from https://trac.sagemath.org/ticket/22866

@embray embray added this to the sage-8.0 milestone Apr 24, 2017
@embray

This comment has been minimized.

@embray

This comment has been minimized.

@embray

This comment has been minimized.

@embray
Copy link
Contributor Author

embray commented Sep 28, 2018

comment:3

zeromq is also failing. I don't know if it passed earlier but IIRC it did not , and was just left off this ticket by mistake.

@embray embray removed this from the sage-8.0 milestone Apr 19, 2019
@embray embray added the pending label Apr 19, 2019
@mkoeppe mkoeppe closed this as not planned Won't fix, can't repro, duplicate, stale Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants