coverallsapp / coverallsapp/github-action
Action expects `lcov` to be run in `runner` environment/file system.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 520
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
If unit-tests and lcov are run inside a container, they end up with a path like, /github/workspace/src/SourceFile.cpp.
However, if the unit-tests and lcov are executed using the run: tag (natively in the runner), they have a path like, /home/runner/work/<repo>/<repo>/src/SourceFile.cpp.
I was unable to discover an option that could be passed to lcov to satisfy the Coveralls GitHub action requirement. I was able to introduce a workflow step to workaround this issue (shown below), but my goal would be to remove this step in favor of an updated Coveralls acton.
- name: Coveralls Action Bug Workaround
id: coveralls_bug_workaround
run: sudo sed -i 's/github\/workspace/home\/runner\/work\/<repo>\/<repo>/g' ./coverage/lcov.info
My expectation is that the Coveralls GitHub action would be compatible with tests executed in both native and docker actions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the workflow with lcov run inside a container and natively via the runner, using the paths shown in the issue. Inspect the action's handling of coverage paths and compare both environments. Done means the action accepts both path formats without the sed workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100