chore(infra): remove build-macos-x86_64#1325
Conversation
|
@milenkovicm please take a look |
milenkovicm
left a comment
There was a problem hiding this comment.
Personally I don't think we should care about Intel Macs at this stage, latest makes more sense to me
.github/workflows/build.yml
Outdated
| needs: [generate-license] | ||
| name: Mac x86_64 | ||
| runs-on: macos-latest | ||
| runs-on: macos-15-intel |
There was a problem hiding this comment.
I'm not sure, why would we test it on intel chipset, arm (latest) makes more sense to me
There was a problem hiding this comment.
making this change because this was originally using macos-13
macos-15-intel is the direct replacement
There was a problem hiding this comment.
the name of the step "Mac x86_64" suggest that we should use an intel based processor.
macos-latest is arm64
https://docs.github.com/en/actions/reference/runners/github-hosted-runners#standard-github-hosted-runners-for-public-repositories
There was a problem hiding this comment.
opened this pr to correct the mistake from #1324
we can follow up with removing this github action step is necessary
There was a problem hiding this comment.
I believe intel architecture for Mac is on its way out, let's keep arm, and just rename action, Wdyt?
There was a problem hiding this comment.
i remove the build-macos-x86_64 step entirely, the step above, build-python-mac-win, already covers mac-latest
There was a problem hiding this comment.
can we rename
build-macos-x86_64:
needs: [generate-license]
name: Mac x86_64
runs-on: macos-latest
build-macos-x86_64 -> build-macos-arm64
There was a problem hiding this comment.
so instead of removing build-macos-x86_64, we want to just rename to build-macos-arm64?
|
@milenkovicm i updated the pr to split out windows and mac. lmk if this is what you were thinking about |
| path: python/target/wheels/* | ||
|
|
||
| build-macos-x86_64: | ||
| build-macos-arm64: |
There was a problem hiding this comment.
this is what i was asking, as name changed after you push update to use arm64 👍🏻
| path: LICENSE.txt | ||
|
|
||
| build-python-mac-win: | ||
| build-windows: |
There was a problem hiding this comment.
I'm not sure why you removed mac from here? is there other job which tests this python on mac
There was a problem hiding this comment.
yes, build-macos-arm64.
build-python-mac-win used to run for windows and macos. but since build-macos-arm64 already runs for macos, im chaning this to just run windows.
There was a problem hiding this comment.
build-python-mac-win builds ballista/python/ extension, on the other hand build-macos-arm64 builds core ballista/ or I'm missing something
There was a problem hiding this comment.
heres a side by side diff of build-python-mac-win and build-macos-arm64 taken from latest main
datafusion-ballista/.github/workflows/build.yml
Lines 108 to 213 in 400f818
the only difference is which os is running. the refactor here is to get rid of the matrix.os in build-python-mac-win since build-macos-x86_64 is already running for macos-latest
Which issue does this PR close?
Closes #.
Rationale for this change
Follow up to #1324, the correct replacement formacos-13should bemacos-15-intelfor Intel-based architectureaccording tohttps://docs.github.com/en/actions/reference/runners/github-hosted-runners#standard-github-hosted-runners-for-public-repositories
Since both
build-python-mac-winandbuild-macos-x86_64usemacos-latest, we can consolidate and refactor the steps to run for individual osWhat changes are included in this PR?
Are there any user-facing changes?