Closed mkoeppe closed 2 years ago
Branch pushed to git repo; I updated commit sha1. New commits:
8617b6f | .github/workflows/tox.yml: Reduce/streamline macos environments |
Branch pushed to git repo; I updated commit sha1. New commits:
2dee3f0 | .github/workflows/tox.yml (macos): Remove max-parallel |
Looks like homebrew's gcc
package no longer installs an unversioned gfortran
binary
https://github.com/mkoeppe/sage/runs/4572338375?check_suite_focus=true
Also conda install fails early
https://github.com/mkoeppe/sage/runs/4572338435?check_suite_focus=true
Replying to @mkoeppe:
Also conda install fails early
https://github.com/mkoeppe/sage/runs/4572338435?check_suite_focus=true
(same as #32113 comment:17)
Dependencies: #32113
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
43d481b | bump to 0.1.0 |
f66821b | cysignals are needed |
ae37b4e | deprecate sage.interfaces.primecount, not just remove |
d3ae5f4 | primecount is on conda, too |
3a8c7fe | primesieve is on conda, too |
74b3845 | allow float inputs for prime_pi |
591be34 | Merge #32894 |
049a5f6 | tox.ini: Do not set environment variable CONDARC |
f3116a1 | tox.ini (conda): Force use of conda's python3 |
6418579 | Merge #32113 |
Branch pushed to git repo; I updated commit sha1. New commits:
933134c | build/pkgs/gfortran/distros/homebrew.txt: Use gfortran |
Changed dependencies from #32113 to #32113, #32947
Branch pushed to git repo; I updated commit sha1. New commits:
ab4fb99 | tox.ini: Add ubuntu-jammy, debian-bookworm, linuxmint-20.3, fedora-36 |
e51225a | .github/workflows/tox*.yml: Remove debian-jessie, add ubuntu-jammy, debian-bookworm, linuxmint-20.3, fedora-36 |
ac47e7d | .github/workflows/tox-gcc_spkg.yml: Remove |
1aa9328 | Merge #32947 |
e99a09e | sed -i.bak 's/ubunty/ubuntu/g' .github/workflows/*.yml |
I know we already touch upon this point, but can you please expand on
Unfortunately, because because "needs" cannot depend on "matrix", the jobs for building/testing Python packages would not start before all jobs building SAGE_LOCAL for all platforms are completed
That is, why do you prefer the "custom stage build" over having a "local-macos-stage2" job that depends via "needs" on "local-macos-stage1", where each of these jobs defines an appropriate matrix. In particular, I don't understand the "all platforms" part, as ubuntu and macos are in different jobs, right? It appears to me that with the current design also stage 1 builds are executed before any stage 2 is executed, so the only difference is that you can already have 4 or so stage 2 builds running while the last stage 1 build finishes. I guess for the overall build time this shouldn't make much of a difference anyway, as these 4 runners would be busy with other workflows then (or are free to execute builds of other stuff in the sagemath org).
Replying to @tobiasdiez:
That is, why do you prefer the "custom stage build" over having a "local-macos-stage2" job that depends via "needs" on "local-macos-stage1", where each of these jobs defines an appropriate matrix.
To avoid copy-paste
Replying to @tobiasdiez:
I don't understand the "all platforms" part, as ubuntu and macos are in different jobs, right?
Yes, that's right, within each job; and in this ticket, only for macos.
Replying to @mkoeppe:
Replying to @tobiasdiez:
That is, why do you prefer the "custom stage build" over having a "local-macos-stage2" job that depends via "needs" on "local-macos-stage1", where each of these jobs defines an appropriate matrix.
To avoid copy-paste
Github recently made it possible to reuse workflows: https://docs.github.com/en/actions/learn-github-actions/reusing-workflows Thus you could extract the current local-macos job into a new workflow and pass the right "tox" command as an argument (determined by the matrix + step).
Thanks for the pointer!! I've added this to #29060 for welcome future refactoring - but this won't make it into Sage 9.5
Branch pushed to git repo; I updated commit sha1. New commits:
edb4364 | .github/workflows/tox.yml: Replace homebrew-macos-python3_xcode-standard by homebrew-macos-usrlocal-python3_xcode-standard |
Description changed:
---
+++
@@ -18,8 +18,6 @@
As of this ticket, we rely on the bottleneck of the available parallel jobs on GH Actions to ensure that the 2nd stages of a configuration are run after the 1st stage of that configuration. Experience with this workflow will show whether this suffices.
-References
-- https://evilmartians.com/chronicles/build-images-on-github-actions-with-docker-layer-caching
+We also update the macOS/Xcode versions according to what's available on GH Actions and switch the `homebrew` builds to faster `homebrew-usrlocal` variants, which can use bottles for all available packages.
-
Changed reviewer from https://github.com/mkoeppe/sage/actions/runs/1605145773 to Dima Pasechnik
OK,macOS runs on GH look good.
Thanks!
Changed branch from u/mkoeppe/gh_actionsrun_a_job_formake_build_localfirst__cache_image_for_jobmakebuild to edb4364
We revise the GH Actions workflows to use a 2-stage build: In the first stage, run
make build-local
, and storeSAGE_LOCAL
as a build artifact. In the second stage, download the build artifact and run more building and testing.(+) On top of the artifact containing the full SAGE_LOCAL, we can test several ways to build the Python parts
configure --enable-editable
configure --enable-system-site-packages
(#29665)(+) Tests of optional and experimental packages can be streamlined, as we avoid rebuilding their dependencies that are standard packages.
(+) Splitting the job into two would also help with the configurations for which we scrape at the 6 hour time limit
(-) Unfortunately, because because "needs" cannot depend on "matrix", the jobs for building/testing Python packages would not start before all jobs building
SAGE_LOCAL
for all platforms are completedIn this ticket, we only change all existing
macos
workflows to a 2-stage workflow, integrating the separate workflows for optional and experimental packages.As of this ticket, we rely on the bottleneck of the available parallel jobs on GH Actions to ensure that the 2nd stages of a configuration are run after the 1st stage of that configuration. Experience with this workflow will show whether this suffices.
We also update the macOS/Xcode versions according to what's available on GH Actions and switch the
homebrew
builds to fasterhomebrew-usrlocal
variants, which can use bottles for all available packages.Depends on #32113 Depends on #32947
CC: @tobiasdiez @kliem @orlitzky @isuruf
Component: porting
Author: Matthias Koeppe
Branch/Commit:
edb4364
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/32703