diff options
| author | Eli Schwartz <eschwartz@archlinux.org> | 2022-03-25 01:32:08 -0400 |
|---|---|---|
| committer | Eli Schwartz <eschwartz@archlinux.org> | 2022-03-25 01:32:08 -0400 |
| commit | 0022e1863d8d9769378ebfb56695bdbf55f118b9 (patch) | |
| tree | 1ad764d54ccdaa6915b24ff6aa67fb833ba48499 /docs | |
| parent | b0d300e788571f48e95d6e673c6f94e54d1dd355 (diff) | |
| download | meson-0022e1863d8d9769378ebfb56695bdbf55f118b9.zip meson-0022e1863d8d9769378ebfb56695bdbf55f118b9.tar.gz meson-0022e1863d8d9769378ebfb56695bdbf55f118b9.tar.bz2 | |
cygwin CI: work around gcovr bug
Due to https://github.com/gcovr/gcovr/pull/576 it is not possible to
`pip install gcovr` and have it work.
It is possible, but not ideal, to install the cygwin gcovr package,
which is unmaintained and built for python36 while only depending on
python39.
This is of course not a problem on the other CI jobs, where we either
install it from a distro repository that ensures it is stable and
backports patches, or simply tests that the resulting image passes tests
before baking it as a CI images update.
gcovr upstream isn't sure when they are going to release a new version
that fixes this bug. There is a new feature release scheduled "soon".
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions