Skip to content

[DO NOT MERGE] test: verify Codecov config takes effect (same-repo) - #6055

Closed
jam-jee wants to merge 1 commit into
masterfrom
codecov-verify-donotmerge
Closed

[DO NOT MERGE] test: verify Codecov config takes effect (same-repo)#6055
jam-jee wants to merge 1 commit into
masterfrom
codecov-verify-donotmerge

Conversation

@jam-jee

@jam-jee jam-jee commented Jul 18, 2026

Copy link
Copy Markdown
Collaborator

⚠️ DO NOT MERGE — verification PR

Confirms the merged codecov.yml (PR #6034) takes effect. Makes a no-op docstring-only change in sagemaker.mlops to force a unit-test coverage upload so Codecov recomputes.

Why same-repo (not a fork): the earlier fork-based attempt (#6054) uploaded coverage but Codecov errored it (state=error, sessions=0) because the CodeBuild uploader gets no PR/branch context for fork PRs (pr=false, empty branch). Same-repo branches upload with full context (verified: #6051 processed cleanly with sessions=4), so Codecov will actually process and post here.

This branch is cut from current master (which contains codecov.yml). Expected result:

  • test files excluded via ignore: (previously ~98% of measured files were test files)
  • project ~71% product-only, not the old ~90%
  • status targets project 65% / patch 70%

Will be closed without merging once verified.

No-op docstring line in sagemaker.mlops to force a unit-test coverage
upload from a SAME-REPO branch (fork PRs upload without PR/branch context
and Codecov errors them). Confirms the merged codecov.yml takes effect:
- test files excluded from the report (ignore: list)
- product-only project coverage (~71%, not the old test-inflated ~90%)
- project floor 65% / patch 70% status targets

Branch cut from current master (contains codecov.yml). Verification only.
@jam-jee jam-jee closed this Jul 18, 2026
jam-jee added a commit that referenced this pull request Jul 27, 2026
…erage (#6056)

`after_n_builds: 4` made Codecov wait for four coverage uploads before
finalizing a report. But this repo's CI runs unit tests only for the
submodules a PR changes (detect-changes), so a PR touching 1-3 submodules
produces fewer than four uploads. Codecov then waits forever and never
posts a report or status.

Observed on PR #6055 (changed only sagemaker-mlops): the mlops unit-test
job uploaded coverage successfully, but Codecov reported state=error,
sessions=0 and posted no codecov/project or codecov/patch status, because
it was still waiting for three more uploads that never come.

Drop the fixed count and rely on `wait_for_ci: true`, which finalizes the
report once CI completes using whatever uploaded — correct for this repo's
dynamic per-submodule CI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant