Using for Python code and coverage.py

[aodj]

I was just looking into this for use in the GitHub actions beta, and covering my Python code, but it looks like the coverage tooling for Python doesn't support lcov output (ie running coverage.py via pytest-cov on pytest unittests).

I know that the coveralls Python library can interface with the coveralls.io API, so I'm curious what the suggested solution might be.

Any ideas?

[nickmerwin]

Hi @aodj, could you try the steps described here:

https://github.com/coveralls-clients/coveralls-python/blob/master/docs/usage/multilang.rst

e.g.:

coveralls --output=coverage.json
coveralls-lcov -v -n coverage.info > coverage.json

Then use "./coverage.json" as the path-to-lcov input for the Coveralls Action.

Let me know how it goes, thanks!

[aodj]

I'll give it a try, but is installing and running a Ruby gem the only option here? I've previously used a workflow on Travis that simply invokes the coveralls tool which uploads the output from coverage.py, which is nice since it's simply a case of installing an extra Python lib.

[aodj]

I think I'm missing something; the coveralls-lcov tool doesn't output LCOV formatted data. It consumes LCOV data to output json Looking at the coveralls Python library, is it not possible to use the api/v1/jobs endpoint since that appears to consume the more common JSON format instead of LCOV:

[aodj]

Any more thoughts on using the action with Python?

[aodj]

Just to keep this ticket up-to-date I gave up with this action, and just used the coveralls Python package. Workflow for reference.

[mikkokotila]

@aodj dead simple approach solves the issue. Which raises an important question; how come the official version from the company itself, does not work?

[hakonanes]

However, running just coveralls on a pull_request event does not prompt Coveralls.io to later on to add a comment to the PR, even though it is enabled in the Coveralls.io settings?

[abhinavsingh]

This probably should be re-opened or at-least put instructions for Python integration upfront in README.

[jvesely]

Running just coveralls in github actions reports branch HEAD. I ended up with:

    - name: Coveralls
      run: |
        CI_BRANCH=${GITHUB_REF#"ref/heads"} coveralls
      shell: bash

@hakonanes, There's also CI_PULL_REQUEST env var that you can set to something from ${{ github.event }} context or parse it out of the file at $GITHUB_EVENT_PATH

[ly-cultureiq]

if nickmerwin/node-coveralls#243 gets merged - i have a simple pr to add pytest and coverage.py support