Changes between Version 4 and Version 5 of Ticket #3384


Ignore:
Timestamp:
2020-08-19T15:31:03Z (4 years ago)
Author:
sajith
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3384 – Description

    v4 v5  
    33Let us unpin coverage and see what happens in CI!
    44
    5 For more context, the follow-up ticket to this would be #3385, which will attempt to use [[https://coveralls.io|coveralls.io]] for code coverage checks.  We are not entirely satisfied with [[https://codecov.io|codecov.io]], which we currently use.  For example, it is not always clear why codecov checks turn disapprove of certain PRs, even when test coverage remains unchanged.
     5For more context, the follow-up ticket to this would be #3385, which will attempt to use [[https://coveralls.io|coveralls.io]] for code coverage checks.  We are not entirely satisfied with [[https://codecov.io|codecov.io]], which we currently use.  For example, it is not always clear why codecov checks turn red/disapprove of certain PRs, even when test coverage remains unchanged.
    66
    77Now, in order to upload coverage reports to codecov.io, we will need to use [[https://github.com/coveralls-clients/coveralls-python|coveralls-python]], which requires that coverage reports should be in coverage 5.0 format.  Which is the real motivation for unpinning coverage.