archived-codacy / python-codacy-coverage Goto Github PK

The package on PyPi indicates that the code is under the MIT license: https://pypi.org/project/codacy-coverage .

However, this repo states it is under BSD3.

Which one is right?

Are you looking for help?

This is an issue tracker, used to manage and track the development of this Codacy project.

It is not a platform support system. If think your problem is related with our platform at https://www.codacy.com/, please contact us through our contact form or our internal chat application, visible after you login on the bottom right corner.

Keep in mind that this issue tracker is for specific problems of this project.

Python Version

3.7.5

Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)

Ubuntu 19.10

Use uname -a if on Linux.

Linux sky-hole 5.3.0-1008-gcp #9-Ubuntu SMP Mon Nov 11 09:52:23 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Library Dependencies

If this is an issue that involves integration with another system, include the exact version and OS of the other system, including any intermediate drivers or APIs i.e. if you connect to a PostgreSQL database, include both the version / OS of PostgreSQL and the JDBC driver version used to connect to the database.

Expected Behavior

Please describe the expected behavior of the issue, starting from the first action.

Actual Behavior

Please provide a description of what actually happens, working from the same starting point.

Be descriptive: "it doesn't work" does not describe what the behavior actually is -- instead, say "when sending the coverage with the command (...) it returns the output error (...)"

Reproducible Test Case

Please provide a some information on how to reproduce the bug. A PR with a failing test would be awesome, if possible.

If the issue is more complex or requires configuration, please provide a link to a project on Github/Codacy that reproduces the issue.

I'm running the python-codacy-coverage -r coverage.xml from a python3 environment and it fails with the messages:

DEBUG - b'{"error":"could not get json body."}'

If I run the exact command, same coverage.xml from a python2 environment is submits fine (doesn't matter the branch I'm on)

would be great if I could use your reporter with python3, as our build machine is only running python3.

At https://app.codacy.com/manual/Codacy/python-codacy-coverage/dashboard I see a coverage curve over time, but the coverage report (line by line) doesn't seem to be available?

It says "You need to request someone with write permissions to setup coverage.".

Does codacy support coverage reports (like on coveralls.io)?
Where is a working example that I can browse?

Right now codacy is allowing only to publish a signel result for a single languages.

This limit the adoption of codacy in place of coveralls for example where one is able to publish an aggregated results for multiple languages.

Issue noticed while evaluating the adoption of codacy for GlobaLeaks:

In globaleaks for example we are using coverage for collecting python coverage and istanbul for collecting javascript coverage and we mesh them up in json format before sending them to coveralls

Are you looking for help?

Maybe this is a bug. My Travis CI is in here.

Everytime when it run, it will send a report file coverage.xml successfully. Here is an example.

However, Codacy doesn't display coverage for successfully sent report in here.

As we can see, only one report displayed successfully.

Python Version

• Python3.6
• Python3.7
• Python3.8

Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)

• Ubuntu
• Windows 10

Expected Behavior

Codacy display coverage information in here.

1. coverage run -m unittest discover
2. coverage xml --include=ontology/* --omit=tests/*
3. python-codacy-coverage -r coverage.xml

Actual Behavior

Codacy doesn't display coverage for successfully sent report.

$ python-codacy-coverage -r coverage.xml
INFO - Parsing report file coverage.xml...
INFO - Uploading report...
INFO - Coverage received successfully.

Reproducible Test Case

Maybe you can clone my project in here.

Then, run make coverage.

There is line #111 in the reporter.py which works only when everything is fine. Otherwise, you will see a traceback instead of at least some kind of useful information about what happened.

On my system and I think in general, tox runs whatever 3.x version of python you have if the version you have is not 3.5.

When I change py350 to py35, it properly fails with an InterpreterNotFound. Is py350 even a thing? I looked in the tox docs and all I could see was {py27,...,py33,py34,py35,py36} nowhere I see definition with a trailing zero.

There is also this issue.
Talking about installing python3.5 yourself because tox doen not install it for you.