-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
"ImportError: cannot import name 'get_all_providers'" for macOS in TravisCI after 1.5.1 update #5344
Comments
What error did you get? Are you sure you've installed all the dependencies? On my machine it complained of missing libomp. After installing libomp, I didn't see any issue.
|
Good call. When looking at our TravisCI log, a
I'll try your fix and report back. :) |
Thanks so much. It looks like editing our For anyone reading in the future, see: https://docs.travis-ci.com/user/installing-dependencies/#installing-packages-on-macos addons:
homebrew:
packages:
- libomp Or |
Describe the bug
We use
onnxruntime
in a Python project called SpinalCordToolbox, and test the project using pytest and TravisCI. Underonnxruntime==1.4.0
, our test suite for macOS 10.14 runs without error. But, after the update toonnxruntime==1.5.1
, the following error interrupts the test suite:By a stroke of luck, we had two identical Travis jobs run withn 30m, one before and one after the PyPI update (see spinalcordtoolbox/spinalcordtoolbox#2930 (comment)), so I think the version bump is the cause.
Potentially related to #2572, #3943, #4196, #4806.
Urgency
We have a quick workaround (pinning
1.4.0
), so it's not terribly urgent, but that isn't ideal, I think.System information
onnxruntime-1.5.1-cp36-cp36m-macosx_10_12_x86_64.whl
To Reproduce
The error occurred in a CI job, so it may be a little tricky to reproduce in a different environment. But, it amounts to:
onnxruntime
in a conda environment.pytest
test suite that includes a test that importsonnxruntime
.Relevant CI links:
Expected behavior
Test imports
onnxruntime
without failure (like it does in1.4.0
).Thanks much!
The text was updated successfully, but these errors were encountered: