coverallsapp / coverallsapp/github-action

Invalid paths in lcov input leads to files silently disappearing

Open
#113 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
520
Forks
78
PR merge metrics
No merged PRs in 30d

Description

If there is a misconfiguration that causes the file paths in lcov.info to be invalid, the files are missing from the output to coveralls with no warning or error.

Relates to https://github.com/coverallsapp/github-action/issues/103

For example in this ctest (Debug) run: https://github.com/ShrapnelDSP/ShrapnelMonorepo/runs/5343824003

# lcov input
SF:/__w/ShrapnelMonorepo/ShrapnelMonorepo/firmware/components/audio_param/include/audio_param.h

Run coverallsapp/github-action@master
  with:
    path-to-lcov: lcov.info
    base-path: test
    github-token: ***
    parallel: true
    flag-name: ctest
    coveralls-endpoint: https://coveralls.io/

# locv after processing by coveralls action
SF:test/__w/ShrapnelMonorepo/ShrapnelMonorepo/firmware/components/audio_param/include/audio_param.h\n

[info] "2022-02-26T10:17:40.263Z"  'sending this to coveralls.io: ' '{"source_files":[],"flag_name":"ctest"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the action's handling of the lcov.info input, using the shown SF: path and base-path: test configuration as a reproduction. Trace how invalid paths become an empty source_files payload; done means the action reports the invalid files instead of silently sending no source files.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.