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

Pin to Coverage 4 for Python 3.6-3.7 on Windows #1227

Closed
wants to merge 1 commit into from

Conversation

hugovk
Copy link
Contributor

@hugovk hugovk commented Jan 10, 2020

For some reason, the new Coverage.py version 5 is failing on Windows for Python 3.6 and 3.7.

Run coverage run tests/test_black.py
Traceback (most recent call last):
  File "tests/test_black.py", line 1788, in <module>
    unittest.main(module="test_black")
  File "c:\hostedtoolcache\windows\python\3.6.8\x64\lib\unittest\main.py", line 64, in __init__
    self.module = __import__(module)
ModuleNotFoundError: No module named 'test_black'
##[error]Process completed with exit code 1.

It's passing on Windows for 3.8, and all Python versions on Ubuntu and macOS.

Here's an older build that passed for everything, before Coverage.py 5 came out.

This is a workaround to get the CI back to green.

@hugovk
Copy link
Contributor Author

hugovk commented Jan 12, 2020

Good news, this has been fixed in Coverage.py 5.0.3:

nedbat/coveragepy#862 (comment)

Restarting builds should fix the Windows issue.

@hugovk hugovk closed this Jan 12, 2020
@hugovk hugovk deleted the workaround-coverage-5-on-windows branch September 6, 2020 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant