Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(web): top-level coverage reporting artifact is all but broken #13195

Closed
jahorton opened this issue Feb 12, 2025 · 0 comments · Fixed by #13196
Closed

chore(web): top-level coverage reporting artifact is all but broken #13195

jahorton opened this issue Feb 12, 2025 · 0 comments · Fixed by #13196
Assignees
Milestone

Comments

@jahorton
Copy link
Contributor

#13158 (as of commit 3e456bb) experienced a build failure on the "Test - Keyman (Web)" build. Upon inspection, it's because the changes made therein... caused the collation folder for coverage reports to become empty! In essence, our coverage-reporting setup is and has been pretty much broken for a while. That said, the 17.0 version of the report is fine - the coverage action was written before the big reorganization of Web-related code we did earlier during 18.0's alpha cycle.

Here's a link to the coverage report from #13158's parent PR: https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/522532:id/build/coverage/index.html. Note how only predictive-text stuff appears within it! The same can be seen for builds against master (and now, beta).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants