-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
pipx run coverage lcov -o coverage.lcov
yields No data to report
on GitHub actions (maybe namespace issue?)
#730
Comments
Until it gets resolved in pyscaffold/pyscaffold#730. Web of dependencies and use of GitHub actions makes it difficult to troubleshoot.
Hi @sgbaird, sorry for the delay. I am trying to understand your reproducer and see what might be happening. # .coveragerc to control coverage.py
[run]
branch = True
source =
honegumi.core
honegumi.ax
# omit = bad_file.py But in your from ax.service.ax_client import AxClient I wonder how you are managing to import from Maybe if your coverage is configured to report on |
Great catch. That was a bad naming convention on my part. I need to rename |
Description of your problem
I've been having a lot of trouble with coverage with the setup in PyScaffold. Maybe it has something to do with me using namespace packages. There's a discrepancy between what's running via GitHub actions and what runs locally, and it's not clear where in the tangle of packages and interfaces the issue is arising from.
Please provide a minimal, self-contained, and reproducible example.
Here is a Colab reproducer that shows I can get coverage manually pretty easily, though it's not exactly what happens in GitHub actions. I've found it really tough to debug things within GitHub actions, so any help in pointing me in the right direction if something sticks out to you is appreciated. The reproducer invokes
tox
followed by the coverage command.Workflow that failed
Versions and main components
3.8.*
pip
I thinkThe text was updated successfully, but these errors were encountered: