Add code coverage back in to SCons CI

[mwichmann]

The codecov package has been removed from PyPI and fails the build:

if %COVERAGE% equ 1 .\.appveyor\install-cov.bat
Collecting coverage
  Using cached coverage-6.2-cp36-cp36m-win32.whl (182 kB)
ERROR: Could not find a version that satisfies the requirement codecov (from versions: none)
ERROR: No matching distribution found for codecov
Command exited with code 1
if ($env:COVERAGE -eq 1) { .\.appveyor\coverage_report.ps1 }

This was entirely intentional on the part of the company providing the package, and we have to seek alternatives.

https://about.codecov.io/blog/message-regarding-the-pypi-package/

Perhaps it's a good time to move a coverage build to a GitHub action, since one of the proposed mitigations from that blog is already available as a prebuilt action.

Update: changed the summary line from "Python codecov package is gone, breaks appveyor-coverage build" - the specific issue of appveyor broken is resolved, and we subsequently lost appveyor entirely, but still want to track that we now don't have any automated code coverage reporting, whether at the level of the whole codebase, or at the level of an individual PR.

[mwichmann]

Updating - the one AppVeyor job that did codecov now no longer does; we have no replacement yet. Supposedly we can use this:

https://github.com/codecov/codecov-action

[mwichmann]

So what to do with this issue? Not only don't we have a coverage runner enabled any longer, we lost AppVeyor also. Do we want to keep this open and track the possibility of setting up some kind of code coverage again someday, or just close as not particularly relevant.

[bdbaddog]

Worth keeping it open til we find a solution.

…

On Wed, Jun 12, 2024 at 2:47 PM Mats Wichmann ***@***.***> wrote: So what to do with this issue? Not only don't we have a coverage runner enabled any longer, we lost AppVeyor also. Do we want to keep this open and track the possibility of setting up some kind of code coverage again someday, or just close as not particularly relevant. — Reply to this email directly, view it on GitHub <#4338 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAUCNHT3ZYPJVQP46GKBODZHA7ORAVCNFSM6AAAAABJGJKDI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSHEZDCNJVGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>