New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
coverage reporting broken? #642
Comments
cc/ @sbejaoui |
I see the error. @moylop260 any clue? |
Maybe the issue is that pip is ignoring the pinned versions:
Actually, it is not compatible. hehe Maybe, a bump version of coverage >=5 and make MQT script compatibles with new version could fix it |
Why do we pin these versions?
…On Wed, Mar 4, 2020 at 3:33 PM moylop260 ***@***.***> wrote:
Maybe the issue is that pip is ignoring the pinned versions:
- https://travis-ci.com/OCA/brand/jobs/293455206#L298
ERROR: coveralls 1.8.2 has requirement coverage<5.0,>=3.6,
*but you'll have coverage 5.0.3 which is incompatible.*
Actually, it is not compatible. hehe
Maybe, a bump version of coverage >=5 and make MQT script compatibles with
new version could fix it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#642?email_source=notifications&email_token=AAFI62ZXPN4BVAXLTV3ZEADRFZRDVA5CNFSM4LAUF4DKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENYEDAQ#issuecomment-594559362>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFI62Z6YMCL3ZNPXYLGYCLRFZRDVANCNFSM4LAUF4DA>
.
|
In fact, the issue is not a pinned version, the issue is because of it is ignoring the pinned version where the script is compatible. An bump/unpinned version requires a migration of the script in order to be compatible. But answering the pinned version comes after a issue using a new one: Reported here: And fixed here: IMHO Since that MQT is used for all OCA (and other orgs) projects is better using a pinned version in order to avoid errors for all projects. |
Hello the coverage is still broken in all OCA repos I could look at. SHORT VERSION: - git clone --depth=1 https://github.com/OCA/maintainer-quality-tools.git ${HOME}/maintainer-quality-tools
- export PATH=${HOME}/maintainer-quality-tools/travis:${PATH} - export PATH=${HOME}/maintainer-quality-tools/travis:${PATH}
- travis_install_nightly - travis_install_nightly
+ - pip install -q coverage==4.5.4
+ - pip install -q QUnitSuite codecov coveralls
script: script:
- travis_run_tests - travis_run_tests Now Let me see if I understood well and explain:
Some googling led me to "coveralls is not working for python 3.5 or 3.8": So then I tried pinning Now the question is how do we fix this for real in the maintainer-quality-tools? |
Thanks a lot raphael for the explanation. |
The diff doesn't seem correct. We are not using anymore coveralls. |
@pedrobaeza Well it seems we still use coveralls: https://github.com/OCA/maintainer-quality-tools/blob/master/travis/travis_after_tests_success#L6 |
But not effectively. That's only old code. Codecov is the one valid. If the issue is solved removing coveralls, then that cleaning should be done instead. |
As recommended by https://docs.coveralls.io/python Attempting to fix OCA#642
As recommended by https://docs.coveralls.io/python Attempting to fix OCA#642
As recommended by https://docs.coveralls.io/python Attempting to fix OCA#642
See for example: https://travis-ci.com/OCA/brand/jobs/293455206#L1189-L1199
I have not had time to investigate yet.
The text was updated successfully, but these errors were encountered: