-
Notifications
You must be signed in to change notification settings - Fork 3k
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
In a fresh miniconda
environment, pip
detects the macOS version number as 10.16
, causing the new 1.17.0 onnxruntime wheels to not be found
#19371
Comments
1.17.0
fails on macos-11
GitHub Actions runner ("ERROR: No matching distribution")1.17.0
fails on macos
GitHub Actions runners ("ERROR: No matching distribution")
I have difficulty on reproducing the issue. I created a Github Action with macOS-11, then tried to install the latest ONNX Runtime version. It worked well. https://github.com/snnn/ghtest/actions/runs/7749332259/job/21133675909 |
Well, that's good to hear, at least. It probably means that it isn't urgent or widespread. :)
I can only assume that the problem lies the specific environment of the project I am working on, then. I will continue debugging on my end and report back when I find out what conditions this happens under. |
I'm noticing a similar issue. I can install in a macos env, but it leads to segmentation faults in macos github actions. |
I think that may be a different issue? (One that would be better served by opening a separate issue.) My issue is specifically related to From the above issue, there is the following remark:
This seems like it might be on the right track, given the change from |
Alright, I was able to reproduce the issue in an isolated workflow. Running
Marking this issue as resolved for now. I will try to get to the bottom of how to fix this and update this comment later on, but I'll try not to bother the onnxruntime devs further with any more pings. :P EDIT: With the problem now well-understood, I've found these related issues:
EDIT2: In the future, this line of debugging could be done much faster using the command EDIT3: Looks like this is a dupe of: That issue suggests the fix of |
1.17.0
fails on macos
GitHub Actions runners ("ERROR: No matching distribution")miniconda
environment, pip
detects the macOS version number as 10.16
, causing the new 1.17.0 onnxruntime wheels to not be found
Describe the issue
We have a GitHub Actions workflow that performs the following steps:
pip freeze
.The
macos-11
runner began failing after the January 31st release of 1.17.0 with the following error:The Ubuntu/Windows runners seem to be able to install the frozen requirement
onnxruntime==1.17.0
just fine (alongside all of the other requirements we freeze). So, I don't think that this is a dependency conflict with another package.If I had to guess, this might be because of the change in platform signifiers for macOS wheels:
onnxruntime-1.16.3-cp38-cp38-macosx_10_15_x86_64.whl
onnxruntime-1.17.0-cp38-cp38-macosx_11_0_universal2.whl
But, the docs on
universal2
seem to suggest we meet thepip
/packaging
requirements. (We installpip==23.3.2
andpackaging==23.2
.)To reproduce
pip install onnxruntime
on a macos-11 runner will install1.16.3
.pip install onnxruntime==1.17.0
on a macos-11 runner causes a crash.Note: We
pip install
into a fresh Python 3.9 conda environment (pip+conda is a bit weird, so I wouldn't want to discount that as the potential cause). The packages that are installed when initializing the conda environment are:Then, we explicitly upgrade
pip
in a separate step:Urgency
Not terribly urgent for us, but if this affects macOS more generally, then it is probably quite urgent!
Platform
Mac
EDIT: Silly bot! I chose Mac as my OS, but you've added the
platform:windows
tag. Oops.OS Version
11
We also tested 12 and the same behavior persists. Presumably, this is also the case for 13/14?
ONNX Runtime Installation
Released Package
ONNX Runtime Version or Commit ID
1.17.0
ONNX Runtime API
Python
Architecture
X64
Execution Provider
Default CPU
Execution Provider Library Version
No response
The text was updated successfully, but these errors were encountered: