-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add Mac OS tests to Github Action #4759
Comments
The test suite might not be run, but that doesn't mean the tests are failing. |
I reported this as running the test suite on my local machine produced different errors than those reported by the GitHub actions. I have added the report. Perhaps this is due to something I messed up in my local environment, but I did not fully understand why these errors were only thrown on my local machine.
|
Can you run these two commands and check if anything changes? # The output might help
pylint --version tox -r -e py39 --
# Inside the 'pylint' folder
python3.9 -m venv venv-39
source venv-39/bin/activate
python -m pip install -U pip setuptools wheel
pip install -r requirements_test.txt
pytest tests/test_functional.py |
Manual route still gives me the same failed tests.. Perhaps it has something to do with my local python installation, but I wouldn't know why. |
I also have this issue on MacOS 11.4 BigSur, and they only occur with Python 3.9. Python 3.8 works fine.
|
Quite strange. I have no issues with Python 3.7 through 3.10 |
Might it be something with Big Sur? In your earlier comment you mentioned you were using Catalina. |
Another possibility would be the architecture, as I am running an M1 with arm64. At least the Downloads page on python.org has two separate installers (Intel and universal2). |
Maybe we need to change those options in the pylintrc ?
|
As this currently only happens with some yet to determine specific combinations of Python version / architecture / OS I would say no - I don't think it is Edit: just checked: running |
OK, I just dug a little deeper. The versions installed with I do not know if |
This became a real issue when working on #4784. To test my implementation I copied the code to my local pylint installation. This worked and all messages showed up correctly. Do we have any idea about how to go about solving this issue? I would gladly help, but have no idea where to start.. |
How did you install your Python version? When I first stumbled over this I made a list to check what the culprits are, and it boiled down to two modules:
For example, the Edit: (tmp396) 3.9.6 % find . -name "math.pyi"
./envs/tmp396/lib/python3.9/site-packages/mypy/typeshed/stdlib/math.pyi ... whereas my originally created Python 3.9 environment does not have a (tmp396) 3.9.6 % find ~/programming/forks/pylint/venv39 -name "math.pyi"
/Users/andreas/programming/forks/pylint/venv39/lib/python3.9/site-packages/jedi/third_party/typeshed/stdlib/2and3/math.pyi
/Users/andreas/programming/forks/pylint/venv39/lib/python3.9/site-packages/jedi/third_party/django-stubs/django-stubs/db/models/functions/math.pyi
/Users/andreas/programming/forks/pylint/venv39/lib/python3.9/site-packages/mypy/typeshed/stdlib/2and3/math.pyi However, upgrading
but Hmm, I really hoped that some missing Maybe @Pierre-Sassoulas or @cdce8p who have more knowledge about how inference from C implementations work in |
Currently I'm using HomeBrew. Going to look into Edit: |
I don't have a mac so I can't test but could it be that the version of socket is not the same ? I remember that Mac often have outdated lib by default. |
I noticed that |
@DanielNoord my installation has neither (both the "working" installation from |
Similar to @DudeNr33, I am getting false positives when importing from math (all members as far as I can tell, noticed it for pi, sin, cos, fmod, and others). I'm running Big Sur 11.4 on an intel architecture, and the problem started occurring after updating python to 3.9.6 yesterday using homebrew. |
Same here. Using pyenv's python fixed this problem. |
I'm also getting this same issue with math, socket and also struct which hasn't been mentioned before that I see. |
It might be interesting to take another look at this now that |
I just did another test on I'm still going to open a PR to run one suite on CI though as it wouldn't hurt to do so. |
Current problem
The tests suite is not run on Mac so the tests are failing locally for mac developpers.
Desired solution
Run Mac tests in Github Actions.
Additional context
See discussion in #4753 (comment)
The text was updated successfully, but these errors were encountered: