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

Re-enable test coverage for CI #726

Open
phmccarty opened this issue Feb 28, 2022 · 1 comment
Open

Re-enable test coverage for CI #726

phmccarty opened this issue Feb 28, 2022 · 1 comment
Labels
enhancement Feature request for autospec

Comments

@phmccarty
Copy link
Contributor

phmccarty commented Feb 28, 2022

As mentioned in #660 (comment), the coverage tool is no longer present in the python-extras bundle. My best understanding is that coverage was pulled into the bundle originally via runtime dependencies, not via direct listing in the bundle definition. And once that dependency link was severed (from a package (or packages) that I have not identified :-) ), the tool disappeared from the bundle.

It is desirable to re-enable coverage analysis for CI runs. The options I see to resolve are:

  1. Add pypi-coverage to python-extras, since the CI container installs that bundle already.
  2. Add pypi-coverage to a different bundle if that's more appropriate, and also update the Dockerfile (referenced above) to install that bundle as well.
@phmccarty phmccarty added the enhancement Feature request for autospec label Feb 28, 2022
clrbuilder pushed a commit to clearlinux/clr-bundles that referenced this issue Mar 31, 2022
@phmccarty
Copy link
Contributor Author

I opted to implement option 1, simply adding pypi-coverage to python-extras.

We can re-enable the coverage scans at some point after the Dockerhub image is updated to 36120 or newer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature request for autospec
Projects
None yet
Development

No branches or pull requests

1 participant