Skip to content
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

24 tests fail #331

Open
yurivict opened this issue Feb 3, 2024 · 3 comments
Open

24 tests fail #331

yurivict opened this issue Feb 3, 2024 · 3 comments
Labels
information needed More information needed

Comments

@yurivict
Copy link

yurivict commented Feb 3, 2024

log

Version: 0.14.0
Python-3.9
FreeBSD 14.0

@woodruffw
Copy link
Member

From that log, the failing tests really just look like mypy errors (not actual unit test failures).

Could you provide some more context here? We'll make an effort to diagnose those, but they aren't indicative of regressions or errors in the release itself.

@woodruffw woodruffw added the information needed More information needed label Feb 3, 2024
@yurivict
Copy link
Author

yurivict commented Feb 3, 2024

This happened in the context of the FreeBSD ports framework - the www/py-cachecontrol port is being tested.

These mypy-related packages are installed:

py39-mypy-1.8.0                Optional static typing for Python
py39-mypy_extensions-1.0.0     Experimental type system extensions for programs
py39-pytest-mypy-0.10.3        Mypy static type checker plugin for pytest

@woodruffw
Copy link
Member

Okay, thanks for the extra context. I'm not sure if we do (or ever have) supported a pytest-mypy path -- I believe our CI runs tox -e mypy or similar. It's possible that running it through the pytest plugin causes some configuration settings to be dropped, causing these errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
information needed More information needed
Projects
None yet
Development

No branches or pull requests

2 participants