Yicong-Huang opened a new pull request, #4649:
URL: https://github.com/apache/texera/pull/4649

   ### What changes were proposed in this PR?
   
   Follow-up to #4646. The upload steps wired in that PR for the scala and 
frontend stacks have been silently uploading nothing (`Found 0 coverage files 
to report` in the Codecov action logs); only `python` and `agent-service` flags 
reach Codecov today. Reason: the underlying tools were not configured to write 
the report files at the paths the upload globs expected.
   
   `frontend/karma.conf.js`:
   - Add `"coverage"` to the explicit `reporters` list. Without this, Angular's 
`--code-coverage` flag cannot inject the `karma-coverage` reporter because the 
user-supplied `reporters` array overrides Angular's defaults.
   - Add an explicit `coverageReporter` block writing `lcovonly` to 
`frontend/coverage/lcov.info` — the path the Codecov upload step globs 
(`./frontend/coverage/**/lcov.info`).
   
   `build.sbt`:
   - Set `ThisBuild / jacocoReportSettings` to use both `ScalaHTMLReport()` and 
`XMLReport(encoding = "utf-8")`. By default `sbt-jacoco` emits only HTML; 
without XML there is nothing for Codecov to read at 
`<module>/target/scala-2.13/jacoco/report/jacoco.xml`.
   
   ### Any related issues, documentation, discussions?
   
   Follow-up to #4646. Original tracking issue: #4645.
   
   ### How was this PR tested?
   
   Will be exercised by this PR's own scala and frontend matrices on CI. 
Expected post-fix behaviour: both flags appear at 
https://app.codecov.io/gh/apache/texera (currently only `python` and 
`agent-service` are listed) and per-stack coverage shows up on PR commits.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Opus 4.7
   


-- 
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