-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
ci-cygwin.yml: Multi-stage build #29403
Comments
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
comment:4
Sample run https://github.com/mkoeppe/sage/actions/runs/63708828 |
Dependencies: #29397 |
comment:6
Something is still triggering rebuilds of targets that have been built in a previous stage. |
comment:7
I'd suspect it's the |
Changed dependencies from #29397 to none |
comment:9
I'm running one test with MAKE="make --debug=verbose" to see what's happening there |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Author: Matthias Koeppe |
comment:13
This works pretty well now. |
comment:15
New failure mode: https://github.com/mkoeppe/sage/runs/560884908
|
comment:16
https://github.com/mkoeppe/sage/runs/560884917
|
comment:17
https://github.com/mkoeppe/sage/runs/560884917
|
comment:18
Replying to @mkoeppe:
welcome to Cygwin rebase Hell. |
comment:21
In https://github.com/mkoeppe/sage/runs/572730280 (cygwin-stage-ii-a (minimal)), despite rebasing in the "Extract sage-local artifact" step, I am still getting |
comment:23
#29486 cygwin-standard: rpy2 fails to build |
comment:24
cygwin-stage-ii-b (minimal) times out - https://github.com/mkoeppe/sage/runs/572730298 - may need to rebalance stages |
comment:37
with these multi-stage builds, where *.so get built at one place, and moved then somewhere esle, it could be that more rebasing is needed. In particular, I recall seeing and fixing rebase locations for Python modules being built. |
comment:38
Testing at https://github.com/mkoeppe/sage/actions/runs/80516745 |
comment:39
Yes, I'm rebasing after unpacking |
comment:40
I think it's working now, and we can see the real build errors again in |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:43
testing on https://github.com/dimpase/sage/actions/runs/81294070 |
comment:44
I cannot reproduce the matplotlib build error locally - even when I download and unpack stage-i-a and stage-i-b (standard) and configure against that. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:49
how does one need to modify ~/.github/ to make GH Actions only run cygwin tests? |
comment:50
Replying to @dimpase:
Just delete the file tox.yml |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Dima Pasechnik |
comment:54
Thanks! |
Changed branch from u/mkoeppe/ci_cygwin_yml__multi_stage_build to |
The GitHub workflow for cygwin does not fit into the 6-hour time limit.
We do a multi-stage build, saving and loading
local/
to/from build artifacts.Depends on #29417
Depends on #29392
CC: @dimpase @embray @slel @jpflori @tscrim @vbraun @kcrisman
Component: porting: Cygwin
Author: Matthias Koeppe
Branch/Commit:
27ddea3
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/29403
The text was updated successfully, but these errors were encountered: