rangareddy commented on issue #17232:
URL: https://github.com/apache/hudi/issues/17232#issuecomment-5366038538

   This issue was reviewed as part of the JIRA-migrated backlog triage 
(HUDI-9037).
   
   **Findings: this has been done. Coverage is being published to Codecov.**
   
   On `master`, `.github/workflows/bot.yml` has three **active** upload steps:
   
   ```yaml
   - name: Upload coverage to Codecov
     uses: codecov/codecov-action@75cd11691c0faa626561e295848008c8a7dddffe # v5
     with:
       files: ./jacoco-report.xml
       disable_search: true
       flags: spark-client-hadoop-common
   ```
   
   at lines 176, 234 and 333. Each is preceded by 
`./scripts/jacoco/generate_merged_coverage_report.sh` and uploads under its own 
flag. Additional blocks at `:391`, `:464`, `:530`, `:596` and `:662` are 
present but commented out, so coverage can be widened later without new 
plumbing.
   
   The integration has also been maintained rather than landed once and left:
   
   | PR | what | merged |
   | --- | --- | --- |
   | #18230 | `chore(ci): Add Codecov coverage report in GitHub actions` | 
2026-02-21 |
   | #18994 | `[MINOR] Disable codecov-commenter PR comment` | 2026-06-14 |
   | #19130 | `chore(ci): upload integration-test coverage to Codecov` | 
2026-07-01 |
   | #19138 | `chore(ci): modernize Codecov config for the coverage initiative` 
| 2026-07-27 |
   
   Closing as fixed. If the intent was broader - every module reporting rather 
than the three active jobs - that is worth a fresh ticket naming the target 
coverage surface, since the commented-out blocks suggest that expansion was 
deliberately deferred rather than forgotten.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to