archived-codacy / php-codacy-coverage

Phar for uploading PHP code coverage to Codacy
https://www.codacy.com
MIT License
44 stars 18 forks source link

Hey Seems like we stopped receiving your coverage results. Check your CI server! #40

Closed emamerto closed 6 years ago

emamerto commented 6 years ago

Issue

Coverage received successfully, but not displaying in Codacy

PHP Version

Tried it on 7 and 5.6

Operating System

Tried it on Mac and Linux

Expected Outcome

Coverage should display in the Codacy Dashboard and File page

Steps to reproduce the issue

Step 1 - Installed codacy/coverage (I preferred globally)

$ composer require global codacy/coverage

Step 2 - export token on terminal

$ export CODACY_PROJECT_TOKEN=<project_api_token>

image Step 3 - Send clover xml file to Codacy

$ ~/.composer/vendor/bin/codacycoverage clover path/to/clover.xml -v

Actual Outcome

Terminal Output

image

Codacy Error's Message

image

rtfpessoa commented 6 years ago

@emamerto can you open a ticket with support at codacy dot com so they can track the specific case of your project?

From here the only thing I would suggest would be to check which commits you are sending coverage to. I would recommend sending coverage from a build server like CircleCI or TravisCI automatically for every commit.

emamerto commented 6 years ago

@rtfpessoa Additionally I am using Bitbucket Server and we use Bamboo for our build system, but I doubt that sending it from bamboo would make a difference since machine I was sending it from is identical.

Maybe specifying the commit would solve the issue, I would try this before sending a ticket to support. Thank you!

rtfpessoa commented 6 years ago

The build server is just to make sure you are sending for every commit.

About support is so they can check the project internally and see if there is any problem they can detect.

emamerto commented 6 years ago

@rtfpessoa Thanks! My intention is to test my config so I was sending it manually.

So I just tried adding the commit hash of the last commit, and it's the same result 👎.

I'll check with support. Thank you!

rtfpessoa commented 6 years ago

Closing this issue here since there is not much we can do here. Let me know if we need to re-open.

angelxmoreno commented 6 years ago

I am having the same issue. Recently stopped working

rtfpessoa commented 6 years ago

@angelxmoreno please follow the same steps for support to be able to help you.

smohanty-mdsol commented 5 years ago

I am having the same issue. Recently stopped working. Codacy report is sending to codacy correctly. But the project status in showing Inactive in codacy.

fasatrix commented 5 years ago

Same here

fasatrix commented 5 years ago

I am having the same issue. Recently stopped working

@angelxmoreno @smohanty-mdsol have you guys got it resolved upon contacting the support?

angelxmoreno commented 5 years ago

@fasatrix Sorry, I do not recall

smohanty-mdsol commented 5 years ago

Hi Fabio,

I am not facing this issue right now. Thanks

Thanks & Regards Santosh M

On Tue, Oct 29, 2019 at 10:53 AM Angel S. Moreno notifications@github.com wrote:

@fasatrix https://urldefense.com/v3/__https://github.com/fasatrix__;!in-LNeQdOnY!hSYmW9NKYVkUgkFvTKyvs2NisHNvLVKsyg8Sd3kt4p3JxL9mYHnrSa7rwVgw2w$ Sorry, I do not recall

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://urldefense.com/v3/__https://github.com/codacy/php-codacy-coverage/issues/40?email_source=notifications&email_token=AGG2QMMKHBMG5VKSW6LRUW3QQ7CFZA5CNFSM4FP7VVEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECPIYPQ*issuecomment-547261502__;Iw!in-LNeQdOnY!hSYmW9NKYVkUgkFvTKyvs2NisHNvLVKsyg8Sd3kt4p3JxL9mYHnrSa7qybpucg$, or unsubscribe https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AGG2QMO2UQK2KJK2REDMVB3QQ7CFZANCNFSM4FP7VVEA__;!in-LNeQdOnY!hSYmW9NKYVkUgkFvTKyvs2NisHNvLVKsyg8Sd3kt4p3JxL9mYHnrSa4qXMe5JQ$ .

sgongar commented 4 years ago

Same error here. Suddenly stop working, everything is alright at CircleCi side.