cloudwego / cloudwego/eino

ci: Codecov configuration is ignored because the workflow path does not exist

Open Beginner friendly
#1,209 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
13k
Forks
1.1k
Avg merge
4h 6m
Merged PRs (30d)
41

Description

**Describe the bug**

The unit-test workflow passes `codecov_yml_path: ./github/.codecov.yml`, but that path is not tracked. The repository's Codecov configuration is `.github/.codedev.yml`.

The current successful upload step therefore uploads coverage without the repository's configured project/patch thresholds, ignore rules, or comment settings.

**To Reproduce**

1. Run the `eino-unit-test` job in `.github/workflows/tests.yml`.
2. Inspect the Codecov upload log.
3. Observe: `Config file github/.codecov.yml not found, or is not a file. Ignoring config.`

This is visible in job `95749550042` from Actions run `32148915071` on the current `main` commit.

**Expected behavior**

The Codecov upload step should point to the tracked configuration file so Codecov applies it.

**Screenshots**

Not applicable; the Actions log contains the diagnostic above.

**Version:**

`main` at `ebd616c8291e957684ea6ca99dd54225d04e0438`

**Environment:**

GitHub Actions, `cloudwego/common-eino-test@main` Codecov upload step.

**Additional context**

A minimal fix is to set `codecov_yml_path` to `./.github/.codedev.yml`. I checked open and closed issues, pull requests in every state, repository discussions, and the files changed by every currently open PR; none covers this path mismatch.

Contributor guide

Open the contributing guide

Research direction

Open .github/workflows/tests.yml and inspect the Codecov upload step and its job log. Compare its codecov_yml_path with the tracked .github/.codedev.yml file. Done means the workflow points to the tracked configuration and the upload log no longer reports that the config file is missing.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
92/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.