-
### Describe the bug
During the workflow runs for #3378 uploading coverage to the CI failed.
### Steps to reproduce
1. Fork Cobbler
2. Create branch
3. Submit PR
4. See Testing CI fail
…
-
(raising a new issue here because I cannot reopen the closed issue #327)
### Operating System
```
Linux aaa9b2ded5ac 5.15.0-79-generic #86-Ubuntu SMP Mon Jul 10 16:11:29 UTC 2023 aarch64 aarch6…
-
### Expected Behavior
Parsing of `coverage.lcov` report.
```
bash
-
We already use Codacy for code quality and they also offer a code coverage feature. Instead of using two tools, we should instead consolidate code coverage into Codacy and move from Codecov.
---
Req…
-
- Currently, users have to convert MSTest to a different format before using the coverage reporter. A process like the one described [here](https://docs.microsoft.com/en-us/azure/devops/pipelines/task…
-
To avoid re-downloading over and over, we can cache the latest version of `codacy-coverage-reporter` at Docker build time, this will improve the speed of the action and the user experience.
-
I'm running parallel tests so I will upload multiple coverage reports. Ideally, I can add a wildcard (or similar) so that I don't have to hardcode each individual filename (one for each thread). That …
-
Since 13.13.3 was merged 2 hours ago, our bitbucket pipelines have been broken with the following error:
> bash ______ __
> / ____/___ ____/ /___ ________ __
> / / / __ …
-
### Are you looking for help?
No, looking for the codacy coverage CLI to support ARM 64-bit platforms
### Scala Version (2.10.x / etc)
N/A
### Operating System (Ubuntu 15.10 / MacOS 10.10 …
-
We are getting this error when running the coverage reporter action using the latest version (13.13.3)
```
codacy-coverage-reporter-linux: OK
chmod: cannot access '/home/runner/.cache/codacy/cove…