Closed emamerto closed 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.
@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!
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.
@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!
Closing this issue here since there is not much we can do here. Let me know if we need to re-open.
I am having the same issue. Recently stopped working
@angelxmoreno please follow the same steps for support to be able to help you.
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.
Same here
I am having the same issue. Recently stopped working
@angelxmoreno @smohanty-mdsol have you guys got it resolved upon contacting the support?
@fasatrix Sorry, I do not recall
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$ .
Same error here. Suddenly stop working, everything is alright at CircleCi side.
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)
Step 2 - export token on terminal
Step 3 - Send clover xml file to Codacy
Actual Outcome
Terminal Output
Codacy Error's Message