-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
Add GitHub CI workflow for cygwin #29295
Comments
Branch: u/mkoeppe/29106+ci |
Commit: |
Author: Matthias Koeppe |
This comment has been minimized.
This comment has been minimized.
comment:3
This works pretty well already (https://github.com/mkoeppe/sage/runs/492908952?check_suite_focus=true) Issues:
|
comment:5
Tests at https://github.com/mkoeppe/sage/actions/runs/51902280 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:7
I see here in the log some probably known to Erik issue, crypt module does not build for py3
maybe it's just a forgotten Cygwin package: |
comment:8
See also #29012 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:13
oh, right, it should have been https://cygwin.com/packages/summary/libcrypt-devel.html |
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
Changed dependencies from #29106 to none |
comment:17
Rebased on 9.1.beta8 |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits: |
comment:20
what is the point of having |
comment:21
Even if it times out, it provides valuable testing of the build process for the early packages. |
comment:22
But I'm working on the refinement of this workflow using several stages |
comment:23
ok |
Reviewer: Dima Pasechnik |
Changed branch from u/mkoeppe/29106+ci to |
Using choco instead of apt-cyg because it is available out of the box on GitHub Actions, and can install cygwin unattended.
CC: @embray
Component: porting: Cygwin
Author: Matthias Koeppe
Branch/Commit:
85b3c3d
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/29295
The text was updated successfully, but these errors were encountered: