Unfortunately codecov commonly has issues with proper reporting. It looks like in your case the mac builders weren't successfully submitting coverage. We'd love to migrate to a more functional system, but codecov and coveralls both have...issues. We won't let that block review, although pushing a few extra commits or rebasing can resolve it since it's an inconsistent problem with codecov.
As for doc8, feel free to modify the offending line. Moving the trailing punctuation (which should be a period) will likely resolve it. It's probably worth filing a bug with doc8 around this if you can come up with a small reproducer since I believe we've seen this issue in the past. -Paul On Thu, Jul 29, 2021 at 10:38 AM Krzysztof Jackiewicz/Security (PLT) /SRPOL/Engineer/삼성전자 <k.jackiew...@samsung.com> wrote: > > Hi, > > Project codecov and doc8 checks for my recent PR > (https://github.com/pyca/cryptography/pull/6181) have failed and I can't > find the way to make them pass. > > IMHO the codecov fail is unrelated to the PR. It looks like a problem with > testing environment. I ran pytest with coverage report before and after my > changes and the coverage ratio was unchanged. Is it possible to reproduce > the codecov check locally somehow? > > The doc8 check fails because of too long line in CHANGELOG.rst but the line > was not changed in the PR. I noticed that doc8 complains only if the > offending line is not the last one on the list. I could trick it by putting > the KBKDFCMAC entry before the offending line but I don't think it's the > way to go. > > Please advise, > > Thanks > > -- > Krzysiek > > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev@python.org > https://mail.python.org/mailman/listinfo/cryptography-dev _______________________________________________ Cryptography-dev mailing list Cryptography-dev@python.org https://mail.python.org/mailman/listinfo/cryptography-dev
