You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
error: Distribution `torch==2.13.0+cpu @ registry+[https://download.pytorch.org/whl`](https://download.pytorch.org/whl%60) can't be installed because it doesn't have a source distribution or wheel for the current platform
hint: You're on macOS (`macosx_26_0_arm64`), but `torch` (v2.13.0+cpu) only has wheels for the following platforms: `manylinux_2_28_aarch64`, `manylinux_2_28_x86_64`, `linux_s390x`, `win_amd64`, `win_arm64`; consider adding "sys_platform == 'darwin' and platform_machine == 'arm64'" to `tool.uv.required-environments` to ensure uv resolves to a version with compatible wheels
Error: Process completed with exit code 2.
Torch-MLIR also doesn't have support for MacOS (only manylinux and win), so that's another thing that we'll need to fix before we can officially claim to support MacOS.
I'm able to reproduce it locally. In my first setup, I deliberately skipped: uv sync --extra ingress-torch-cpu --extra runtime_mpich.
However, while for Torch, it's actually a simple fix since the +cpu postfix (within the toml file) is not needed on Darwin, for torch-mlir we don't have the macOS support right now (see here), as you pointed out :(
At the moment only Linux (x86_64 + AArch64) and Windows (x86_64) builds are published. If you are interested in other configurations, please send a PR.
Now seriously, it should be simple to do get macOS on the matrix, but getting all the tests to pass is a whole different matter. I think it would be an interesting conversation at the very least. Starting with an issue, and perhaps a mock PR that shows what crashes would be a good start.
Now seriously, it should be simple to do get macOS on the matrix, but getting all the tests to pass is a whole different matter. I think it would be an interesting conversation at the very least. Starting with an issue, and perhaps a mock PR that shows what crashes would be a good start.
I'm working on this. I'll send a PR ASAP. Thank you!
I have an AI-assisted commit in which I'm running the GH action against (it works locally).
torch-mlir 20261001, mpich and mpi4py already have macOS arm64 wheels.
tools/kernel-bench hardcodes libmlir_c_runner_utils.so (.dylib on macOS). Runner already adds this library with the right suffix, so kernel-bench doesn't need to pass it.
With both, lit gives 87 passed / 6 failed / 2 unsupported. The 6 failures (test/transform/test_subgraph_tiling.py and five examples/xegpu/llama-bench_1B_* tests) all segfault at prepare_subgraphs.py:112 on every run, while the same commit passes on Linux CI. I'm looking into it.
@FedericoBruzzone are you still working on this? If not, I'm happy to send a PR against main for 1 and 2 (without the CI change for now, since it would hit the segfault).
Thank you for the report. Due to the current backlog upstream and my research, no.
Unfortunately, I don't have the time I'd like to have for Lighthouse :(
Before starting this, I'd wait for @rengolin to know the current status of MacOS support and/or Torch-MLIR release migration and so on.
The main constraint is lighthouse itself (#283). @tkarna how are we doing on this front?
pyproject.toml: there is no +cpu torch wheel for macOS,
This should be fine. @FedericoBruzzone is this something you did on your tests, too?
The 6 failures (test/transform/test_subgraph_tiling.py and five examples/xegpu/llama-bench_1B_* tests) all segfault at prepare_subgraphs.py:112 on every run, while the same commit passes on Linux CI. I'm looking into it.
XeGPU example should not need to run on MacOS. Though, that tests is just a PyTorch scaled attention, so it should not be a problem.
@FedericoBruzzone Thanks! I think #283 is already covered by #302 (torch-mlir now comes from PyPI), and the fork run above installs it from there on macOS.
@rengolin would you like to push your macos branch as a PR, or should I open one with your commit? cc @tkarna in case anything in #283 is still missing.
Activity
FedericoBruzzone commentedon Aug 26, 2026
Hi @rengolin, thanks for iterating on this🙏
I'm able to reproduce it locally. In my first setup, I deliberately skipped:
uv sync --extra ingress-torch-cpu --extra runtime_mpich.However, while for Torch, it's actually a simple fix since the
+cpupostfix (within the toml file) is not needed on Darwin, fortorch-mlirwe don't have the macOS support right now (see here), as you pointed out :(So, the
torch-mlir-releaseREADME explicitly say:What do you suggest we do?
rengolin commentedon Aug 26, 2026
Send a PR? 😄
Now seriously, it should be simple to do get macOS on the matrix, but getting all the tests to pass is a whole different matter. I think it would be an interesting conversation at the very least. Starting with an issue, and perhaps a mock PR that shows what crashes would be a good start.
FedericoBruzzone commentedon Aug 27, 2026
I hadn't thought about that, you know? :'D
I'm working on this. I'll send a PR ASAP. Thank you!
I have an AI-assisted commit in which I'm running the GH action against (it works locally).
aeft commentedon Nov 14, 2026
I ran the CI steps from the
macosbranch locally on an Apple M2 Pro (macOS 26.5), on main (d753671). Two changes get it most of the way:pyproject.toml: there is no+cputorch wheel for macOS, so use a platform marker:20261001, mpich and mpi4py already have macOS arm64 wheels.tools/kernel-benchhardcodeslibmlir_c_runner_utils.so(.dylibon macOS).Runneralready adds this library with the right suffix, so kernel-bench doesn't need to pass it.With both, lit gives 87 passed / 6 failed / 2 unsupported. The 6 failures (
test/transform/test_subgraph_tiling.pyand fiveexamples/xegpu/llama-bench_1B_*tests) all segfault atprepare_subgraphs.py:112on every run, while the same commit passes on Linux CI. I'm looking into it.@FedericoBruzzone are you still working on this? If not, I'm happy to send a PR against main for 1 and 2 (without the CI change for now, since it would hit the segfault).
FedericoBruzzone commentedon Nov 14, 2026
Thank you for the report. Due to the current backlog upstream and my research, no.
Unfortunately, I don't have the time I'd like to have for Lighthouse :(
Before starting this, I'd wait for @rengolin to know the current status of MacOS support and/or Torch-MLIR release migration and so on.
rengolin commentedon Nov 14, 2026
Torch-MLIR has support for MacOS: https://pypi.org/project/torch-mlir/#files
And so does MLIR Python Bindings: https://github.com/llvm/eudsl/releases/tag/mlir-python-bindings
We should be fine on that front.
The main constraint is lighthouse itself (#283). @tkarna how are we doing on this front?
This should be fine. @FedericoBruzzone is this something you did on your tests, too?
XeGPU example should not need to run on MacOS. Though, that tests is just a PyTorch scaled attention, so it should not be a problem.
FedericoBruzzone commentedon Nov 14, 2026
Yup, exactly. I don't recall why I didn't open the PR (may I was convinced that I had), but I do have a branch with this diff:
I hope this helps, folks :D
aeft commentedon Nov 14, 2026
@rengolin @FedericoBruzzone #322 and #323 fix the issues I found. With both, plus the CI change from the
macosbranch, all three Pre-Commit jobs pass on my fork, and macOS gives 93 passed / 2 unsupported, same as Linux: https://github.com/aeft/lighthouse/actions/runs/43635619040Once both PRs land, the CI change should be the last step. Happy to send it as a PR against main, or leave it to you.
[macOS] Fix torch install and kernel-bench runtime library lookup (#322)
[transform_ext] Avoid stale op handles in prepare_subgraphs (#323)
rengolin commentedon Nov 14, 2026
Nice! Both were good fixes, I merged them, thanks! Now we just need to add the workflow for macos.
FedericoBruzzone commentedon Nov 15, 2026
Thank you :D
This aspect is tracked under #283.
Overall, I'd wait for @tkarna.
aeft commentedon Nov 15, 2026
@FedericoBruzzone Thanks! I think #283 is already covered by #302 (torch-mlir now comes from PyPI), and the fork run above installs it from there on macOS.
@rengolin would you like to push your
macosbranch as a PR, or should I open one with your commit? cc @tkarna in case anything in #283 is still missing.rengolin commentedon Nov 15, 2026
That's an old branch. Feel free to cheery pick and open a new PR.