Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

report.llcov not created

Open
  • Is something wrong?
#490 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by tracing the slather coverage command options shown in the report, especially --llvm-cov and --jenkins, and inspect how the command chooses its output path. Reproduce the command with a small Xcode project and check whether it creates CCC/report.llcov; done means the report is generated or the command clearly explains why it cannot be.

Written by the indexing model from the issue text.

Description

bundle exec slather coverage -s --scheme AAA \
		--build-directory BBB \
		--output-directory CCC \
		--workspace DDD \
		--llvm-cov --jenkins \
		EEE;

When I run the above (inside a Jenkins job), the file CCC/report.llcov isn't generated, even though it doesn't report any errors.

Dominant language
Ruby
Stars
1.6k
Forks
239
Avg merge
10h 19m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from SlatherOrg/slather

All issues in SlatherOrg/slather

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.