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

Minimal m1 build #648

Closed
wants to merge 4 commits into from
Closed

Minimal m1 build #648

wants to merge 4 commits into from

Conversation

pdjames
Copy link

@pdjames pdjames commented Oct 16, 2023

Hi team,

I've created a minimal changes branch to enable M1 builds using GitHub's recently added M1 runners.

  • steps in the build task are the same
  • M1 runners currently have a price attached, but it's not huge and these builds are in the order ~$1, so not terrible but developing changes against them might not be fun, try on a private machine first.
  • I have frozen about 20 versions of dev dependencies in this commit.
  • hopefully dev dependencies aren't seen as too critical to have bleeding edge versions.

There were a few discoveries a long the way, the GitHub workflow changes here are minimal, there was a lot of time spent discovering a combination of dev dependencies which pass muster on a variety of os & arch combinations. The package solver didn't always get it right wrt what would run, just what would install.

I think this link is public, but let me know if you can't see it;
https://github.com/pdjames/httpstan_build/actions/runs/6530495372
This shows the exact same commit just without the dev dependency changes is failing, in this case it's autoapi that fails, though I have walked up that tree and arrived at what is committed in this PR.

Let me know if you have any questions,
Thanks!

Peter

… architectures for a couple of python versions."

This reverts commit cec8321.
- requests more recent poetry version.
- maintains existing code checking and tests
…ing.

- most recent versions throw errors in some environments
-then passes down the dependency tree as each one is fixed
- this is a freeeze set of working configuration of dependencies

- Note. All related to dev packages only.
- Note. Mostly cenetered around Sphinx and api-testing.
@riddell-stan
Copy link
Contributor

So no changes to the Makefile or build steps, right?

I've created a simpler PR #649 . It doesn't appear to be working at the moment. I'll try to sort out the billing next week.

@pdjames
Copy link
Author

pdjames commented Oct 21, 2023

I recognise those apispec errors, in this pull request I've worked around the sphinx versions by stepping versions backwards.

I have another PR here #650 which has the versions stepping forwards and all the existing and the new builds pass.

I'll close this PR as the newer is simpler.

Correct, no changes to the makefile needed.

@pdjames pdjames closed this Oct 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants