Closed vcernomschi closed 8 years ago
Hi @vcernomschi ,
From what I can check, your project has files named like src/path1/path2/file.js
but the reports are being sent for files named src/path1/compile/path2/file.js
.
Edit: Notice the compile
in the middle of the path.
If the coverage is sent for a different path we cannot associate it with the original file on our side.
If you cannot fix this at the coverage tool level, maybe you can sed replace the paths before sending the report to Codacy.
Thanks @rtfpessoa! I will update and check one more time.
@rtfpessoa: It doesn't display coverage for deepify, deep-package-manager projects.
From log I see that it sent and had valid path:
[debug] "2016-05-18T10:13:12.135Z" 'Sending coverage'
[debug] "2016-05-18T10:13:12.674Z" 'Successfully sent coverage'
TN:
SF:/home/travis/build/MitocGroup/deepify/src/lib/Exception/Exception.js
Hi, just wondering if there are any reasons. Because issue is still reproducible and affects 3 projects.
Hi @devs-deep,
Can you please explain your issue in Codacy website support, and specify which projects have the issue? You will get a better support that way.
Thank you
No coverage displayed after sending valid lcov report
Prerequisities:
Steps to reproduce:
cat ${COVERAGE_PATH}"/lcov.info" | codacy-coverage --debug
[debug] "2016-05-13T09:00:01.658Z" 'Successfully sent coverage'
)Expected result: coverage info is displayed. Actual result: coverage info is not displayed. After click on
Setup Coverage
button the following information is displayed:lcov.info.txt
Please refer to the attached coverage file (lcov.info.txt) that is generated by instanbul.
Please refer to the full TRAVIS CI log: https://s3.amazonaws.com/archive.travis-ci.org/jobs/129941728/log.txt